Techniques for Keeping Retrospectives Effective and Fun
•
1 like•1,462 views
This document discusses retrospectives in Agile software development. It outlines the basic structure of retrospectives, including setting the stage, gathering data, generating insights, deciding what to do, and closing. It emphasizes the "prime directive" of understanding that everyone did their best given the circumstances. The document also presents various tools that can be used in retrospectives, such as timelines, silent retrospectives, and team radars. It concludes by advertising an upcoming Agile engineering conference and recommending a book on Agile retrospectives.
1 of 19
More Related Content
Techniques for Keeping Retrospectives Effective and Fun
2. The State of Retrospectives
@FadiStephan #AgileDC
3. Fadi Stephan
◊ 15+ years of experience in
software development
◊ Focused on Agile since 2006
– Agile readiness & maturity
assessments
– Agile coaching & mentoring
– Agile principles & software
engineering training
◊ Founder of the DC Software
Craftsmanship User Group
◊ Organizer of the DC Scrum User Group
@FadiStephan #AgileDC 3
4. Basic Retrospectives
◊+ /
– What went well?
– What should change?
http://www.flickr.com/photos/40055757@N00/1157649
4/
@FadiStephan #AgileDC
6. Setting the Stage - Prime Directive
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
@FadiStephan #AgileDC