9/5/13

1

RefineM    Virtual  Lunch  &  Learn  

NK Shrivastava, PMP, RMP, ACP CEO/Consultant - RefineM

Reflect  and  find  a  be,er  way!!  

Agile Retrospective

www.RefineM.com

Agenda 1.  What is Virtual Lunch & Learn 2.  Your expectations from this webinar – why you are here? 3.  Introduction - myself 4.  What is an agile retrospective? 5.  Objectives and benefits of retrospectives 6.  Steps to perform retrospectives 7.  Templates and examples 8.  Upcoming agile learning opportunities 9.  A short quiz – let us see what you learned J 10. Q & A

2

9/5/13

2

www.RefineM.com

RefineM’s Virtual Lunch & Learn This is a monthly webinar delivered during the lunch hour on the first Tuesday of every month. It’s designed to help you learn while you eat lunch, providing a relaxed environment to enhance your experience. The monthly webinars will cover a variety of hot Project Management topics.

3

www.RefineM.com

Your Expectations

4

What are your expectations from this webinar?

Or

Why you are here today?

9/5/13

3

www.RefineM.com

About Myself

5

www.RefineM.com

NK Shrivastava, PMP, RMP, ACP *  CEO/Consultant since Dec 2011

*  Agile Coaching/Adoption *  Project Management/ Process Improvement

Consulting and training *  Project Management Products (for PMs, Executives

and Agile Practitioners)

*  Board Member – SWMO Chapter since 2009

6

Helping organizations turn their project management capability into a competitive advantage

My professional journey b/f RefineM *  20+ years of Successful Project Leadership *  Led 100s of projects of all sizes, successfully *  Recovered many projects, saved millions of $ *  Implemented numerous process improvements *  Coached/mentored 100s of PMs, and some

executives

9/5/13

4

What is Agile Retrospective?

“An  Agile  Retrospec0ve  is  a  mee0ng  that  is  held  at  the  end  of  a  itera0on  in  the  Agile  So8ware  Development.  During  the  retrospec0ve,  the  team  reflects  on  what  happened  in  the  

itera0on  and  iden0fies  ac0ons  moving  forward.”  

“A retrospective is an opportunity for the participants to learn how to improve. The focus is on learning, not fault-finding.”

Norm Kerth

www.RefineM.com

*  “Learning  and  Development  do  not  necessarily  occurs  as  a  result  of  the  experience  itself  but  as  a  result  of  reflec0on  explicitly  designed  to  faster  learning  and  development.”  

B.  Jacoby  *  “For  many  of  the  team  members,  this  will  be  the  first  0me  they  consciously  think  about  the  process  they  use.”  

N.  Kerth  *  “Wisdom  comes  from  our  ability  to  understand  the  rela0onship  between  an  individual’s  work  and  that  of  the  en0re  team.  …  I  have  seen  whole  team  reflec0on  explain,  discover,  and  teach  so  much.  I  believe  that  there  is  no  beLer  way  to  improve  a  team’s  performance  and  Quality.”  

N.  Kerth  

Why Agile Retrospective?

9/5/13

5

www.RefineM.com

Basic outcome of Agile Retrospective: *  There  are  three  basic  ques0ons  asked  to  everyone  in  a  Agile  Retrospec0ve:  ü What  went  well?  ü What  did  not  go  well  and  could  be  improved?  ü What  ac0on  should  be  taken  to  improve?  

www.RefineM.com

*  The  primary  objec0ve  of  a  Agile  Retrospec0ve  is  learning,    

     Which  allows  a  team  to:  ü Correct  mistake,  some0mes  it  can  be  recurring  ü Gather  data  for  overall  assessment  ü Create  more  complete  and  accurate  report    ü Prepare  beLer  for  future  projects.  

What are the Objectives?

9/5/13

6

www.RefineM.com

When  the  team  conduct  a  good  retrospec0ve  following  posi0ve  outcomes  are  normally  expected:    

ü Ability  to  develop  and  deliver  so8ware  steadily  improves  ü Team  grows  closer  and  more  cohesive  ü More  transparency  among  team  members,  which  helps  team  members  understand  and  respect  issues  other  team  members  face  

ü Honest  and  open  about  success  and  failure  ü More  comfortable  and  flexible  towards  posi0ve  change.  

Benefits of Agile Retrospective

www.RefineM.com

*  The  primary  focus  should  always  be  learning,  not  finding  other  team  members  fault.    Team  member  should  never  lash  out,  aLack,  or    blame  another  team  member.  

 *  Team  member  should  get  along  well  and  should  not  take  this  as  an  opportunity  to  find  fault  and  blame  on  someone  they  don’t  like.  

 

Possible Contradiction

9/5/13

7

www.RefineM.com

1. Set the Stage

2. Gather Data

3. Generate Insights

4. Decision on Change/Action

5. Close Retrospective

