Podcast #128: We chat with Kent C Dodds about why he loves React and discuss what life was like in the dark days before Git. Listen now.

New answers tagged

0

There are two problems with only doing backlog refinement during Sprint Planning: The Sprint Planning meeting may end up being very long If you realise some information is missing from a story, then it is often too late to do anything about it There is no simple definition of when you should do backlog refinement or how often you should do it. It depends ...


2

As a new PM/PO I need to do Sprint Planning. As I understand, Sprint Planning is also known as Sprint 0 as nothing is delivered for customers or for internal teams to test/look into. This is not correct. Sprint Planning is a regularly occurring event. It happens once per Sprint and involves the entire Scrum Team. The purpose is to review the Product ...


0

Your understanding is correct. But sprint planning does not take 4-8 weeks. One sprint is created for 1, 2, 4.. weeks, before stating each sprint you need couple of days in order to plan your sprint. When you are planning, for example, 2nd sprint your development team works on 1st sprint. It means you should prepare everything beforehand. In my case scrum ...


2

Analysis In most agile frameworks, load-leveling of individual resources is a known anti-pattern. It is a variant of the 100% utilization fallacy, which generally leads project leadership to favor individual busyness over full-team collaboration and predictable delivery. Effective project management requires process slack. Agile frameworks generally make ...


2

If I understand correctly, you have 6 developers and 4 testers (I'm excluding the automation engineer because they aren't doing work in the sprint from your description). You say that the developers are completing pieces of functionality in as short as a day, so some work should getting tested early on. It is also clear that regression eats up a lot of time ...


1

For the sake of argument, ignore for one second the two entry level developers. You now have a team of just the two experienced engineers. Do you see any issues in implementing Scrum now? Probably not. You will develop in sprints, you will have sprint planning, you will do refinement, you will have retrospectives and reviews, build and deploy product ...


2

Who has authority? the designated group leader and Product Owner Here's one of your problems. As a Scrum Master, it's your responsibility to ensure that the Scrum Team (including the Product Owner (PO)) understands and follows the Scrum process. But the PO is your 'designated group leader'. Your boss. You need to clarify expectations from the management ...


2

he thinks the idea of a time-boxed sprint would produce additional stress in the beginning. I disagree with this assessment. The time boxed sprint is not intended to create a stressful deadline. Instead it is a natural break point that allows the team to get feedback and to inspect & adapt. A Scrum team that is a mixture of experienced engineers and ...


Top 50 recent answers are included