Agile Retrospectives - ASPE – SDLC Training

aspe.sdlc.com

Agile Retrospectives - ASPE – SDLC Training

Agile Retrospectives Unlocking the secrets of GREAT Agile Teams


Christy Clement Agile Trainer Agile Coach Trained hundreds of people in Agile methods Personally coached 15 different teams in variousindustries to successfully transition to an Agile approach Davisbase ConsultingWebsite: davisbase.org Developing People Who Develop Software.Email: christy.clement@davisbase.org Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden


Agenda‣ What is Agile? (for those who are new)‣ What is a Retrospective?‣ How to effectively conduct aRetrospective‣ Why does it matter‣ Your call to action‣ Q & A and Meeting CloseCopyright 2010 Davisbase LLC. Distribution without express permission is forbidden


Agile/Scrum in a NutshellScrum in 100 words (83 actually) • Scrum is an agile process that allows us to focus ondelivering the highest business value in the shortest time.• It allows us to rapidly and repeatedly inspect actual workingsoftware (every two weeks to one month). • The business sets the priorities. Teams self-organize todetermine the best way to deliver the highest priorityfeatures.• Every two weeks to a month anyone can see real workingsoftware and decide to release it as is or continue toenhance it for another sprint. Courtesy Mike Cohn, Mountain Goat SoftwareCopyright 2010 Davisbase LLC. Distribution without express permission is forbidden


The Anatomy of an Agile Approach"Scrum FlavorProduct VisionProduct ReleaseProductBacklogDailySprintBacklog2-4 Weeks(Sprint or Iteration)ProductIncrementProcess OverviewRetrospectiveCopyright 2010 Davisbase LLC. Distribution without express permission is forbidden


The Anatomy of an Agile Approach"Scrum FlavorProduct VisionProduct ReleaseProductBacklogDailySprintBacklog2-4 Weeks(Sprint or Iteration)ProductIncrementProcess OverviewRetrospectiveCopyright 2010 Davisbase LLC. Distribution without express permission is forbidden


The Anatomy of an Agile Approach"Scrum FlavorProductBacklogProduct VisionSprintBacklogDailyWe conduct aRetrospective at the2-4 Weeks(Sprint or Iteration)end of EVERY sprintcycle!Product ReleaseProductIncrementProcess OverviewRetrospectiveCopyright 2010 Davisbase LLC. Distribution without express permission is forbidden


One of the Agile PrinciplesAt regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden


What Are Retrospectives?‣ A forum used by the Agile team toinspect the preceding sprint so that theycan collaborate on what can be learnedfrom the experience‣ A working session meant to encourageeveryones participation‣ Resetting of teams expectations basedon new information‣ A demonstration that the team caresenough about their commitments toexplore how to improve‣ A retrospective is NOT...Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden


A Retrospective is Not...‣ A session spent complaining only about whatwent wrong.‣ We can discuss what went wrong, but this is only halfof the equation.‣ Focus on how others caused our failures.‣ We must explore how we contributed to our failures.‣ A session to seek who to blame.‣ Looking only to those factors outsideof the teams control.‣ It doesnt help‣ Blaming alone creates"a divided teamCopyright 2010 Davisbase LLC. Distribution without express permission is forbidden


Its Not a Post Mortem!‣ Improvement forums of the past(lessons learned and post mortems)waited until all was said and done todiscuss what happened‣ These discussions may haveproduced good information, but thetiming was poor‣ We should seek what we can learnfrom our experience within a timeframe where it can be put to useCopyright 2010 Davisbase LLC. Distribution without express permission is forbidden


Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden


PAST EXPERIENCES = FUTURE POSSIBILITIES


We are a team of people‣ People have personalities‣ Personalities favor different workingconditions‣ Our retrospective is to seek how our teamof personalities can work more effectivelytogether‣ We are not simply resourcesCopyright 2010 Davisbase LLC. Distribution without express permission is forbidden


