HTML MASTER CLASS /// LEARN TAGS /// BUILD STRUCTURE /// SEMANTIC WEB /// HTML MASTER CLASS /// LEARN TAGS ///

Undone Work in Tech Management

Learn about Undone Work in this comprehensive Tech Management tutorial. The technical debt trap.

⚡ Total XP: 0|💻 management XP: 0

Skill Matrix

UNLOCK NODES BY LEARNING NEW TAGS.

Select an unlocked node to view details root

🚀 LEVEL UP TO SENIOR:Unlock 500+ Advanced Practical Challenges & Exercises.

🎓 COURSERA PARTNER:Earn professional Google, Meta, and IBM certificates to supercharge your resume.

1Almost Done

In Scrum, there is no such thing as '90% Done'. If an item does not meet the Definition of Done by the end of the Sprint, it cannot be demonstrated at the Sprint Review, and it cannot be released. It returns to the Product Backlog for future consideration. This strict rule prevents hidden technical debt.

2Step-by-Step Breakdown

Transparency. Artifacts are designed to maximize transparency of key information. Everyone needs to look at the same artifact and have the exact same understanding of what it means.

1. The Product Backlog. An emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team. Owned entirely by the Product Owner.

Product Goal. Every artifact contains a 'Commitment' to ensure it provides information that enhances transparency. The commitment for the Product Backlog is the 'Product Goal' (the long-term objective).

2. The Sprint Backlog. The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), and an actionable plan for delivering them (how).

Knowledge Check. Who is the ONLY entity allowed to change the Sprint Backlog during a Sprint as more is learned about the work?

→The Product Owner
→The Developers

Sprint Goal. The commitment for the Sprint Backlog is the 'Sprint Goal'. It is the single objective for the Sprint. It provides flexibility regarding the exact work needed to achieve it.

3. The Increment. An Increment is a concrete stepping stone toward the Product Goal. It is the sum of all the Product Backlog items completed during a Sprint. It MUST be usable.

Definition of Done (DoD). The commitment for the Increment is the 'Definition of Done'. This is a formal description of the state of the Increment when it meets the quality measures required for the product.

When is it Done?. The moment a Product Backlog item meets the Definition of Done (e.g., code reviewed, tests passing, deployed to staging), an Increment is born.

Summary. Three Artifacts. Three Commitments. Maximum Transparency.

Pascual Vila

Frontend Instructor // Code Syllabus

Common Pitfalls & Errors

The Error //

Reporting an item as '90% Done' at the Sprint Review

Wrong: "The login feature is basically done, just needs tests and a code review."
Right: "The login feature isn't Done yet — it hasn't met the Definition of Done, so it's not part of this Sprint's Increment."

The Solution //

Scrum has no concept of partial completion. If a Product Backlog item doesn't meet the full Definition of Done, it isn't an Increment and can't be demonstrated or released — it simply returns to the Product Backlog. Agree on the Definition of Done up front so 'Done' is a binary, shared standard, not a personal judgment call.

The Error //

Treating the Product Backlog as a fixed requirements document

Wrong: "We signed off on this backlog in January, it can't change now."
Right: "We just learned users don't want feature X — the Product Owner re-ordered the backlog to reflect that."

The Solution //

The Product Backlog is emergent, not a frozen spec written once at project kickoff. It should be constantly refined, reordered, and rewritten as the team and the Product Owner learn more. Locking it down like a Waterfall requirements doc destroys the transparency the artifact is meant to provide.