Join Doug Rose for an in-depth discussion in this video Understanding the LeSS diagram, part of Enterprise Agile: Growing Scrum.
- Like many other enterprise agile frameworks, large-scale scrum, or LeSS, has many diagrams to help explain how everything fits together. You can certainly go through this course without downloading any of the diagrams, but if you have access to a printer, these graphics can really help get a sense of the big picture. You can download them freely from the LeSS website. If you visit their site, try to get the PDF versions of their diagrams. You can view all these graphics on one page when you click on the link for Resources, and then Graphics, and finally, click on Website Graphics.
The graphics that will be the most helpful as you go through the course are The LeSS Complete Picture, LeSS Principles, LeSS Framework, Sprint Planning, Product Owner Relationships, Product Backlog Refinement, Scrum Master Focus over Time, Potentially Shippable and Definition of Done. If you only printed out one of these, then you might want to start with the PDF of the LeSS Framework. Just looking at it gives you a sense of how LeSS approaches enterprise agile.
It's a friendly little image, and everyone seems happy in their enterprise agile world. It's almost like the map you'll see in an amusement park. When you look at it, it's tempting to try and find a place for boardwalk fries or glazed frozen yogurt. Like an amusement park, the diagram is designed with a beginning and an end. You'll move through the map as you move through your sprint. Large-scale scrum has two levels of sprint planning. Near the entrance, there's Sprint Planning 1 and Sprint Planning 2. They're stacked on top of each other.
When you're done with sprint planning, you can start to move over into the bottom of the LeSS diagram. It's almost like the main pavilion of your park. It's here where most of your work gets done. This is the bulk of the time in your sprint. Your team is happily gathered near the task board to create their sprint backlog to start their work. The main pavilion is split up into three different traffic lanes. Each of these lanes represents one scrum team. You're already getting a sense for how large-scale scrum organizes their teams.
You have one product owner that hovers over all the teams. That shows that you can have one product owner providing work for several teams. Double-ended arrows show how you use daily meetings as a way to coordinate work between the teams. At the very end, you see another stack of meetings, just before you exit the sprint. On the very top, you'll see the sprint review meeting. This is where each team demonstrates their work. Before you finish the sprint, each team goes through a retrospective.
There, they focus on areas to improve. Then, all the teams get together with the scrum masters and product owners and run an overall retrospective. In this meeting, you'll look for much broader process improvements. When all that's complete, you have your potentially shippable product. At this point, you can exist the LeSS amusement park and start it all over again in the next sprint.
- Descaling enterprise agile
- Defining Larman's Laws and LeSS principles
- LeSS product owner and scrum master
- Growing Scrum
- Defining "done"
- Organizing a sprint review
- Organizing an overall retrospective
- Approaching key challenges