Disciplined Agile Applied
by Scott Ambler
This blog explores pragmatic agile and lean strategies for enterprise-class contexts.
Recent Posts
Data Technical Debt: 2022 Data Quality Survey Results
Is Technical Debt A Management Problem? Survey Says...
You Think Your Staff Wants to Go Back to the Office? Think Again.
Contracts, Procurement, Vendors, and Agile
Disciplined Agile 5.4 Released
Categories
#AgileBeyondIT,
#ChoiceIsGood,
ACP,
agile,
Agile Alliance,
agile-manifesto,
book,
Business Agility,
Certification,
Choose your WoW,
Conference,
Context,
Continuous Improvement,
contracts,
COVID-19,
Data Management,
database,
DDJ,
Disciplined Agile,
Enterprise Agile,
estimation,
Fundamentals,
Governance,
GQM,
guesstimation,
http://disciplinedagiledelivery.com/principles/be-awesome/,
India,
information technology,
Introduction,
Kanban,
lean,
MANAGEIndia,
math,
MENA,
Metrics,
mindset,
News,
OKRs,
Organization,
People Management,
Planning,
PMO,
Portfolio Management,
Principle,
Project Management,
Quality,
Ranged Estimates,
Remote Work,
Scrum,
Security,
skill,
software,
Surveys,
Technical Debt,
Technical debt,
Terminology,
Transformation,
value stream,
vendor management,
VMO
Date
| One of the seven principles behind Disciplined Agile (DA) is Pragmatism. People are often surprised when we suggest that mainstream methods such as Scrum and Extreme Programming (XP) are prescriptive. But they are indeed. Scrum prescribes a daily stand-up meeting (Scrum) no longer than fifteen minutes to which all team members must attend, that teams must have a retrospective at the end of each iteration (Sprint), and that team size should not be more than nine people. These are all great ideas, but they don't apply to all situations. Similarly, Extreme Programming mandates pair programming (two people sharing one keyboard) and Test-Driven Development (TDD).
We are not suggesting that prescription is a bad thing, we’re merely stating that it does exist. Many agile purists are quite fanatical about following specific methods strictly. In fact, we have met many who say that to “do agile right” you need to have 5-9 people in a room, with the business (Product Owner) present at all times. The team should not be disturbed by people outside the team, and should be 100% dedicated to the project. However, in many established enterprises such ideal conditions rarely exist. The reality is that we have to deal with many suboptimal situations, such as distributed teams, large team sizes, outsourcing, multiple team coordination, and part-time availability of stakeholders.
The DA toolkit recognizes these realities and rather than saying “we can’t be agile” in these situations we instead say “let’s be as effective as we can be.” Instead of prescribing “best practices” DA instead provides strategies for maximizing the benefits of agile despite certain necessary compromises being made. As such, DA is pragmatic, not purist in its guidance – DA provides guardrails helping you to make better process choices, not strict rules that may not even be applicable given the context that you face.
SOURCE
This article is excerpted from Chapter 2 of the book An Executive’s Guide to Disciplined Agile: Winning the Race to Business Agility.
|
Posted on: October 07, 2019 12:00 AM
|
Permalink |
Comments (4)
|
"It is better to deserve honors and not have them than to have them and not to deserve them."
- Mark Twain
|