Agile 102 Workshop Syllabus: Difference between revisions
No edit summary |
|||
Line 46: | Line 46: | ||
'''Total: 3 hours''' | '''Total: 3 hours''' | ||
===Activity Instructions=== | |||
# 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 | |||
===Concept Centres=== | |||
===Syllabus=== | ===Syllabus=== |
Revision as of 04:54, 20 May 2022
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
- 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:
- Introduction and orientation of the approach - 15 mins
- Team self selection
- 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 (if using 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
- 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 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
Concept Centres
Syllabus
Here is a table of suggested activities mapped to the intended learning outcomes of the session:
Topic | Learning Objectives | Activity |
---|---|---|
Team Definition |
|
|
Agile Framework | ||
Agile Roles |
|
|
Agile Manifesto |
|
|
Scrum Values |
|
|
Traditional vs Empirical control methods |
|
|
Iterative and Incremental delivery |
|
|
Sprints, Iterations and Flow |
|
|
Iteration Planning |
|
|
Product Backlog Refinement |
|
|
Daily Scrum / Daily Standups |
|
|
Sprint Review / Iteration Review |
|
|
Sprint Retrospective / Kaizen |
|
|
Definition of Done |
|
|
Artefacts |
|
|
Agile Estimation |
|
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