Try referring to your family as a RESOURCE and see where that gets Copyright 2010 Davisbase LLC. Distribution without express permission is forbiddenyou!


How to Run an Effective RetrospectiveEstablish our goal for the forumElicit input, dutifully capturing foreveryones reviewCollaboratively draw conclusions fromthe data capturedDeciding to act upon the"conclusions drawnThe Playbook Making a team commitmentBased onEsther Derbys Approach 1. Set the Stage 2. Gather Data 3. Generate Insight 4. Decide What To Do 5. Close the Retrospective www.estherderby.com Always give credit where its due :)Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden


Establish Our Goal for the Forum!What are we here to do?‣ We must value ourexperience enoughto want to examineit authentically‣ Discuss with anintent to understandrelated causations,not for blame butfor improvement‣ We are not meeting tosimply satisfy Agileprocess requirements,we are here becausewe want to get better‣ Ask for every memberscommitment forparticipationCopyright 2010 Davisbase LLC. Distribution without express permission is forbidden


Getting Everyones Input‣ Focus on the team, not theproduct‣ Solicit everyones input on:‣ What worked well‣ What didnt work well‣ What impediments kept our team "from optimal operation & delivery‣ Do not vet any input, let it all flow‣ Ensure everyones participationCopyright 2010 Davisbase LLC. Distribution without express permission is forbidden


What Does All This Information Mean?‣ Our opportunity to look at common causes to issues‣ Encourage collaborative, free form discussion to arrive at teamconclusions‣ Determine if patterns in problems or"experiences exist‣ Have the team dig deep beyond"the usual suspects, usual thinking‣ Teams may only be able to address"1 or 2 prime candidates for decompositionCopyright 2010 Davisbase LLC. Distribution without express permission is forbidden


What Are We Going to Do Now?‣ Data alone does not drive true change.‣ This is the most important portion of the retrospective, andmust have collaborative participation.‣ Focus on those things that the team can influence.‣ This is the forum for moving from discussion to action, it isan essential part of the overall approach.‣ Allow the team to determine what the action steps"need to be, they need to own itCopyright 2010 Davisbase LLC. Distribution without express permission is forbidden


CLOSE THE FORUM ‣ Review what was decided upon by the team‣ Ensure that all action items are owned by the team or havespecific owners with clear acceptance criteria‣ Identify areas in which the next retrospective can be improved‣ Appreciate the teams effort to want to improve and then...‣ Everyone should commit to the team to improving in theareas that have been identified.Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden


Why We Should Care‣ Great teams dont start that way. Great"athletes dont start that way either.‣ Agile teams that dont invest in their own"improvement will experience the same"failures and disappointments over and over.‣ It takes time to get good at Retrospectives,"it is more than simply scheduling the time.‣ Once it become habit, and actions return"results, teams will not proceed without one.Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden


What’s Important to Remember?!Complete retrospectives at the conclusion of EVERY iteration.They are not optional.Lead by example. If you commit to making an improvement oraction, follow through. This builds team momentum.Be patient. Not all problems can be solved in just"one iteration. Give the team time and space.Retrospectives are not meant to solve all"problems, some issues need to be resolved"offline.Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden


Your Call To Action‣ Find experts that can point you inthe right direction. ‣ Recognize that training is theproper foundation on whichteams build. ‣ It takes time to get good atanything, including Agile andretrospectives, but the rewards arewell worth it. Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden‣ Getting started is easier than youmight think.


Your Questions, My AnswersNote: For those questions we do not have time to answer during the webinar,I will be providing a written response. Thanks to ASPE for allowing me to be here!Please connect with me on Christy Clement Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden


How to Claim Your PDU‣ Go to ccrs.pmi.org‣ Search for ASPE as a Registered Education Provider.Our number is 2161.‣ At the bottom of our details page, select"See Providers Activities‣ Find the activity and code stated by the ASPE moderatorduring the seminar‣ The seminars are typically a Category 3 for one PDUWebinar Code:WS120810Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden

More magazines by this user
Similar magazines