|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.|
This page is curated by Al Shalloway.
This page is designed for three different roles:
- a person making a decision on which flavor of Scrum to pursue for their organization
- a Scrum master
- teams doing Scrum
Every topic will be of value for each role but they are marked accordingly for those who want to focus on their role.
The latest Scrum Guide says:
- Simple to understand
- Difficult to master
I have never liked these statements. For one, it sounds like a gutsy way to justify having a framework that’s hard to use. But just as important, having done Scrum since 2000, I would suggest that Scrum is often easy to master. The question is why is it sometime difficult to master and sometimes easy to master. My experience is that when Scrum is used by a team for where it was originally designed (creating new products – see The New New Product Development Game) it is a good framework and easy to master.
It has often been a good framework for teams to use for other purposes, but usually easier when teams were more experienced. There is a correlation between Scrum being easier to master and:
- cross-functional teams are present
- the team is building a new product
- the individuals are experienced in Flow, Lean and/or Kanban
- the individuals involved are closer to early adopters than to laggards using the Crossing the Chasm terminology
Scrum can be difficult to master when these aren’t present. The reasons for this is:
- Scrum is not fit for purpose everywhere
- Scrum provides little insights on how to transition an organization to meet it’s requirements (it assumes the people using it will figure this out)
This guide is designed to make Scrum easier to master (even if what you are mastering is not Scrum Guide Scrum).
Background and How to Start (optional)
This section is intended for someone considering how to start with Scrum. There are two main options today – Scrum Guide Scrum (Scrum Alliance, Scrum.inc, Scrum.org) and Disciplined Agile Scrum. These are short posts that will provide you insights on which is better for you.
- Why we must not settle for difficult to master in knowledge work
- Two ways to Start with Scrum
- Determining if Scrum is applicable to your team.
- Scrum as Example
- Why You Want to Choose an Agile Coach in an Agile Way
- When and how to start with Classic (Scrum-Guide) Scrum
Practices / Concepts to Introduce to the Team
- Attend to delays in your system (“Just in time”)
- Create a focus on finishing . Some people attempt to manage WIP via WIP limits. It is usually easier and more effective to create a focus on finishing. Completion exists at many levels: tasks, stories, features, and MBIs.
- When done with a task, look to finish another task in the same story.
- When done with a story, look to finish another story within the same feature.
- When done with a feature, look to finish a feature within the same MBI. This focus quickens the rate of feedback, both increasing quality and efficiency.
- Understand the concept of the MBI
Things to Know
- A Minimal Set of Concepts All Agilists Should Know
- Improving Scrum by Attending to Flow, not Merely Using It
- When Is Theory Useful?
How to Learn Scrum
If You’re Already Use Scrum