Proving Use Cases Correct
Posted by EdmontonPMNov 14
Live Webinar – November 20th 2014, 12:00-1:00 PM EDT
Offered by ASPE (REP 2161) 1 Category A PDU – Free PDU
Note: Although ASPE is an REP presentations may have to be recorded as a Cat C PDU Event – Contact Traci Lester Marketing Specialist at ASPE for more information
The Greatest Source Of Defects Originate From Requirements!
If requirements defects can be removed, the quality of a product can be more than doubled!
Whether you are doing agile or traditional projects, requirements defects are the greatest source of error, and loss of quality.
For projects that are complex or require high quality results, such as in the financial, health, and astronautical fields, the requirements should be validated before coding.
This presentation shows a clean method of eliciting requirements from the sponsor mission statement to use cases.
It shows how to make use cases comply with the IEEE standard for requirements specifications, and then explains how to rigorously validate the use cases to be provably correct.
The best news is that this process takes less time per use case than guess-and-check coding, even in agile environments.
Presenter: Al Cline, PMP, PMI-ACP
PDU Category B (PMBOK 5) documentation details:
Process Groups: Executing
Knowledge Areas: 5 – Scope
- 5.2 Collect Requirements
- 5.3 Define Scope
- 5.5 Validate Scope
As a Category C ‘Self Directed Learning Activity’ remember to document your learning experience and its relationship to project management for your ‘PDU Audit Trail Folder’
Click to register for Proving Use Cases Correct
Leave a Reply