Whose definition of done?
Here's a riff on the definition of done (DoD), and how it often only refers to a link in the larger value chain.
Of course, if you happen to work in a software product team, DoD is a valuable instrument. It will help decide whether a software increment is shippable. In other words, whether the software increment complies with the functional and non-functional requirements that have been set for it, and the generic quality standards for all software increments or specifically for this software increment.
Nothing wrong with that. Except that the increment still has to be shipped, configured and integrated with the other software increments and the rest of the system. And that the system not only has to be running but that users also have access to it. And that the users not only have technical access to the system but also know how to use it in their business context. And not only the use of the system but also the use of the information that the system provides them with. And not only that they use the information but also that they use it to achieve the desired business objectives. And that the users have support for use and application of the system and the resulting information.
So, depending on your scope of control, influence and concern, 'done' means
领英推荐
It also implies that the requirements for the software increment include criteria that support that the IT system is operational, the IT service available, the functionality used, the information applied, and the investment returned.
Finally, it begs the question who is responsible for each of these definitions of done, and how well these parties align their activities.
Advocatus Diaboli for Project, Program and Lean Portfolio Mgmt. I Trainer, Consultant, Assurance Consultant & Trusted Challenge Advisor | Maxpert & Peoplecert PRINCE2 Ambassador and SME
1 年Excellent take, dear Mark Smalley.Depending on the control focus this ultimately leads to benefit metrics resp. value (net-benefit) metrics such as conversion rate improvement, engagement rates etc. Totally tied to the business case the DoD should force us to think in those business terms...
ITIL Master | Agile Coach | DevOps Transformational Leader | ITIL & DevOps Ambassador | Helping Individuals & Organizations to Create, Deliver and Preserve VALUE
1 年Great! this explanation clearly separates the elements of the DoD which in some point interacts with the Acceptance Criteria (which also includes the Functional, Non-functional aspects but from a Customer's perspective I'd say). Thanks for sharing Mark.
????????/???????? ???????????? & ???????????? | ?????????????? ???????????????????????????? ???????????????????? | ???????????????? ???????????????????? & ???????????????? | ?????????????? ?????? & ????????????????????
1 年This is great. Thank you! Overall by establishing a clear DoD organizations can ensure that services are delivered according to agreed upon standards, meet customer expectations, and align with the overall IT service strategy and goals.