Agile Evolve: Difference between revisions

From AgileMe
Jump to navigation Jump to search
(Created page with "Category:Agile:WorkshopsCategory:Agile ==Introduction== This workshop is inspired by the work of Diana Larsen and James Shore and their [https://www.agilefluency.org/...")
 
Line 16: Line 16:
* [[:File:AgileFluencyModel.pdf|Agile Fluency<sup>TM</sup> Model]] downloadable from [http://agilefluency.org/ http://agilefluency.org]
* [[:File:AgileFluencyModel.pdf|Agile Fluency<sup>TM</sup> Model]] downloadable from [http://agilefluency.org/ http://agilefluency.org]
* [[:File:Agile_Evolve_Canvas.pdf|Agile Evolve Canvas]] one per team
* [[:File:Agile_Evolve_Canvas.pdf|Agile Evolve Canvas]] one per team
* [[:File:Agile_evolve_zone_cards.pdf|Agile Evolve Zone Cards]] one set per team


==Workshop Flow==
==Workshop Flow==

Revision as of 07:03, 22 November 2018

Introduction

This workshop is inspired by the work of Diana Larsen and James Shore and their Agile Fluency Project and is intended to provide a means for teams to determine what their next level improvements are, and also provide a bit of exposure with the growth opportunities possible.

Frustrated with attempts by some organisations to measure teams' maturity, this workshop takes an alternative team directed and non-assessment based approach, and allows them to determine how they want to grow and head towards mastery...whatever that is...

Learning Objectives

  • What direction do the team/organisation want to take towards mastery
  • Exposure to other growth areas that they might have not had previous exposure to

Timings

  • This workshop is expected to take 60 mins or so

Materials

Workshop Flow

Connections

  • Ask the team to look at the Agile FluencyTM Model and consider which Agile Fluency Zone is important to them and why

Concepts

  • Ask the team to pick up the Agile Evolve Cards and look through them considering which cards they are interested in

Concrete Practice

  • Ask the team to work through the Agile Evolve Canvas with the cards and considering the model

Conclusions

  • Finish up with a share back about their findings, what they want to do next, and why