a.   2-3 people work independently
b.   4-5 people break into 2 teams
c.    6 or more people go for a maximum size of 3 people per team
d.    Do not distribute any handouts yet

2.  Have teams draw a tree that has at least 4 roots, a trunk, at least 6 branches and leaves on the branches. Let 5 minutes pass and then distribute Handout-1. Once there is a lull in drawing go to next step.

3.   Have the team make a list of what they feel makes up being Agile; seed their list with: iterative and incremental development, scrum, Agile values, concurrent testing and continuous integration. Instruct the teams to document their compromises, negotiations and tradeoffs.

4.   Have them put their list of elements aside for the time being. Give the teams the list of items contained in Handout-2 to match to one of the four parts of their tree. Once again instruct the teams to document their compromises, negotiations and tradeoffs. Do not show Handout-3 to teams yet.

5.   Distribute Handout-3 and get back together as a group and have individuals share and discuss as an entire group the differences.

a.    Place the trees the teams drew in plain site for all to see
b.    Have a group discussion first about the differences between Handout-3 and their tree.
c.    Next compare and discuss list of elements from Step 3 and the list of items on Handout-2 and depicted on Handout-3.

Handout-1

Significance of Roots
They provide a solid foundation that will nourish and support the tree. In the case of being Agile and creative Agile thinking they represent the key foundational elements of being Agile.

Significance of Trunk
The roots absorb water and nutrients from the soil, which are then transported up the tree trunk. Just like the trunk is the part of a tree that connects the leafy crown with its roots people with their depth of knowledge and specific skill levels connects the fundamentals of what it means to be Agile to the actual doing the work and delivering commercial or operational value.

Significance of Branches
The branches represent common approaches/practices or key building blocks for doing something with a specific purpose in mind. An ordered set of assembled practices is a practice pattern (dare I say process).

Significance of Leaves
The leaves obtain water and nutrients from the roots through the trunk that are necessary for the manufacture of food from light energy (photosynthesis).   Food made in the leaves is then transported down to the roots and to other parts of the tree for growth.   The leaves represent results and the symbiotic relation between practices, people and the key elements of being Agile.

Handout-2

• Iterative and Incremental Development
• Continuous Integration
• Agile Manifesto: Values and Principles
• Concurrent Testing
• Test Driven Development
• Leading Change
• Scrum
• Lean
• People (Team/Individual)
• Four Level Planning
• Acceptance Test Driven Development
• Visual Modeling
• Daily Stand-Up
• Sprint Review
• Sprint Retrospective
• User Story Empowered Development
• Product Backlog
• Inspect and Adapt
• Requirements
• Use Cases
• Evolving Architecture s
• Charts: Velocity, Burn-up, Burn-down
• Evolving Architecture

Handout-3

Trackback(0)

TrackBack URI for this entry

Comments (2)

...
written by Russell, November 12, 2009

Rlsmall56,

You ask a great question.

I would be surprised if they came up with something "totally" different but I actually expect what they come up with to be different than the handout.

I would though start a dialogue with the team and have them share why they placed their labels where they did.

I would then based on what I thought I heard might offer them another perspective or point-of-view that then might influence them. Especially if they didn't have Iterative and Incremental Development as one of foundational elements or roots of being Agile.

The real value in doing this exercise is not the final result it is what the team learns about each others’ beliefs, understanding and perspective and the compromises they are willing to make for the good of the whole (team).

Most folks new to being Agile just do not know what they do not know so as the team's understanding of what it means to them evolves their depiction of what that looks like using the tree will evolve and change; which is how it should be.

• 
• +0
• 
• 

...
written by rlsmall56, November 12, 2009

That sounds good, however I think I am missing something. What if the group comes up with something totally different then the example because of the major differences?

• 
• +0
• 
• 

Write comment

Show/hide comment form

Name

Comment

smaller | bigger

Subscribe via email (registered users only)

Write the displayed characters

Add Comment Preview