Scott & Mark interviewed by InfoQ on Executive’s Guide to Disciplined Agile book
<<This book is for people with the courage to look at the bigger picture, because frankly the big picture tends to be very ugly in practice. It’s for people willing to consider all aspects of their organization and who realize that IT is a key enabler of business agility. It’s for people who realize that context counts, that everyone faces a unique situation and will be agile in their own unique way, that one process does not fit all. It’s for people who realize that, although they are in a unique situation, others have faced similar situations before and have figured out a variety of strategies that you can adopt and tailor – you can reuse the process learnings of others and thereby invest your energies into adding critical business value to your organization.>>
I was very happy to contribute to official review of this book. There are some few software related books that are unique by their content fundamental value, as: ”Refactoring” (Martin Fowler and collaborators), “Clean Code” & “Clean Coder” (Robert C. Martin), “Extreme Programming Explained” (Kent Beck). The new book by Scott W. Ambler and Mark Lines seems to be from the same category, being unique of its kind. The proposed “final destination”, the “Business Agility” it is not only a concept, but it is covered with very useful light and essential guidance. The book has a great and, in the same time, light-efficient coverage of the overall process aspects:
- Delivery (software development) process
- Agile IT
- Agile Enterprise
- Agile Transformation
- From Transformation to Continuous Improvement
Agile Enterprise: this is a first time when this concept is backup with a process guideline. One of the main and great ideas is to focus improvement on value streams (“creating, producing, and delivering a good or service to the market”).
Here are some great ideas from the book:
- The mindset is only the beginning
- Context counts: use DA context sensitive, goal driven guidance
- Choice is Good: More Agile & Lean Delivery Lifecycles
- DevOps: Architecting for DevOps
- DevOps: Developer-led operations (You build it …).
- DevOps: Address your DevOps technical debt – Automated regression tests, Clean code, Clean data, Operational and reporting infrastructure, Small Projects, Refactoring and others
- IT cannot be treated like a “black box.”. IT deserves a seat at the management table. IT must work collaboratively with the rest of the organization.
- IT Governance: Consider both the long and short term.
- Reuse engineering: fund reuse directly
- Product management: Rolling wave planning
- “Teal is the new Black” for Enterprises: Adaptive, Self-Organization. Cellular, living organism; Awareness, Fulfillment; Evolutionary purpose.
- Marketing: Customer discovery over static prediction
- Sales: Reward sales people for long-term, delighted customers.
- Finance: Fund three growth horizons (operational, entrepreneurial, venture)
- Contracts: Prefer incremental delivery contracts over big-bang contracts.
- Transformation: Continuous improvement – the true strategy is to become a learning, adaptive organization.
- Transformation: Becoming self-sufficient, moving from external to internal coaching.
- Business agility requires true agility across all of IT, not just software development
Happy to participate to comunity events and talks (organized by AgileWorks). I have presented the topic “Enhancing Clean Architecture – 2 n-dimensional layers“.
Here are the presentation slides.
On Wednesday, September 21 2016 we ran a webinar overviewing the latest version of the DA poster. A recording of the webinar can be viewed online from the DAC Webinars page and a PDF of the slide deck is posted on Slideshare entitled The Disciplined Agile IT Department. -Scott Ambler
You can find there the new DA poster, a link to a recent webinar , corresponding slide deck, and also responses to the questions from the webinar.
You can find the Scott Ambler description of the changes here:
In particular, we simplified the wording of the three principles (reduce technical debt, visualize workflow, multi-modal organizations) that we added to extend the original Manifesto for Agile Software Development. – Scott W. Ambler
and the updated manifesto here:
Mark Lines: 800+ Agile teams! Jon Smart describes Barclays worldwide Transformation with #disciplinedAgile
<<For us, our approach is based on Disciplined Agile (DA) as it is not one-size-fits-all, it is a goal-based, risk & value focused framework and is enterprise aware. It allows practices to vary as the context differs, with recommendations. >>
Disciplined Agile 2.x has new interactive map up and running. It is the only guidance that I know for:
- Lean Enterprise
- Disciplined Agile IT
- Disciplined DevOps
- Solution Delivery
You can also find a new DA poster here.
“PSM III – The distinguished level for Scrum mastery. This level proves that the individual has a deep understanding of the application of Scrum, Scrum practices and the Scrum Values. Those who pass PSM III also have the ability to apply Scrum in a variety of complex team and organizational situations.” – See more on Scrum.org site