The Liberators Network

Why Scrum Requires Completely “Done” Software Every Sprint

January 17, 2020 The Liberators Season 1 Episode 21
The Liberators Network
Why Scrum Requires Completely “Done” Software Every Sprint
Chapters
The Liberators Network
Why Scrum Requires Completely “Done” Software Every Sprint
Jan 17, 2020 Season 1 Episode 21
The Liberators

In the Scrum.org Headquarters there is a picture of Ken Schwaber — one of the founders of Scrum — pointing at a sticky saying “Done”. This picture underscores the most essential rule in Scrum: create “Done” software every Sprint.

But what does that mean? And why does it matter? Isn't it enough if you just work as hard as you can during a Sprint and do the rest - like testing and deployment - in a future Sprint?

In this episode we explore how vitally important a Done increment is to the purpose of the Scrum Framework. And more importantly, to working empirically in the face of complex work.

This podcast is an audio recording of this post on Medium:
http://bit.ly/2LkKcFc

Donate to support our work
https://bit.ly/supportheliberators

Follow us on Medium:
https://medium.com/the-liberators 

Show Notes

In the Scrum.org Headquarters there is a picture of Ken Schwaber — one of the founders of Scrum — pointing at a sticky saying “Done”. This picture underscores the most essential rule in Scrum: create “Done” software every Sprint.

But what does that mean? And why does it matter? Isn't it enough if you just work as hard as you can during a Sprint and do the rest - like testing and deployment - in a future Sprint?

In this episode we explore how vitally important a Done increment is to the purpose of the Scrum Framework. And more importantly, to working empirically in the face of complex work.

This podcast is an audio recording of this post on Medium:
http://bit.ly/2LkKcFc

Donate to support our work
https://bit.ly/supportheliberators

Follow us on Medium:
https://medium.com/the-liberators 

Support the show (https://bit.ly/supportheliberators)