Produce Retrospective Report (Process Notes 6.2.2)

Your aim is to have as many people as possible read the retrospective report with interest. Design this report so that it captures people's attention and is easy to find one's way around:

• Write the report in clear, straightforward language.

• Avoid words whose only purpose is to provide bulk.

• Be honest.

• Use pictures to help with explanations.

• Include quotes from project participants.

• Maintain anonymity unless individuals have requested otherwise.

Here is a sample table of contents for a retrospective report:

Retrospective Report on Requirements Specification

Our project had successes and failures. This report shares our experiences so that you can profit from the successes and avoid the mistakes that caused the failures.

Contents

1. The most important things we learned

2. The history of the project (abridged)

3. The project objectives: Did we meet them?

4. The process we used: Did it work?

5. Communication: within the team

6. Communication: with the world

7. The tools we used and what we learned

8. How we tested our requirements

9. Management issues

10. Project reviews

11. Requirements issues

12. Design issues

13. Some things we did right

14. Why our faces are red

15. Actions to take

Diagram 6.3. Build a Requirements Filter