Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Requirements = Scope

3,316 views

Published on

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

Published in: Business
  • Dating for everyone is here: ❤❤❤ http://bit.ly/36cXjBY ❤❤❤
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Sex in your area is here: ❤❤❤ http://bit.ly/36cXjBY ❤❤❤
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Requirements = Scope

  1. 1. Requirements = Scope<br />Project Performance information Better and Faster with Requirements Traceability.<br />Craig Brown<br />PMOZ Proposal 2011<br />
  2. 2. 3 learning outcomes<br />
  3. 3. Requirements drive scope<br />Unstable requirements drive unstable scope. <br />Unstable requirements are almost inevitable.<br />
  4. 4. Scope changes over time<br />What’s your monthly scope change rate? Is it under control? <br />Do you know your company’s baseline? <br />Do you know your industry average?<br />
  5. 5. Requirements Traceability is a standard project activity<br />Despite industry standards, Requirements Traceability is not always done, or done well. It’s performance should be encouraged.<br />
  6. 6. Requirements Traceability - features<br />It helps to know what traceability is, and what data is captured.<br />
  7. 7. How Traceability can help you track project progress<br />Requirements Defined > Work Done > Work Remaining<br />Release scheduling based on actual progress.<br />
  8. 8. All you need: 3 pieces of data that is already captured<br />Number of Requirements<br />Requirements State<br />Over time (e.g. weekly/monthly progress)<br />

×