Viewing Posts by Scott Ambler
We used to say that software is eating the world, but the fact is today software is the world. Gone are the days where IT could be treated like a utility, one that more often than not was outsourced in the belief that you needed to focus on your core competencies and IT didn’t make it onto that list. These days being competent at IT is mere table stakes at best, you need to excel at IT if you hope to become an industry leader. Today business executives must focus on disruptors, new competitors entering their market space using technologies in new ways. Becoming an agile business – an adaptive, responsive, and learning organization – is the true goal. Business agility requires true agility across all of your organization, not just software development, not just DevOps, and not just IT. There isn’t a single industry now that either isn’t dominated by agile businesses or isn’t under threat of disruption by new agile competitors.
The Disciplined Agile (DA) tool kit was created to apply agile in complex enterprise agile implementations. DA has been well received and implemented in organizations around the world. According to Gartner, Disciplined Agile is also the only available agile process explicitly allowing enterprises to customise agile for their unique enterprise challenges at both the organization and project levels. In their research report, Adopt Disciplined Agile Delivery for a Comprehensive and Scalable Agile IT Approach, Gartner reported:
In this article, we address several common questions executives have about Disciplined Agile (DA):
The Disciplined Agile (DA) tool kit provides straightforward guidance to help organizations streamline their processes in a context-sensitive manner, providing a solid foundation for business agility. The figure below provides a high-level overview of the scope of DA (click on the diagram to zoom in).
DA provides a foundation for business agility does this by showing how the various activities such as Finance, Portfolio Management, Solution Delivery (software development), IT Operations, Enterprise Architecture, Vendor Management and many others work together. DA also describes what these activities should address, provides a range of options for doing so, and describes the trade-offs associated with each option.
DA also provides a straightforward strategy for implementing value streams, overviewed in the following diagram (click on it to zoom in).
You can read more about DA in Introduction to Disciplined Agile.
There are several reasons why your organization should adopt the Disciplined Agile (DA) tool kit:
You can read more about why you should consider DA at Why Disciplined Agile?
DA is being used in numerous organizations, in a wide range of industries, around the world. You can see a list of a subset of the organizations using Disciplined Agile.
Yes. We have published several Disciplined Agile success stories with more on the way.
The answer to this question depends on what you're trying to achieve:
There are several ways that you can learn more about DA, and we recommend following the one(s) that seem best for you:
There are also several options for getting a team going with Disciplined Agile, we recommend considering all three:
Our fundamental advice is to start where you are, do the best that you can given the situation that you face, and always strive to get better. To succeed, there are three key concepts to understand:
Although every organization's journey is unique, we have found that at a high-level they all follow a similar 3-step transformation path:
When we think about assets we often think "financial assets" such as money, stocks, bonds, and other financial instruments. But of course there are many more types of assets than just financial ones, particularly when we consider it from the point of view of our organization.
We are currently in the process of evolve Disciplined Agile (DA)'s Reuse Engineering process blade, which had a very clear software focus to it, into a more robust Asset Management blade. Part of that effort is to rework the reuse categories, which we had originally adopted from the Enterprise Unified Process (EUP), depicted in Figure 1 into the asset categories of Figure 2.
As you can see, we've made several interesting changes:
We'd love to hear your feedback, particularly if you have ideas to improve Figure 2. Looking forward to reading your comments below.
This month, February 2021, marks the 20th Anniversary of the meeting from which the Manifesto for Agile Software Development, or more colloquially the Agile Manifesto, emerged. To celebrate this, the Agile20Reflect Festival is being held and PMI Chapters around the world are involved.
Here's what PMI chapters and individual members are doing:
I've likely missed a couple of events so please add a comment and I'll update as soon as I can. I hope you're able to attend some of these great sessions.
Also, I checked with the organizers and they've agreed to keep the ability to add an event to Agile20Reflect open until February 28th, so it's not too late!
We've have recently updated our thinking around the tactical scaling factors that we apply in DA to help understand the context faced by a team or organization. Figure 1 depicts the original scaling factors and Figure 2 the new scaling factors. Below we discuss what changed and how this can affect anyone taking a Disciplined Agile (DA) certification exam.
The changes we made were motivated by our experiences applying the scaling factors outside of IT teams. Originally these scaling factors were described by the Software Development Context Framework (SDCF) which we evolved into the Situation Context Framework (SCF) in late 2020. Here is what has changed:
As you can see in Scaling Factors we have made it clear that the exam will test you for knowledge about the original version for now (in Figure 1) and that when we update the courseware and exam to reflect this update we will let you know. In general our intent is that whenever material on the web gets ahead of what is being tested for that we'll make it clear that this has happened. More on this in a future blog posting.
February 2021 will be the 20th Anniversary of the meeting from which the Manifesto for Agile Software Development, or more colloquially the Agile Manifesto, emerged. To celebrate this, the Agile20Reflect Festival will be held around the world during the month of February. The festival is a collection of agile learning events around the world, where each event is run by a local group such as a PMI chapter. This is a great opportunity for PMI members to learn more about agile, and for PMI Chapters to host an event for their members as part of the festival.
This blog is organized into the following topics:
Good things to know:
Here is a list of event ideas that should get you thinking about what your chapter can do:
The above list is just a start. If you have other ideas that you'd like to share, please do so (see below).
This is what I suggest you do:
Time is short, so we need to collaborate to make this successful. Let's take advantage of the Disciplined Agile discussion forum on LinkedIn to collaborate. Here's how we can use it: