Agile 102 Workshop Syllabus: Difference between revisions

From AgileMe
Jump to navigation Jump to search
Line 163: Line 163:
|
|
* [[Marshmallow Challenge]]
* [[Marshmallow Challenge]]
|-
| Scrum Roles
|
* Differences between traditional and agile roles
* Cross functional and self organising teams
|
* [[Scrum Roles Exercise]]
|-
|-
|[[Iterative vs. Incremental]] Release Planning
|[[Iterative vs. Incremental]] Release Planning

Revision as of 07:36, 23 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
  • 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

Agile 101 Part 2 Workshop Setup

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


Syllabus

Workshop Format

Here is a table of the learning outcomes from the workshop format and how it is to be run:

Topic Learning Objectives Activity
Team Definition
  • Team enablement, definition, purpose and identity
Agile Framework
Agile Roles
  • Differences between traditional and agile roles
  • Cross functional and self organising teams
  • Use of team and facilitator in the sessions
Sprints or Iterations
  • 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 or intent
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
Debrief
  • Reflection on the activities and the learning

Concept Centres

Here is a table of suggested concept centres mapped to the intended learning outcomes that can be used for teams to choose from as activities to be done during their sprints:

Topic Learning Objectives Concept Centre
Agile Manifesto
  • Principles and values of the Agile movement
Traditional vs Empirical control methods
  • Prediction vs experimentation
Scrum Roles
  • Differences between traditional and agile roles
  • Cross functional and self organising teams
Iterative vs. Incremental Release Planning
  • How to work with iterations and increments
Batch size and Flow
  • Limiting the work in progress
  • Working with constraints
Daily Scrum / Daily Standups
  • Inspecting progress towards the goals
  • Adapting in the moment
  • Self organising and self managing teams
Agile Estimation
  • Estimation and metrics techniques
  • Making decisions
Prototyping
  • Value Proposition
  • Testing Assumptions

See Also

References