Agile 102 Workshop Syllabus

After the practical exercise in the Agile 101 Workshop, this workshop focuses on developing teams' ability to apply some of their experiences to another simulation project, which needs a next level understanding of the Agile concepts.

This workshop sees teams selecting a project, developing an estimated and prioritised backlog of work, running a dice based simulation against it and making critical decisions to deliver the most value within the time and cost constraints.

Materials

• Large poster illustrating the Agile framework for the session such as Scrum for example
• Flip chart paper and markers
• Post-it notes and markers
• A4 spare paper
• Dice, enough for pairs of attendees to be able to throw up to 3 dice
• Release and Sprint burn down charts
• Visible timer to indicate the time left for the activities
• Music playlist and sound system to help play low level music whilst the teams are working
• Debrief Cards

Setup

The setup for the room with up to 16 participants includes:

• Concept centres for each activity on offer (including a poster, instructions, materials and equipment)
• Large poster of the Agile framework to be used visible on the wall
• Several workstations arranged in cafe seating available for multiple table groups

Team Workstations

Each team should have setup:

• Poster of their team name and sense of identity
• Flip chart paper for their Backlog or Product Backlog of work
• Flip chart paper for their Iteration or Sprint Backlog
• Agile 102 Instructions
• Table where to work

Timings & Run Sheet

Provide 3 hours for teams to orientate themselves to their project, conduct 4 iterations or Sprints and conclude with a reflection:

1. Introduction and orientation of the approach - 15 mins
   1. Team self selection
   2. Team name poster and workstation setup
   3. Run through of the Agile framework poster and how the session is going to run
2. 4 x iterations or Sprints - 150 mins:
   1. Sprint Planning (if using Scrum) - Team decides how long
   2. Sprint or iteration to do the chosen activities - 25 mins - Including Sprint Planning time (if used)
   3. Group Sprint Review as a Feature Fair to enable teams to interact, offer feedback and discuss what they have learned - 5 mins
   4. Sprint Retrospective or other reflection for the teams to improve how they do things - 5 mins
3. Overall share back and reflection on the workshop with Debrief Cards if needed - 15 mins

Total: 3 hours

Activity Instructions

Part 1: Release Planning

1. Each team choose a desired scenario
2. As a team review the scenario and the associated user journey
3. Draw up sketches of the outcome using Crazy 8s Sketching
4. Using dots or similar review the sketches and form a feature heatmap of the best features to include
5. Draw a composite sketch of the best features
6. Arrange the sketches and the user journey in the order of time as a horizontal row
7. Brainstorm epics from the user journey and sketches to form the "back bone" of a Story Map
8. Decompose the epics into stories or tasks as the "ribs" of the story map
9. Using Kano Analysis categorise the stories or tasks
10. Estimate the stories or tasks using Affinity Mapping
11. Re-form the story map into iterations with a goal for each iteration
12. Add post-it notes down one side of the Story Map indicating Sprints 1-5 to form swim lanes for each of the Sprints
13. Adjust the iterations between the Sprint swim lanes to form a release plan over the 5 Sprints
14. Call over the facilitator to review and discuss

Part 2: Simulation

1. As a team sum up the total number of story points for all of the items in the Product Backlog
2. Divide the total number of story points on the Product Backlog by 150. This is the number of dice to now request from the facilitator.
3. On the Release Burndown chart mark off the total number of story points on the vertical axis, and calculate the divisions on the vertical axis. (For example, if my total number of story points on my Product Backlog is 100, then I will put 100 on the top of the vertical axis and mark off 10 story points for each division on the vertical axis.)
4. Finally, draw the ideal burn down line from the total number of story points on the vertical axis to Sprint 5 on the horizontal axis. (This should provide a diagonal line from the total amount of work down to zero by Sprint 5.)

   

5. Repeat steps 1, 3 and 4 for the Sprint 1 Burndown chart, but this time only for the items in Sprint 1 on the Product Backlog. (The end result should be a total number of story points for Sprint 1 on the vertical axis, the vertical axis divided into equal divisions, and a diagonal line from the top of the vertical axis to day 5 on the horizontal axis.)
6. DO NOT GO BEYOND SPRINT 1 at this point
7. Working on Sprint 1, throw the dice. The total numbers from the dice throw now represent the work that was completed on day 1.
8. On the Sprint 1 Burndown Chart decrement the dice throw (work done) for day 1 from the total number of story points and mark how much work is remaining on the chart for day 1.

   

9. Repeat step 7 and 8 for each of the remaining 4 days for Sprint 1. (If the burndown chart shows that the work is completing ahead of time, bring in an additional item into Sprint 1 on the Product Backlog and mark off how much work is remaining with the new item.)
10. The first Sprint has now been completed.
11. Next update the Velocity chart with the total work completed for Sprint 1. (This should be around half way up the vertical axis, as future Sprints may deliver more or less work.)

    

12. Going back to the Release Burndown chart, decrement the work done for Sprint 1 from the total amount of work and mark how much total work is remaining on the chart after Sprint 1.
13. On the Product Backlog mark off the items that were completed during Sprint 1 as “Done” with a bold tick or similar.
14. Performing a Sprint Review adjust the release plan on the Product Backlog by rearranging the work planned for the future Sprints based upon the velocity. (Any items not completed in Sprint 1 should now be moved to a future Sprint.)
15. Repeat steps 5 – 14 for the remainder of the Sprints and adjusting the Product Backlog as you go to provide the best possible value with respect to the velocity.
16. Call over the facilitator for review and discussion.

Syllabus

Here is a table of activities to be done as part of the format of the workshop and based upon the structure of how it is to be run:

Topic	Learning Objectives	Activity
Team Definition	Team enablement, definition, purpose and identity	Team Charter Exercise
Agile Framework	Scrum, Kanban and their application	Build Your Scrum Framework Build Your Kanban Framework
Agile Roles	Differences between traditional and agile roles Cross functional and self organising teams	Use of team and facilitator in the sessions
Sprints, Iterations and Flow	Limiting the work in progress Working with constraints Agile events and activities	Use of 4 x Sprints or iterations
Sprint Planning / Iteration Planning	Generating impact with iterations Capacity planning	Each team plans their own sprints with a sprint goal Sprint Goal Template
Product Backlog Refinement	Adapting, learning and responding	Each team refines their own backlog as needed
Sprint Review / Iteration Review	Inspecting and adapting the iteration / Sprint output and outcomes	Teams obtain feedback from other team members in a Feature Fair
Sprint Retrospective / Kaizen	Inspecting and adapting the process Continuous process improvement	Teams perform their own retrospectives in one of the formats: Quadrant Retrospective Plusses & Deltas Retrospective Mood Thermometer Retrospective MDA Retrospective Sailboat Retrospective Story Cube Retrospective I

Here is a table of suggested activities mapped to the intended learning outcomes of the session:

Topic	Learning Objectives	Activity
Team Definition	Team enablement, definition, purpose and identity	Team Charter Exercise
Agile Framework	Scrum, Kanban and their application	Build Your Scrum Framework Build Your Kanban Framework
Agile Roles	Differences between traditional and agile roles Cross functional and self organising teams	Scrum Roles Exercise
Agile Manifesto	Principles and values of the Agile movement	Agile Manifesto Discussion (Small Group)
Traditional vs Empirical control methods	Prediction vs experimentation	Marshmallow Challenge
Iterative vs. Incremental delivery	How to work with iterations and increments	Backlog Strategy (Short Version) Prioritisation Exercise
Sprints, Iterations and Flow	Limiting the work in progress Working with constraints Agile events and activities	Sprints Exercise The Dice Game
Iteration Planning	Generating impact with iterations Capacity planning	Prioritisation Exercise
Product Backlog Refinement	Adapting, learning and responding	Prioritisation Exercise
Daily Scrum / Daily Standups	Inspecting progress towards the goals Adapting in the moment Self organising and self managing teams	Daily Scrum From Heaven
Sprint Review / Iteration Review	Inspecting and adapting the iteration / Sprint output and outcomes	Feature Fair
Sprint Retrospective / Kaizen	Inspecting and adapting the process Continuous process improvement	Quadrant Retrospective Plusses & Deltas Retrospective Mood Thermometer Retrospective MDA Retrospective Lego Retrospective Sailboat Retrospective Story Cube Retrospective I
Agile Estimation	Estimation and metrics techniques Making decisions	Agile Metrics Workshop

See Also

• Agile 101 Workshop Syllabus
• Scrum Framework
• Kanban Framework
• Scrum Master Coaching Syllabus
• Product Owner Coaching Syllabus

References

• Scrum Foundations Learning Objectives, accessed 21 Jan 2019