SCRUM: Why Scrum Requires Completely “Done” ✅ Software Every Sprint by Christiaan Verwijs

🔥The most essential rule in Scrum: 𝘤𝘳𝘦𝘢𝘵𝘦 “𝘋𝘰𝘯𝘦” 𝘴𝘰𝘧𝘵𝘸𝘢𝘳𝘦 𝘦𝘷𝘦𝘳𝘺 𝘚𝘱𝘳𝘪𝘯𝘵.

An increment is “Done” or it isn’t, there is no gray area:

👉No remaining stabilization

👉No remaining install package

👉No remaining acceptance tests

👩 🏫 𝗗𝗲𝗳𝗶𝗻𝗶𝗻𝗴 “𝗗𝗼𝗻𝗲”

“Done” depends on various factors:

👉quality guidelines

👉critical level

👉users involvement

👉technologies

👉and many more...

It requires an effective workflow to deal with all the stakeholders.

It may be tempting to limit “Done” to what a Development Team can do

So many teams end up with a definition of “Done” like:

👉code review

👉 Unit tests coverage

👉merged to develop-branch

👍👎 “𝗗𝗼𝗻𝗲” 𝗮𝗻𝗱 𝗨𝗻𝗱𝗼𝗻𝗲 𝗪𝗼𝗿𝗸

Such a previous definition of “Done” is incomplete.

You will still have to handle:

👉PO review of the feature

👉Unnoticed bug

👉Merge conflict of other teams' code

👉Wrong scale on mobile

👉Install failure on prod

👉Security flaws

👉Latency bottlenecks

👉User calls support due to deficient documentation

👉UX/UI accessibility flaws

😮𝗦𝘂𝗰𝗵 𝘂𝗻𝗱𝗼𝗻𝗲 𝘄𝗼𝗿𝗸𝘀 𝗵𝗮𝘃𝗲 𝗳𝗼𝘂𝗿 𝗰𝗼𝗻𝘀𝗲𝗾𝘂𝗲𝗻𝗰𝗲𝘀:

1️⃣ It draws time and energy

2️⃣ This decreases the transparency of the Increment

3️⃣ “staying busy” feeling while there is no potentially releasable product increment

4️⃣ The risk of software development not being fully validated

🗣️ 𝗤𝘂𝗼𝘁𝗲:

The bigger the gap between what a team defines as “Done” and what is needed -- the more disruptions and interruptions will happen in future Sprints due to undone work.

👀𝗘𝘅𝗮𝗺𝗽𝗹𝗲𝘀 𝘁𝗼 𝗶𝗹𝗹𝘂𝘀𝘁𝗿𝗮𝘁𝗲 𝘁𝗵𝗲 𝗽𝗼𝗶𝗻𝘁

1️⃣ A scrum team doing software for complicated machinery.

For practical reasons, they roll out to production in the end and use the pre-prod along the way.

In the end, they discovered that the prod hardware causes so many issues that they revert to the old solution and negate their work investment.

2️⃣ A PO makes a scrum team work on a market disruptive solution, but he chose to deliver it after one year. This was too late, the market did not respond positively, and all the investment was wasted.

🗣️ 𝗤𝘂𝗼𝘁𝗲:

𝘙𝘦𝘭𝘦𝘢𝘴𝘪𝘯𝘨 𝘵𝘰 𝘶𝘴𝘦𝘳𝘴 𝘦𝘢𝘳𝘭𝘺 𝘢𝘯𝘥 𝘰𝘧𝘵𝘦𝘯 𝘪𝘴 𝘵𝘩𝘦 𝘣𝘦𝘴𝘵 𝘸𝘢𝘺 𝘵𝘰 𝘮𝘪𝘵𝘪𝘨𝘢𝘵𝘦 𝘳𝘪𝘴𝘬.

😉 𝗔𝗱𝘃𝗶𝗰𝗲:

1️⃣ Maintain a ruthless focus on “Done” software

2️⃣ Make the gap between what you can do and what is needed for “Done” transparent

3️⃣ Make it smaller & simpler #refinement

4️⃣ It’s not about Scrum, but about reducing risk and maximizing value, and making impediments transparent.

#scrum #dod #done

Full article👉https://www.scrum.org/resources/blog/why-scrum-requires-completely-done-software-every-sprint