Abstract: Despite claims to the contrary, the need for governance does not disappear for agile projects. Your project sponsors have a right to know the status of the health and risk of their investments. But trying to blend traditional agile methods such as Scrum with traditional stage gate approaches can cause frustration for both project teams and their stakeholders. Disciplined Agile Delivery (DAD) provides straightforward and common sense ideas for applying governance in a lightweight fashion for agile projects. DAD has been adopted organization-wide in some very large companies and in many cases the primary motivations have been related to its hybrid method approach as well as the built-in governance that it provides.
In this talk Mark reviews the four DAD lifecycles along with their associated phases and milestones. He will explain which milestones are highly recommended vs those that are considered optional. He will show how a lightweight Vision statement created in Inception can be used as a governance mechanism for moderating uncontrolled change that often happens on agile projects.
Mark will share stories and tips about how to effectively apply these concepts to avoid late projects surprises. He will also review several examples of applying DAD governance such as how DAD was used to bridge the governance gap between an organization's Scrum teams and their corporate mandate of using PRINCE2.
Learning Outcomes: - Understand the mismatch between traditional and agile governance expectations
- Learn the four DAD lifecycles that support various approaches such as agile, lean, and continuous delivery
- Understand why DAD has phases and why they are valuable
- Learn the value of DAD's Vision statement as a mechanism for good governance
- Learn about the DAD milestones as well as where and when to apply them
- How to enhance your end of iteration demos to incorporate lightweight milestone reviews
- Contrast traditional governance metrics with some suggestions that are more applicable for agile projects
