Requirements = Scope

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

3 learning outcomes

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

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?

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.

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

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

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

http://www.betterprojects.net	348
http://translate.googleusercontent.com	3
http://paper.li	1

Requirements = Scope

by Craig Brown on Jun 01, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

3 Embeds 352

Statistics

Requirements = Scope — Presentation Transcript