#sprint0

[lukepivac]

In this article I talk about how #Sprint0 is a crucial preparatory phase in #Agileprojectmanagement that sets the foundation for success. It involves creating a #productbacklog, setting up tools, defining team roles, and developing strategies. By proactively addressing potential issues, it facilitates smoother development in subsequent sprints and enhances collaboration, efficiency, and innovation.

View On WordPress

[raphael-moutot-blog]

"Sprint Zero is like Casper, the friendly ghost. Well-meaning, but creepy”

— https://dzone.com/articles/antipattern-of-the-month-sprint-zero

[clearsinking]

Sprint 0 at F19 in Eindhoven for the new social intranet and RWD corporate website of Dutch charity Humanitas

[gfader]

Why Sprint 0 Doesn’t Exist

There is a need to do some work before the first Sprint starts. This includes defining the vision and goals, putting together a development team, creating an initial Product Backlog, refining the initial Product Backlog to understand enough work for the first Sprint – which also informs starting state architecture and design. This work should be accomplished in the shortest time possible so that the team can start to get feedback on real software.   As this work in itself does not deliver a potentially shippable product increment, this can not be a Sprint as one of the fundamental rules of Scrum is that each Sprint produces a potentially shippable increment of the product. Calling this pre-sprinting activity a Sprint is not just a matter of language as it sets a precedent early on with people that Sprints do not have to deliver potentially shippable increments of the product. There were also some examples given of teams using multiple Sprint Zeroes (0.1, 0.2… up to 0.14) and how this just perpetuated Big Up Front Design which everyone agreed was a bad thing.

Awesome! -> Sprint 0: “Don't call it like that. There is no such thing”

Discussion notes here  http://scrumopenspace.com/359/why-sprint-zero-doesnt-exist/

[gfader]

Sprint 0: "There is no such thing"

In my eyes "Sprint 0" (or "Iteration 0") highlights:

Not following lean practices

Reduced skill set of team.... which is OK, but acknowledge it!

Falling back to a "Delay business value" mindset

BTW: Even after your "Sprint 0" not everything in your infrastructure is ready yet, so you need to spend some time in Sprint X anyway...

----- 

Recommendation: Have a non-technical PO, that focuses on business value like a laser beam.

--------

Ken says it best:

"Sprint 0, there is no such thing."

Ken Schwaber

Scrum Assessment Discussion about Sprint 0 http://www.scrum.org/assessmentdiscussion/post/1317787