“Wrap Up the Iteration”
- Agile team delivers working software at the end of the iteration – demonstrate to the customers and get their feedback.
- Having testers conduct the ’Iteration Review’ is a common practice as they’ve usually worked on all the stories. The Scrum Master, programmers or testers could demonstrate the new features – It is recommended to rotate this honor.
- Retrospectives are an excellent place to start identifying what and how you can do better.
- Start, Stop, Continue technique – Discussing What went well, What did not go well and what we can start doing to help.
- Write task cards for actions to be undertaken to implement the steps
- At the end of the next iteration, take a checkpoint to see if you improved
Retrospectives are a simple and highly effective way for teams to identify & address issues. The retrospective meeting is a perfect opportunity to raise testing-related issues. Bring up issues in an objective, non-blaming way.
Make sure your team takes at least a little time to pat itself on the back and recognise its achievements.
Even Small Successes deserve a Reward.
Many agile teams have trouble taking time to celebrate success.
Have a weekly fun gathering or team games.
- For big milestones such a big release or achieving a test coverage goal, the whole company can have a party to celebrate, bringing in catered food or go out.
- It is also important to celebrate individual successes. A ‘Shout-Out Shoebox’ – is a great idea to recognize the value different team members contribute.
- Taking time to celebrate successes lets your team take a step back, get a fresh perspective, and renew its energy so it can keep improving your product, giving team members a chance to appreciate each other’s contributions. Don’t fall into a routine where everyone has their head down working all the time!
- Take advantage of the opportunity after each iteration to identify testing- related obstacles, and think of ways to overcome them.