Your SlideShare is downloading. ×
0
Requirements = Scope
Requirements = Scope
Requirements = Scope
Requirements = Scope
Requirements = Scope
Requirements = Scope
Requirements = Scope
Requirements = Scope
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Requirements = Scope

2,457

Published 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.

Published in: Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,457
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
93
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<br />Project Performance information Better and Faster with Requirements Traceability.<br />Craig Brown<br />PMOZ Proposal 2011<br />
  • 2. 3 learning outcomes<br />
  • 3. Requirements drive scope<br />Unstable requirements drive unstable scope. <br />Unstable requirements are almost inevitable.<br />
  • 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. 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. Requirements Traceability - features<br />It helps to know what traceability is, and what data is captured.<br />
  • 7. How Traceability can help you track project progress<br />Requirements Defined &gt; Work Done &gt; Work Remaining<br />Release scheduling based on actual progress.<br />
  • 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 />

×