Requirements = Scope

  • 2,328 views
Uploaded on

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

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

More in: Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,328
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
90
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 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)