Join Doug Rose for an in-depth discussion in this video Use the prime directive as a guide, part of Agile at Work: Getting Better with Agile Retrospectives.
- Like many Agile practices,…a good retrospective depends on a self-organized team.…The team needs to accept responsibility…for their improvement.…That's why Norm Kerth created a short retrospective mission…that he called the Prime Directive.…The Prime Directive should be taken very seriously.…Don't think of it like the original…Star Trek's Prime Directive.…The team shouldn't discard this directive…whenever it may cause problems.…Instead the Prime Directive is a pledge.…It's a shared understanding about how to work together.…Some facilitators even suggest reading out the directive…at the beginning of each retro.…
It's a little strange to see a team do this.…It looks like a pledge to the state of Agile.…If you get the team to do it, there is some evidence…that this reinforces positive behavior.…The Prime Directive states that,…"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,…
Watch and learn agile project management techniques to assess your project today, and get back on track for tomorrow. Find more courses on agile project management in the Agile at Work series on Doug's author page.
- Five phases of retrospectives
- Choosing an ideal meeting space
- Identifying issues and improvements
- Working with a distributed team
- Encouraging discussions
- Setting goals using SMART criteria
- Asking good questions
- Making team decisions
- Closing out an agile retrospective