We released Disciplined Agile (DA) v5.3 earlier today, September 30th 2021. While there are several visible changes that we've made, discussed below, most of this release is "behind the scenes" in that we've updated descriptions of many techniques and added many new references that link to articles, blogs, or books describing a given technique.
The "visible changes" include updates to several process goals:
We also updated the following process blades:
It is important to note that for the DASM and DASSM exams that we are still testing you against the DA 5.0 version of the model.
We recently released the 5.2 version of the Disciplined Agile (DA) tool kit, and in that release we added three new process goals: Intake Work, Organize Metrics, and Measure Outcomes. The focus of this posting is the Measure Outcomes process goal, the goal diagram for which is posted in Figure 1.
Figure 1. The Measure Outcomes process goal diagram (click to enlarge).
The Measure Outcomes process goal describes potential improvement outcomes, or improvement goals, and suggests potential metrics to measure progress against those outcomes. Disciplined Agile doesn't prescribe what to measure, that would be naive because every team is unique with its own priorities and desired outcomes.
All of the potential outcomes in Figure 1 are important. However, you will want to focus on a subset at any given time, and that subset is likely to evolve as your improvement focus evolves. Context counts.
We recently released the 5.2 version of the Disciplined Agile (DA) tool kit, and in that release we added three new process goals: Intake Work, Organize Metrics, and Measure Outcomes. The focus of this posting is the Organize Metrics process goal, depicted in Figure 1.
Figure 1. The Organize Metrics process goal diagram (click to enlarge).
As the name implies, this process goal describes strategies to organize the metrics approach within your team. This strategy will be driven both by your team's culture and skills as well as the needs of your stakeholders - your metrics will likely need to "roll up" to the program or portfolio level.
Your metrics strategy will focus on several important questions:
Where this goal focuses on how to measure, the Measure Outcomes goal describes what to potentially measure.
We recently released the 5.2 version of the Disciplined Agile (DA) tool kit, and in that release we added three new process goals: Intake Work, Organize Metrics, and Measure Outcomes. The focus of this posting is the Intake Work process goal.
Intake Work: Added
Figure 1 depicts the process goal diagram for Intake Work (see How to Read Process Goal Diagrams). This is how a team pulls in work from their "upstream" stakeholders. The incoming work is examined and if ready it is prioritized and put on the team's work backlog. We introduced this process goal because we wanted to have a cohesive source of process information capturing the issues around a common activity that is critical to your team's success.
Figure 1. The Intake Work process goal diagram (click to enlarge)
To be effective at intaking work, we need to consider several important questions:
Address Changing Stakeholder Needs: Refactored
Part of the development of Intake Work was the refactoring of Address Changing Stakeholder Needs which previously captured several decision points that focused on intaking work and several on exploring stakeholder needs. Figure 2 depicts the updated goal diagram. Important changes include:
Figure 2. The Address Changing Stakeholder Needs goal diagram (click to enlarge)
One of the mantras of the agile community is that you need to "be agile," that you need to adopt an agile mindset. Agilists will often point to the Manifesto for Agile Software Development, commonly referred to as the Agile Manifesto, as a good starting point to understand this mindset, which it is. Other mantras within the agile community include respecting others and having a safe environment that embraces diversity. All wonderful ideas, but what do you do when they collide with one another?
The Disciplined Agile Mindset
Figure 1 depicts the Disciplined Agile (DA) mindset, which is captured in the form of principles, promises, and guidelines. Disciplined agilists believe in the DA principles, so we promise to adopt these behaviours and follow these guidelines when doing so. Where the Agile Manifesto addressed the environment faced by software developers 20 years ago, the DA mindset addresses the environment faced by organizations today. The DA mindset reflects our learnings over these past 20 years, adopting great ideas from a wide range of sources, in particular ideas around lean and flow, to describe concepts that enable enterprise agility.
Embracing Different Mindsets in the DA Tool Kit
One of the promises of the DA mindset is to create psychological safety and embrace diversity. Interestingly, when you do that you soon realize that people often have very different mindsets and that this is a very desirable thing. Yes,we want people to embrace an agile mindset so that we all share a similar point of view, but that's only one of many points of view. There are still noticeable differences between the way that you approach something and the ways that others do, even when everyone involved has an agile mindset. This happens because we are all unique people with unique experiences and backgrounds, and as a result you have other points of view than just the agile mindset.
I'm sure that you've noticed that finance people have a different perspective than people from marketing, whose perspective differs from data management professionals, which is different yet again than research and development people, and so on. Each business function tends to attract, and then reinforce, people of a certain mindset. Some people find legal work incredibly interesting, whereas others find it spectacularly boring. To each their own.
This is where it gets interesting. Remember that DA is a tool kit that supports improvement across all aspects of your organization, not just software development. One aspect of the architecture of the DA tool kit is that we've captured the different business functions within your organization as process blades, which in turn are described in terms of mindset, people, flow, and practices. Process blades include Finance, Strategy, Legal, Marketing, Security, IT Operations, Portfolio Management, and many more. Regarding mindset, for a given process blade, we extend the base DA mindset with philosophies that are applicable to that process blade. For example, Figure 2 depicts DA's People Management (Human Resources) mindset and Figure 3 DA's Security mindset.
There are several important points to this strategy:
Just like one process does not fit all situations, one mindset doesn't either. The Disciplined Agile (DA) tool kit explicitly embraces mindset diversity. Do you?