• AgileForNewManagersOutline

Links talking about panel discussions

• http://www.historians.org/Projects/GIroundtable/Discussion/Discussion4_2.htm

• http://blog.guykawasaki.com/2006/03/how_to_be_a_gre.html

Materials:

• Timer
• Noisemaker
• Flipcharts/easels/markers
• Blank 3x5 cards, blank paper, pens
• Prepared user stories (on cards), prepared project charter and release plan.

• Slides. (Including TeamPropertiesMindMaps, ExerciseInstructions)

• Camera - Take picture of each team with their flipchart, email to them or post on wiki, post at conference if we can find a way to print them out.

Handouts:

• TeamPropertiesMindMaps

• AssessmentQuestionsForTeamProperties

• TechniquesForTeamProperties

The New Outline

1. Introduction

   • Kay/Jeremy: Introduce each other

   • Kay: Talk about the tutorial

   • Jeremy: Exercise: Best team experiences/team characteristics that we want. Idea: Have them appoint a spokesperson. Have them discuss at their tables, their best team experiences. What are some of the characteristics of those teams that you enjoyed? Then have the spokesperson from each table come sit at the front for a panel discussion on what are the desirable team characteristics.(Have you ever run a panel? Does this sound interesting?)

2. The four team characteristics covered in this tutorial
   1. Shared Direction

      • Kay: show the mind map slides and talk about Shared Direction

      • Kay/Jeremy (need one of us to scribe) elicit "assessment questions" and "techniques" appropriate for Shared Direction

      • (no exercise for this characteristic)
   2. Delivering Results

      • Kay: show the mind map slides and talk about Delivering Results

      • Kay/Jeremy (need one of us to scribe): elicit "assessment questions" and "techniques" appropriate for Delivering Results

      • Jeremy: Iteration Planning exercise. Debrief/share. Idea: Farm project

   3. Collaboration

      • Kay: show the mind map slides and talk about Collaboration

      • Kay/Jeremy (need one of us to scribe): elicit "assessment questions" and "techniques" appropriate for Collaboration

      • Jeremy: Standup meetings exercise. Debrief/share. Idea: Quick draw

   4. Resilience

      • Kay: show the mind map slides and talk about Resilience

      • Kay/Jeremy (need one of us to scribe) elicit "assessment questions" and "techniques" appropriate for Resilience

      • Jeremy: Reflection workshop exercise. Debrief/share.

3. Conclusion

   • Kay: A few words in summary.

   • Jeremy: Exercise - Audience scenarios. (This is because I promised them "You'll also have the opportunity to describe current issues you face and discuss them with your peers and the presenters." http://agile2007.org/index.php?page=sub/&id=454) Idea: "Thank goodness you're here." The spokespersons come to the front once more to sit on the panel. We use a couple of the audience contributed situations/what are they concerned about at their work (Should we gather these ahead of time?) The panel discusses possible approaches to the situation, gets points for incorporating the team characteristics (shared direction, delivering results, etc.)

4. Finally

   • Kay: Agile wrap-up (Get ah-has)

deprecated old stuff

Outline

1. Introduction (30 min)
   • Gathering, seating
   • Introduce presenters. Perhaps some "straw polls" of the participants as a way of "introducing" them.
   • Describe format of session. Why are participants here?

   • ImportanceOfFrontLineManagers

   • Exercise: PictureIdealTeamExperience

   • Explain you want ParticipantScenarios by break time. A little bit of time here to think of them.

2. Tutorial Part I (60 min)
   • Concepts

     • The SecretOfManagement

   • Quick Exercise YourOwnSecretOfManagementEnvelope

   • Concepts
     • So how do you keep your team productive and deliver something of value every iteration?

     • The most important element you can affect is the team's morale TeamMorale

   • Quick Exercise: FactorsAffectingMorale

     • Morale is high when people have a clear picture of what needs to be accomplished

   • Exercise: UserStories Replaced by CustomerInvolvement

   • Concepts

     • Morale is high when people are successful. SmallWins

     • And when they are allowed to do a quality job ReasonableTimeExpectations

     • And not a lot of interruptions

   • Exercise: IterationPlanning (from XP)

   • Questions and answers/Reminder about ParticipantScenarios

3. Break
4. Tutorial part II (60 min)
   • Concepts
     • Morale is high when people are in a collaborative, helpful environment

   • Exercise: StandupMeetings (from Scrum)

   • Concepts

     • Morale is high when people are recognized for results (Not effort) RecognitionAppreciation

     • DoneMeansDone (from every Agile method)

     • No excuses

   • Exercise: IterationPlanningCompletionReport

   • Concepts
     • For a team to develop its own wisdom, it must reflect together.
     • Team members need to be comfortable with each other, with new situations.

     • Team members need to be comfortable with improvisation. ResilienceAndImprovisation

   • Exercise: ReflectionWorkshop (from Crystal)

   • Exercise: IterationPlanning (again)

5. Some more material, if time permits
   • Concepts

     • Slack PlanSomeSlack (from Lean Software Development)

     • Unpredictability CallOfTheWild

   • Exercise: SlackExercise ReleasePlanning

   • Concepts
     • Avoid the irreplaceable person problem
     • Team provides service even when any given individual is missing

     • HighAvailabilityTeam

   • Exercise: ExpertDefers

   • Concepts (If time)
     • Team members aware of what they're doing to provide real customer value.

     • CustomerResultsFocused

   • Exercise: VisibilityReport (from Zhon)

   • Questions and answers
6. Conclusion (30 min)

   • ParticipantScenarios

   • Continuation: Where do we go from here. Newsgroup? Blog?

   • Exercise: AgileWrapUp (Ah-has)

   • Final feedback on tutorial