Skip to main content

17 Things to Try on Monday Morning

... to do better Scrum.

In my Scrum Performance MasterClass Workshop, the participants reflect on how their teams and organisations do Scrum, compare how they do Scrum with Scrum 'by the book,' and create both a long term vision for improving their organization and a list of things they could start Monday morning to begin the improvement process right away.

Here's the list of things my participants identified to start doing on Monday after last week's MasterClass:
  1. Pairing: Two people work on each story. ( See 'Pair & Share, How We Do Sprint Planning 2')
  2. Review the Definition of Done in my project
  3. The Implementation Team, not the Product Owner or other manager, decides on how much work to accept in the Sprint.
  4. Improve the quality of the User Stories in my project
  5. Move testing from a separate group to the Implementation Team
  6. Hold a retrospective with the Implementation Team and Management
  7. Build awareness and acceptance for the Scrum mindset among our customers
  8. Recognize the impact of technical debt and start working to eliminating it
  9. Introduce the principle of Inspect and Adapt in management
  10. Recommit to doing Scrum well 
  11. Bring passion for doing things well back into the process
  12. Apply the Test Driven Development to process design
  13. Measure velocity instead of using it to drive Team commitments to the Product Owner
  14. Order books to learn more
  15. Create a company Agile library to help the curious find out about Scrum and Agile
  16. Use real (potential) customers and users as personae for creating user stories
  17. Look at Spotify as a role model for organizing and scaling my teams.
Gee, this list is a bit long for to do all at once. So pick one, maybe two (OK, three if the they are tiny changes) and start working there.

Better yet, this list was created for the people who created it. So reflect on how you do Scrum to create your own list! (Feel free to add your ideas in the comments!)

Comments

Popular posts from this blog

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …