Agile 102 Workshop Syllabus: Difference between revisions

From AgileMe
Jump to navigation Jump to search
 
(25 intermediate revisions by the same user not shown)
Line 3: Line 3:
After the practical exercise in the [[Agile 101 Workshop Syllabus|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.
After the practical exercise in the [[Agile 101 Workshop Syllabus|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.
This workshop sees teams building a [[Scrum Artefacts|Product Backlog]] as a [[Story Mapping|Story Map]] and devising a release plan. Finally, the attendees run their release plan through a dice based simulation of [[Scrum Framework|Scrum]] and make release and scoping decisions to try to get the best possible outcome in the simulation.


===Materials===
==Materials==
* Large poster illustrating the Agile framework for the session such as [[Scrum Framework|Scrum]] for example
* Large poster illustrating the Agile framework for the session such as [[Scrum Framework|Scrum]] for example
* Flip chart paper and markers
* Flip chart paper and markers
Line 11: Line 11:
* A4 spare paper
* A4 spare paper
* Dice, enough for pairs of attendees to be able to throw up to 3 dice
* Dice, enough for pairs of attendees to be able to throw up to 3 dice
* [[Media:Metrics_Game.pdf|Release and Sprint burn down charts]]
* Visible timer to indicate the time left for the activities
* 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
* Music playlist and sound system to help play low level music whilst the teams are working
* [[Debrief Cards]]
* [[Debrief Cards]]
* Any materials for the exercises during the Concrete Practice section


===Setup===
==Setup==
The setup for the room with up to 16 participants includes:
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
* Large poster of the Agile framework to be used visible on the wall
* Several workstations arranged in cafe seating available for multiple table groups
* Several workstations arranged in cafe seating available for multiple table groups
Line 25: Line 24:
[[File:Agile_101_Workshop.jpeg|600px|Agile 101 Part 2 Workshop Setup]]
[[File:Agile_101_Workshop.jpeg|600px|Agile 101 Part 2 Workshop Setup]]


====Team Workstations====
==Connections==
Each team should have setup:
 
* Poster of their team name and sense of identity
* Flip chart paper for their Backlog or [[Scrum Artefacts|Product Backlog]] of work
* Flip chart paper for their Iteration or [[Scrum Artefacts|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:
Provide 3 hours for teams to orientate themselves to their project, conduct 4 iterations or [[Sprints]] and conclude with a reflection:
# Introduction and orientation of the approach - '''15 mins'''
# Introduction and orientation of the approach:
## Team self selection
## Team self selection
## Team name poster and workstation setup
## Team name poster and workstation setup
## Run through of the Agile framework poster and how the session is going to run
# 4 x iterations or [[Sprints]] - '''150 mins''':
## [[Sprint Planning & Product Backlog Refinement|Sprint Planning]] (if using [[Scrum Framework|Scrum]]) - Team decides how long
## Sprint or iteration to do the chosen activities - '''25 mins''' - Including Sprint Planning time (if used)
## Group [[Sprint Review]] as a [[Feature Fair]] to enable teams to interact, offer feedback and discuss what they have learned - '''5 mins'''
## [[Sprint Retrospective]] or other reflection for the teams to improve how they do things - '''5 mins'''
# Overall share back and reflection on the workshop with [[Debrief Cards]] if needed - '''15 mins'''
'''Total: 3 hours'''
===Activity Instructions===
====Part 1: Release Planning====
# Each team choose a desired scenario
# As a team review the scenario and the associated user journey
# Draw up sketches of the outcome using [[Crazy 8s Sketching]]
# Using dots or similar review the sketches and form a feature heatmap of the best features to include
# Draw a composite sketch of the best features
# Arrange the sketches and the user journey in the order of time as a horizontal row
# Brainstorm epics from the user journey and sketches to form the "back bone" of a [[Story Mapping|Story Map]]
# Decompose the epics into stories or tasks as the "ribs" of the story map
# Using [[Kano Analysis]] categorise the stories or tasks
# Estimate the stories or tasks using [[Affinity Mapping]]
# Re-form the story map into iterations with a goal for each iteration
# Add post-it notes down one side of the Story Map indicating Sprints 1-5 to form swim lanes for each of the Sprints
# Adjust the iterations between the Sprint swim lanes to form a release plan over the 5 Sprints
# Call over the facilitator to review and discuss
====Part 2: Simulation====
# As a team sum up the total number of story points for all of the items in the Product Backlog
# 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.
# 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.)
# 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.)
#:[[File:Metrics_Examples01.png|300px|Ideal Burndown]]
# 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.)
# '''DO NOT GO BEYOND SPRINT''' 1 at this point
# Working on Sprint 1, throw the dice. The total numbers from the dice throw now represent the work that was completed on day 1.
# 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.
#:[[File:Metrics_Examples02.png|300px|Actual Burndown]]
# 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.)
# The first Sprint has now been completed.
# 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.)
#:[[File:Metrics_Examples03.png|300px|Velocity Chart]]
# 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.
# On the Product Backlog mark off the items that were completed during Sprint 1 as “Done” with a bold tick or similar.
# 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.)
# 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.
# Call over the facilitator for review and discussion.
===Concept Centres===
===Syllabus===


Here is a table of suggested activities mapped to the intended learning outcomes of the session:
==Concepts and Concrete Practice==
# Start with building a Product Backlog and release plan together e.g. following the [[My Sweet 16 Birthday Party]] exercise
# Run through an agile simulation to put the release plan into play e.g. following the [[Kanban Simulation With Dice]] or [[Scrum Simulation With Dice]] exercise


{| class="wikitable"
==Closure==
!Topic
# Host an overall share back and reflection on the workshop with [[Debrief Cards]] if needed
!Learning Objectives
!Activity
|-
|Team Definition
|
* Team enablement, definition, purpose and identity
|
* [[Team Charter Exercise]]
|-
|Agile Framework
|
* [[Scrum Framework|Scrum]], [[Kanban Framework|Kanban]] and their application
|
* [[Build Your Scrum Framework]]
* [[Build Your Kanban Framework]]
|-
|[[Scrum Roles|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)]]
|-
|[[Empirical vs Predictive Control Processes|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|Agile Estimation]]
|
* Estimation and metrics techniques
* Making decisions
|
* [[Agile Metrics Workshop]]
|-
|}


==See Also==
==See Also==
* [[Agile 101 Workshop Syllabus]]
* [[Agile 101 Workshop Syllabus]]
* [[Scrum Framework]]
* [[My Sweet 16 Birthday Party]]
* [[Kanban Framework]]
* [[Kanban Simulation With Dice]]
* [[Scrum Master Coaching Syllabus]]
* [[Scrum Simulation With Dice]]
* [[Product Owner Coaching Syllabus]]


==References==
==References==
* [https://www.scrumalliance.org/ScrumRedesignDEVSite/media/ScrumAllianceMedia/Files%20and%20PDFs/Certifications/Foundational/Foundational_LearningObjectives.pdf Scrum Foundations Learning Objectives], accessed 21 Jan 2019
* [https://www.scrumalliance.org/ScrumRedesignDEVSite/media/ScrumAllianceMedia/Files%20and%20PDFs/Certifications/Foundational/Foundational_LearningObjectives.pdf Scrum Foundations Learning Objectives], accessed 21 Jan 2019

Latest revision as of 07:10, 28 June 2023


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 building a Product Backlog as a Story Map and devising a release plan. Finally, the attendees run their release plan through a dice based simulation of Scrum and make release and scoping decisions to try to get the best possible outcome in the simulation.

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
  • 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
  • Any materials for the exercises during the Concrete Practice section

Setup

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

  • Large poster of the Agile framework to be used visible on the wall
  • Several workstations arranged in cafe seating available for multiple table groups

Agile 101 Part 2 Workshop Setup

Connections

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:
    1. Team self selection
    2. Team name poster and workstation setup

Concepts and Concrete Practice

  1. Start with building a Product Backlog and release plan together e.g. following the My Sweet 16 Birthday Party exercise
  2. Run through an agile simulation to put the release plan into play e.g. following the Kanban Simulation With Dice or Scrum Simulation With Dice exercise

Closure

  1. Host an overall share back and reflection on the workshop with Debrief Cards if needed

See Also

References

Retrieved from "https://agileme.wiki/wiki/index.php?title=Agile_102_Workshop_Syllabus&oldid=1619"