Agile Retrospective Basic Process

www.RefineM.com

1. Set the Stage •  Establish focus for the

retrospective •  Share meeting plan • Working agreements • Make everyone speak •  Keep all the other

concerns aside for the time being

9/5/13

8

www.RefineM.com

2. Gather Data

•  Create a shared pool of data

•  Based on facts, not opinions

•  Consider objective and subjective experience

www.RefineM.com

3. Generate Insight • Understand systematic

influences and root causes

• Observe the pattern •  Think out of box •  Build shared awareness •  See system affects

9/5/13

9

www.RefineM.com

4. Decision on Change/Action

• Move from discussion to action

• Resolve on one or two actions

•  Focus on what can be achieved by the team

www.RefineM.com

5. Close Retrospective •  Reiterate actions and

follow-up •  Appreciate participants

contribution •  Think of better

retrospective

9/5/13

10

www.RefineM.com

Agile Retrospective Duration

This is for a general idea, time can vary based on different variable factors

If my sprint is this long….

My Sprint retrospective meeting should last…

One week 45 minutes

Two weeks 1.5 hours

Three weeks 2.25 hours

Four weeks 3 hours

www.RefineM.com

Retrospective in Agile SCRUM

9/5/13

11

www.RefineM.com

Sample Templates

www.RefineM.com

Sample Templates

9/5/13

12

www.RefineM.com

Sample Templates

www.RefineM.com

A Real Example

9/5/13

13

www.RefineM.com

*  The  Art  and  Science  of  Agile  –  On  25th  Sep  2013  ü 1-­‐day  in  person  class  ü Scheduled  for  25th  September  from  8:30am-­‐12:30pm  CT  ü In  Springfield,  MO  USA  ü Earn  8  PDUs  (if  you  need  them)  

*  Agile  CerJficaJon  (PMI-­‐ACP)  Exam  Prep  Class  –  From  5th  Nov  2013  onwards  ü 2-­‐day  class  delivered  in  4  sessions  of  4.5  hours  each  ü Scheduled  from  11/5/13  to  11/8/13  from  9:00am-­‐1:30pm  CT  ü Delivered  over  the  web  (you  can  aLend  from  wherever  you  are)  ü Earn  21  educa0on  hours  (needed  to  be  eligible  for  the  exam)  

More Agile Learning Opportunities

More info at http://refinem.com/news-and-events/

www.RefineM.com

When do you normally do a retrospective?

A.  Just before the start of a sprint, to prepare everything that is needed for the sprint

B. After the sprint review of each sprint, when you have all the inputs that is needed to reflect and decide upon actions. C. As a servant leader you only do it when the team ask for it.

D. The retrospective is a part of sprint review.

E. Between the planning game and the sprint review, so that you can do improvements during the sprint

Question 1

9/5/13

14

www.RefineM.com

When do you normally do a retrospective?

A.  Just before the start of a sprint, to prepare everything that is needed for the sprint

B. After the sprint review of each sprint, when you have all the inputs that is needed to reflect and decide upon actions. C. As a servant leader you only do it when the team ask for it.

D. The retrospective is a part of sprint review.

E. Between the planning game and the sprint review, so that you can do improvements during the sprint

Question 1

www.RefineM.com

Who should attend the retrospective?

A.  All team members

B. The Scrum Master and some of the team members

C. Everybody in the team, except for the product owners

D. Everybody who is attending the sprint review, to get us much feedback as possible

E. The product owner, team members and there managers

Question 2

9/5/13

15

www.RefineM.com

Who should attend the retrospective?

A.  All team members

B. The Scrum Master and some of the team members

C. Everybody in the team, except for the product owners

D. Everybody who is attending the sprint review, to get us much feedback as possible

E. The product owner, team members and there managers

Question 2

www.RefineM.com

What happens with the actions that comes out of retrospectives?

A.  They are given to the PM so that he can assign to the team

B. Team members will pick up the actions during the next sprint, to continuously improve there way of working C. The Scrum Master collect them and document them in report.

D. There shouldn't be much action coming out, as the sprint is already filled up with user stories. E. They are documented, and will be discussed in the next retrospective to check if they are finished

Question 3

9/5/13

16

www.RefineM.com

What happens with the actions that comes out of retrospectives?

A.  They are given to the PM so that he can assign to the team

B. Team members will pick up the actions during the next sprint, to continuously improve there way of working C. The Scrum Master collect them and document them in report.

D. There shouldn't be much action coming out, as the sprint is already filled up with user stories. E. They are documented, and will be discussed in the next retrospective to check if they are finished

Question 3

www.RefineM.com

__________________________________________________________________

NK Shrivastava, MBA, PMP, RMP, ACP CEO/Consultant, RefineM Nixa, MO 65714, USA nks@refinem.com, www.refinem.com http://www.linkedin.com/in/nkshrivastava @justrightpm

Questions?

32