This is a short introduction presentation for the PMOZ conference in Sydney later this year.

1. Requirements = Scope Project Performance information Better and Faster with Requirements Traceability. Craig Brown PMOZ Proposal 2011

2. 3 learning outcomes

3. Requirements drive scope Unstable requirements drive unstable scope. Unstable requirements are almost inevitable.

4. Scope changes over time What’s your monthly scope change rate? Is it under control? Do you know your company’s baseline? Do you know your industry average?

5. Requirements Traceability is a standard project activity Despite industry standards, Requirements Traceability is not always done, or done well. It’s performance should be encouraged.

6. Requirements Traceability - features It helps to know what traceability is, and what data is captured.

7. How Traceability can help you track project progress Requirements Defined > Work Done > Work Remaining Release scheduling based on actual progress.

8. All you need: 3 pieces of data that is already captured Number of Requirements Requirements State Over time (e.g. weekly/monthly progress)