|This section of the portal is for supporting the Disciplined Agile Value Stream Consultant Workshop (DAVSC), currently under development. Discussions on the pages here will take place on the Disciplined Agile LinkedIn group.|
Comparing Disciplined Agile and Scrum
Disciplined Agile Scrum is not merely Scrum with options. It is based on a different mindset. While Scrum is based on empirical process control – a combination of transparency, inspection, and adaption. Disciplined Agile, on the other hand, is based on flow, lean, Theory of Constraints, organizational development and human behavior. It enables choosing how to work based on the best way to meet the objectives of a role, practice, artifact, or event based on the context you are in.
Scrum’s lack of theory, however, requires its roles, events, artifacts and rules to be immutable because it presents no theory that can be used to choose a different way of working. This, however, often have teams persist in using Scrum’s core in situations where better practices exist.
While it may take a little more for a coach to learn all of the aspects of Disciplined Agile, its ability to create a fit for purpose start to teams makes it much easier to use and adjust. A good coach can provide options they see as appropriate. When a prescription is desired, one that is tailored for the team can be readily provided.
DA Scrum and Scrum Guide Scrum Are Based on Different Mindsets
The posts are written from the mindset of Disciplined Agile. This provides insights into further differences between Disciplined Agile and Scrum..
- The New Scrum Game. What Scrum would look like if it were based on Lean and the New New Product Development Game
- Is it simple? Depends upon what you mean by “it”
- The Difference Between Inspect and Adapt and Plan do Study Act (PDSA)
- Putting Lean-Kanban practices into Scrum is not the same as being Lean. Lean is starting to get popular so it’s being touted as being everywhere. But coming from a Lean mindset is a lot different than coming from an iteration mindset and throwing in a few Lean practices.
- Why contextualized prescriptions are so important
- How a little Lean theory can help those doing Scrum
- Eight Steps to Improved Scrum
- Improving Scrum by Attending to Flow, not Merely Using It
- The Question Isn’t ”Scrum vs. Kanban?” or Even “Scrum and Kanban?” But Rather “What Works?”
- Why Agile Coaches Need to Know Both Scrum and Kanban
- Scrum Masters Working with Mid-Managers
- Re-thinking ScrumBut and ScrumAnd
- How Lean Thinking Helps Scrum
- Contrasting the Daily Scrum with Kanban’s Daily Retrospective
- How you can use the insights of Disciplined Agile to improve your Scrum practices
- How Scrum creates ScrumBut and what to do about it
- How to Adopt Scrum Effectively
- Common Challenges Faced by Teams New to Scrum, Remedies to These Challenges, and Related FAQs
- Making Scrum Easier to Master With Disciplined Agile
- Making Scrum Easier to Master
- Using FLEX to Both Enhance and Simplify Scrum
Information about Scrum
The Risks of Scrum
- Framework Tunnel Vision
- The Trap of Scrum
- Is Scrum applicable for your team?
- Why Shu Ha Ri and Scrum Can Make for a Dangerous Combination. Suggesting people stick to practices until they get them to work can be risky if the practices are the wrong ones to be using.
- Why we must not settle for “difficult to master” in knowledge work
Why Scrum works and fails
- Challenging Why (not if) Scrum Works
- Challenging Why (not if) Scrum Fails. Understanding what causes failure can usually be used to facilitate success.
- Why Scrum Works and How This Tells Us When It Won’t
- VIDEO: Don Reinertsen: Shortcomings of Scrum + the good DNA in Scrum and Kanban
Go to Blog Organized by Topic