Asked • 03/18/19

Why use iterations in Scrum?

I am a Scrum Master in a 7 person team. We currently use one-week iterations for our sprints.I find that sprint planning overhead is huge (2 hours each week for entire team), and not nearly as productive as it should be. Our team members do not care what each task costs, they rely on one or two people with context to provide the estimates. It seems team-wide sprint planning is meaningless.Additionally, there has never been a sprint where we successfully completed ALL planned tasks. We always complete most of them, but there are always a few left over for the next sprint. It seems the time-boxed idea is not working at all, as we are never able to fully deliver. Maybe it has something to do with only two people contributing to estimates, but I don't see the team completing all features even if everyone contributes to the estimates.I know there are literally tons of books and papers that describe how wonderful iterative and incremental development are, but it just doesn't seem to bring enough goodness to our team.So my question is, how valuable exactly is it to keep a time-boxed iteration? If we just let one or two dedicated people maintain a strictly prioritized list and showcase deliverables as necessary, what's the downside of it?

1 Expert Answer

By:

Season H. answered • 02/03/22

Tutor
New to Wyzant

Agile Coach and Scrum Master with 10+ years at top tech companies

Still looking for help? Get the right answer, fast.

Ask a question for free

Get a free answer to a quick problem.
Most questions answered within 4 hours.

OR

Find an Online Tutor Now

Choose an expert and meet online. No packages or subscriptions, pay only for the time you need.