In most retrospectives, we´re using the plain „What went good? What went wrong?“ – technique via a roundtable, noting down the outcome of this, then start discussing possible solutions for the „wrong“ things, coming up with action items to solve them, decide to take the actions, and ask participants for their ROTI (Return of Time Invested).
Schlagwort: retrospective
Andreas Schliep (@andreasschliep) talked about how to test your organization, he started by telling about his experience about playing the ballpoint exercise, which is a kind of scrum-simulation, where the team has to do an exercise, then do a retrospective, and starts to iterate (and hopefully improve).
Here a quick list of articles I´ve read during the last month:
- GTAC 2010: Early Test Feedback by Test Prioritisation: Slides Video
- Share your vision with you employees to empower them
- A new blog for the new year: Testing with Vision
- Testing for Bug Bucks & Breaking The Rules
- Tester’s Pedal
- Exploratory Testing or Scripted Testing: Which Comes First?
- When A Bug Isn’t Really Fixed
- Recognizing Impediments
- Things you should do to sabotage your Scrum implementation
- Test Challenge: On the first software testing team…
- The History of Software Testing
- The Cost of Retrospectives at Large Animal Games
- Agiles Management: Delegation und Authorität/ Agile Management – Authority & Delegation
- Führen ohne Macht
- New Year’s Resolutions
- On Agile Misconceptions
- Definition of Done: A Reference
- Good enough, or perfect?
- Better Testers Keep Their Plates Spinning
- Elephants in the room: seven reasons why project risks are ignored
- Daily Stand-up Variations
- How Much Influence Should Testers Have?
Here a quick list of articles I´ve read during the last month: