1.
www.PairCoaching.net<br />how to make your retrospectives the of your agile process<br />Yves Hanoulle<br />

2.
Principles behind the Agile Manifesto<br />Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. <br />Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. <br />Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. <br />Business people and developers must work together daily throughout the project. <br />Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. <br />The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. <br />Working software is the primary measure of progress. <br />Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. <br />Continuous attention to technical excellence and good design enhances agility. <br />Simplicity--the art of maximizing the amount of work not done--is essential. <br />The best architectures, requirements, and designs emerge from self-organizing teams. <br />At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. <br />

3.
What is a retrospective<br />

4.
It’s not a post mortem<br />

5.
We are not in CSI<br />

6.
More like a checkup<br />

7.
More like a checkup...<br />

8.
Prime Directive<br /> Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.<br />At the end of a project everyone knows so much more. Naturally we will discover decisions and actions we wish we could do over. This is wisdom to be celebrated, not judgment used to embarrass.<br />

9.
Designing the stage<br />

10.
prepare<br />

11.
Who?<br />

12.
Room<br />

13.
Set a goal<br />

14.
Set the Stage (Check in)<br />

15.
First 5 minutes<br />

16.
Team Charter<br /><ul><li> Commit to enage when present

17.
Seek to perceive more then to be perceived

18.
Use teams especially when undertaken difficult or boring tasks

19.
Speak always and only when I believe it will improve the general result/effort ration

20.
Offer and accept only rational result-oriented behavior and communication

21.
Do now what must be done eventually and can effectively be done now

22.
Disengage from less productive situations

23.
When I cannot commit to the team charter

24.
When it is more important to engage elsewhere

25.
Seek to move forward a particular goal, by biasing my behavior toward action.

26.
Use the Core Protocols (or better) when applicable.

27.
Neither harm – nor tolarete the harming of –anyone for this or her fidelity to the team charter

28.
Never do anything dumb on purpose</li></li></ul><li>iLanguage<br />You screwed up <br />the build!!!<br />

29.
Absent people<br />

30.
Timebox<br />

31.
Stop Cards<br />

32.
Referee cards<br />

33.
Start on time...<br />

34.
Safety<br />

35.
ESVP<br />

36.
Gathering Data<br />

37.
Generate Insights<br />

38.
Identify Themes<br />

39.
Ask for help<br />

40.
Rescue<br />

41.
Decide what to do<br />

42.
Actions<br />

43.
Who will be driving these actions?<br />

44.
SMART<br />

45.
Close<br />

46.
Smells<br />

47.
answers come from the leader instead of the participants.<br />

48.
Only a few people participating<br />

49.
Everyone is always happy... <br />

50.
Nobody talks about the elephant<br />

51.
Hidden elephant...<br />

52.
People looking for silver bullet’s<br />

53.
Retrospectives in the team room<br />

54.
Too short retrospectives<br />

55.
Too many changes<br />

56.
Blame Game<br />

57.
Instruments<br />

58.
Resources<br />

59.
Exercise<br />Divide in groups of 3 people (of 3 different locations)<br />Pick up a retrospective Story<br />Design the retrospective (30 minutes)<br />

60.
Team 1<br />The very first retrospective of a new team<br />

61.
Team 2<br />A retrospective of a sprint where the team delivered only 60% of the features. This has been the situation for the last 6 sprints.<br />

62.
Team 3<br />This team is doing "scrum" for a year. They have never done a retrospective. You design their first retrospective<br />

63.
Team 4<br />This team had a great review, the customer invited the whole team to a restaurant with 2 stars in the michelin guide, this is the teams retrospective after that. The teams wonders if they actually need a retrospective at this moment.<br />

64.
Team 5<br />This team has been doing scrum for 3 years. The retrospectives have been dull the last 5 sprints. You need to bring back the energy of the team.<br />

65.
Team 6<br />The retrospectives of this team have been mainly ranting/complaining sessions about other people/teams in the company. Nothing has been comming out of these retrospectives . Some powerfull team members stay away from the last retrospectives.<br />

66.
Team 7<br />After a few painfull sprints, this team had a succesfull sprint<br />

67.
Team 8<br />This is the last retrospective with this team. Next week half of the team leaves.<br />

68.
30 minutes<br />