on project retrospectives - agile netið · 2010-10-02 · on project retrospectives björn brynjar...

18
On Project Retrospectives Björn Brynjar Jónsson PMO Process Lead 15 September 2010 1

Upload: others

Post on 20-May-2020

2 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: On Project Retrospectives - Agile netið · 2010-10-02 · On Project Retrospectives Björn Brynjar Jónsson ... Wikipedia on Agile development - held to look for ways to improve

On Project Retrospectives

Björn Brynjar Jónsson

PMO Process Lead

15 September 2010

1

Page 2: On Project Retrospectives - Agile netið · 2010-10-02 · On Project Retrospectives Björn Brynjar Jónsson ... Wikipedia on Agile development - held to look for ways to improve

The word RetrospectiveFrom Latin -“retrospectare” - looking back

New Oxford American Dictionary -“looking back on or dealing with past events

or situations…”

Wikipedia on Software Engineering -“to discuss what was successful.. what could

be improved”

Wikipedia on Agile development -“held to look for ways to improve the

process for the next iteration”

Page 3: On Project Retrospectives - Agile netið · 2010-10-02 · On Project Retrospectives Björn Brynjar Jónsson ... Wikipedia on Agile development - held to look for ways to improve

Project vs. Iteration Retrospectives

Iteration Retrospective Project Retrospective

Scope Last Iteration Whole Project

Length Typically 30-60 min Typically Half day – one and half day

Participants Dev team, (PO), Facilitated by: Project Lead (Scrum master)

Dev team, Internal Stakeholders, Management, External facilitator

Methods Typically by asking participants:• What worked well? • What can be improved?• Suggestions for improvement?

Menu of activities within three main parts: 1) Setting the stage why, how)2) The Past (what happened)3) The future (how can we improve)

Page 4: On Project Retrospectives - Agile netið · 2010-10-02 · On Project Retrospectives Björn Brynjar Jónsson ... Wikipedia on Agile development - held to look for ways to improve

Employing Iteration and Project Retrospectives

Iteration Retros are not enough• Scope too narrow for holistic solutions

• Assumptions seldom challenged

Betware employs Double Loop learning• Iteration and Project Retrospectives

• Post Project Customer Surveys

Our Conclusion• Project Retrospectives are essential!

• Allow the company to learn and grow

Page 5: On Project Retrospectives - Agile netið · 2010-10-02 · On Project Retrospectives Björn Brynjar Jónsson ... Wikipedia on Agile development - held to look for ways to improve

Project Retrospective Facilitator Group

Group of six Project Facilitators

• Their Purpose

– “to build and share knowledge & experience on how to facilitate a successful retro”

• Independent facilitator

How to facilitate Project retro?

Page 6: On Project Retrospectives - Agile netið · 2010-10-02 · On Project Retrospectives Björn Brynjar Jónsson ... Wikipedia on Agile development - held to look for ways to improve

Start with why

Page 7: On Project Retrospectives - Agile netið · 2010-10-02 · On Project Retrospectives Björn Brynjar Jónsson ... Wikipedia on Agile development - held to look for ways to improve

Conducting a Project Retrospective

7

Page 8: On Project Retrospectives - Agile netið · 2010-10-02 · On Project Retrospectives Björn Brynjar Jónsson ... Wikipedia on Agile development - held to look for ways to improve

Retrospective AgendaEvery project is different – agenda set up to fit project & purpose

Part I

The readying

• Build trust

• Establish safety

• Positive outcome

• Openness, Discovery, Curiosity

Part II

The Past

• Share stories

• Connect the pieces

• Understand what really happened

Part III

The Future

• Apply lessons learned

• Proposals for change

How does a typical agenda look like?

Page 9: On Project Retrospectives - Agile netið · 2010-10-02 · On Project Retrospectives Björn Brynjar Jónsson ... Wikipedia on Agile development - held to look for ways to improve

Retrospective Agenda

Page 10: On Project Retrospectives - Agile netið · 2010-10-02 · On Project Retrospectives Björn Brynjar Jónsson ... Wikipedia on Agile development - held to look for ways to improve

Exercises?

Page 11: On Project Retrospectives - Agile netið · 2010-10-02 · On Project Retrospectives Björn Brynjar Jónsson ... Wikipedia on Agile development - held to look for ways to improve

Develop Timeline

Page 12: On Project Retrospectives - Agile netið · 2010-10-02 · On Project Retrospectives Björn Brynjar Jónsson ... Wikipedia on Agile development - held to look for ways to improve

Develop Timeline - handouts

Page 13: On Project Retrospectives - Agile netið · 2010-10-02 · On Project Retrospectives Björn Brynjar Jónsson ... Wikipedia on Agile development - held to look for ways to improve

Picture It!

Page 14: On Project Retrospectives - Agile netið · 2010-10-02 · On Project Retrospectives Björn Brynjar Jónsson ... Wikipedia on Agile development - held to look for ways to improve

Retrospective Outcomes - closing the circle

“Formulate proposals for change”

• Who carries out proposals for change?

• How is the knowledge internalized within the company?

• The Teams • Quality Circle• PMO

• Product Office• Management team• CEO• Company Board?

• To summarize our results - worth every minute spent!

Page 15: On Project Retrospectives - Agile netið · 2010-10-02 · On Project Retrospectives Björn Brynjar Jónsson ... Wikipedia on Agile development - held to look for ways to improve
Page 16: On Project Retrospectives - Agile netið · 2010-10-02 · On Project Retrospectives Björn Brynjar Jónsson ... Wikipedia on Agile development - held to look for ways to improve
Page 17: On Project Retrospectives - Agile netið · 2010-10-02 · On Project Retrospectives Björn Brynjar Jónsson ... Wikipedia on Agile development - held to look for ways to improve

References

• http://retrospectivefacilitatorgathering.org/doku.php/2010_results

Page 18: On Project Retrospectives - Agile netið · 2010-10-02 · On Project Retrospectives Björn Brynjar Jónsson ... Wikipedia on Agile development - held to look for ways to improve

18