Disciplined Agile

The recording of my 1-hour InformationWeek webcast on DAD is available here:

https://event.on24.com/eventRegistration/EventLobbyServlet?target=registration.jsp&eventid=482700&sessionid=1&key=44991426F6D07634F67A0321147EEA90&sourcepage=register

There are some differences as well as some similarities when comparing agile adoption to agile transformation.  Which does the DAD book address?  One or the other, or both?  I know that I have my opinion, but I am interested in yours.  Add your comments and let us know what you think.  Then we can discuss.

I think that this blog has been quite successful in getting the word out about Disciplined Agile Delivery (DAD) and describing key aspects of the toolkit in advance of the book being released.  However, now that the book is out, it makes sense to evolve the blog into a forum for deeper discussions about DAD.  Scott and I would also like to use it as a medium to answer detailed questions about anything from the book.

Anyone who supports DAD is encouraged to become a contributor to be able to blog a new topic for discussion.  If you wish to become a contributor, send me a note at [email protected]

If you don’t wish to become a contributor directly but have a DAD question, send the question to me and I will post it for discussion.  Thanks!

As you can see from the above diagram, the primary roles of Disciplined Agile (DA) teams are similar to those of Scrum.  In Scrum, the product owner decides what will be built and in what order.  In DA we recognize that architecture is a key source of project risk and someone needs to be responsible for ensuring the team mitigates this risk.  As a result, DA explicitly includes Agile Modeling’s role of architecture owner. The architecture owner is the person who owns the architecture decisions for the team and who facilitates the creation and evolution of the overall solution design.  The person in the role of team lead will often also be in the role of architecture owner, assuming they have the skills and capacity to fill both.  This isn’t always the case, particularly at scale, but it is very common for smaller agile teams.

The responsibilities of the architecture owner include:

• Guiding the creation and evolution of the architecture of the solution that the team is working on.  Note that the architecture owner is not solely responsible for the architecture, but that they lead the technical discussions.
• Mentoring and coaching other team members in architecture practices and issues.
• Working closely with the Enterprise Architecture team, and often being a member of it, to understand and evolve the architectural direction and standards of your organization.
• Ensuring that the team adheres to the architectural direction and standards of your organization.
• Understanding existing enterprise assets such as frameworks, patterns, subsystems and ensuring that the team uses them where appropriate.
• Ensuring that the solution will be easy to support by encouraging good design and refactoring to minimize technical debt.
• Ensuring that the solution is integrated and tested on a regular basis, ideally via the practice of continuous integration(CI).
• Having the final say regarding technical decisions, but they try to avoid dictating the architectural direction in favor of a collaborative, team-based approach. The architecture owner should work very closely with the team lead to identify and determine strategies to mitigate key project technical risks.
• Leads the initial architecture envisioning effort at the beginning of the project and supports the initial requirements envisioning effort (particularly when it comes to understanding and evolving the non-functional requirements for the solution).

One of the key reasons for having this role in DA is that the architecture owner, like the product owner, has a say in work items that are added and prioritized in the work item list (backlog in Scrum parlance).  While business value is certainly a prime determinant of priorities, completing work related to mitigating technical risks is also important.  Additionally, in DA the aim is to deliver consumable solutions, not just working software.  As such, sometimes it is necessary to add work items that are technical in nature, for example related to error logging/monitoring.  Or perhaps work items need to be added to improve the continuous integration and deployment processes.

We have found that the concept of having both product and architecture owners ensures that the solution addresses both functional and quality requirements such as usability and supportability adequately.  In fact, on my current project, I worked with the product and architecture owners to negotiate their priorities such that the iteration underway includes not only a selection of high priority stories, but also a set of technical work items related to hardening the solution in preparation for entering the Transition phase of delivering the solution to the stakeholders.  Without a specific role of architecture owner, it can be difficult to escalate important technical work into the work item list.  As a result it is often done subversively without the knowledge of the product owner which is not a healthy practice, or worse it never gets done resulting in a poor quality solution.

Scott has written a good article that describes the architecture owner role in more depth.  You can view it here.

We are thrilled to confirm that our new book “Disciplined Agile Delivery:  A Practitioner’s Guide to Agile Software Delivery in the Enterprise” will be launched at the IBM Innovate conference in Orlando June 3-7.  It will be a busy week with the following events planned:

Scott will be co-delivering the Agile Transformation track keynote on Tuesday morning with Scott Rich, the development leader of the Jazz team. That afternoon he will be a participant at the Agile and Systems goldfish bowl. Wednesday morning Scott will be delivering his Disciplined Agile Delivery and DevOps talk and then in the afternoon giving an overview of Agile Modeling and Documentation strategies. Throughout the conference Scott will be meeting with customers, contact your IBM sales rep if you want to organize such a meeting, and doing several press interviews.

On Wednesday Mark will be speaking on “Disciplined Agile Delivery:  Adoption in the Trenches”.  On Monday he will be on the “Agile Coaching 101 Panel” with agile/lean thought leaders such as Mary Poppendieck.  Mark will also be at the Canadian reception Monday night at Blue Zoo.

Mark & Scott will also be doing a book signing on Wednesday at the bookstore.

If you miss the signing and want a book signed, try the Agile Transformation Zone in the Exhibit Hall.  There is a good chance that you will find us there, comparing notes with other agilists and discussing the challenges of disciplined agile adoption in the enterprise.

It promises to be a fun week, with the party at Sea World and the band Foreigner playing.  We hope to see you there!