Peter Gfader's brain noise
5 great reasons for a long 4 week Sprint: #shitScrumMasterSay

Reasons for 4 week Sprints:

- You don’t know how to split PBIs (which is hard for your team)
- You have people work on different projects and only assign 20% to your project
- You don’t have to do that boring retrospective every week
- You can delay the hectic time before the Sprint Review
- You don’t need to remove impediments, since they don’t affect you that much in a long Sprint

Are your 3week ScrumSprints just Mini-Waterfalls?

Why is a 3 week sprint length not so effective in Scrum?

In my experience 3 week Sprints are:
- harder to plan, since we don’t know what we could do in 13 days from now
- harder to establish a rhythm, which is very important for a team to have

Sprints help to reduce complexity, and having Sprints longer than 2 weeks is not helpful in reducing complexity.

Do you know 5 great reasons for a long 4 week Sprint

Are your 3week ScrumSprints just Mini-Waterfalls?

Are your Scrum Sprints just Mini-Waterfalls?

I see “MiniWaterfalls” especially with teams that work in 3 or 4 week Sprints (don’t tell me you do 6week sprints ;-).

The tendency of longer sprints is to fall back in usual behavior and don’t change anything.
If you are in such a team, ask in the next Retro:

What do we need to change in order to half our Sprint time?

If you don’t have any established velocity yet, just adapt the Sprint length now. Make sure to do this with your team.

Important
Solve the root cause, and don’t just expand the Sprint length to fit the work!

What is the ideal Sprint length in Scrum?

Or, what is the ideal iteration length in XP?

I would say zero, because that would mean we deliver value immediately.
Isn’t that a nice goal to have ;-)

How do you do Sprint Reviews with 9 teams and 50+ team members?

Great approach!

Sprint Review 3.0:  The Science Fair Approach

Full article
http://iamagile.com/2012/06/13/our-evolution-of-sprint-reviews/

Set expectations to increase learning


"a team that meets its forecast each and every time might not be a hyper-productive team and for sure not a learning team"

Do you have a Sprint goal for each Sprint?

The Scrum Sprint Commitment/Forecast as an Expectation
http://yuvalyeret.com/2012/06/30/the-scrum-sprint-commitmentforecast-as-an-expectation/

What would change if you shorten your Sprints? #proscrum

I made similar observations as Kevin E. Schlabach in his blog post

Every time you shorten your iteration length, your team will realize that there are things that are time-consuming and painful.

Shorten your iteration…  (Sprint)
http://agile-commentary.blogspot.com/2008/09/shorten-your-iteration.html

I asked my current team (just recently started on a new product): 

What would change if we would have 1 week sprints? 

I got a couple of: “No good”, “Bad idea”.

  1. It would be difficult to produce something because we sit so much in meetings
  2. With this setup it doesn’t work, because we are not always available.

These are great answers with 2 major pains that we need to fix.
Just thinking about shortening your sprints, already helped highlight them…