• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Requirements = Scope
 

Requirements = Scope

on

  • 2,708 views

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.

Statistics

Views

Total Views
2,708
Views on SlideShare
2,310
Embed Views
398

Actions

Likes
1
Downloads
88
Comments
0

3 Embeds 398

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

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Requirements = Scope Requirements = Scope Presentation Transcript

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