Requirements: The Old Way and The New Way
Posted by EdmontonPMMar 17
Live Webinar – March 25th, 2014 2:00 pm – 3:00 pm EDT
Presented by: Enfocus Solutions
Duration: 1 Hour 1 PDUs Credits: 1Category C PDU- Free PDU
The vast majority of organizations are using archaic methods to develop requirements based on methods from the 1970s and early 1980s.
With the dynamic pace of business change, organizations that continue to use these practices have continued to see a significant amount of challenged and failed projects and have placed their organizations at a competitive disadvantage.
In fact, even with the recent emphasis on project management practices and certification, Standish Group research shows that there are more failed and challenged projects than there was in their original 1994 report when waterfall and traditional requirement practices are used.
Many studies have shown that poor requirements and changing requirements are two of the leading causes of project failures.
The birth of Agile development largely stemmed from frustration of ineffective requirements practices and the desire to find a better way out of this horrible dilemma.
Agile has made a big difference on project success rates; Standish Group research shows that Agile projects are three times more likely to be successful than waterfall projects. However, having such little documentation has created problems for some organizations that have adopted agile.
In this webinar, John Parker will discuss how methods used to define and manage requirements need to change whether Agile or waterfall development is used.
John will address the following topics:
- The Difference between Business, Stakeholder and Solution Requirements
- Requirements: One time or Incremental delivery
- Requirements Review and Validation: One Time or Continuous
- Requirements Documentation: Paper Documents or Electronic
- Elicitation: Interviews or Stakeholder Collaboration
- What is Requirements and What is Design
- How Better Discovery Practices can Improve Agile
PDU Category C (PMBOK 5) documentation details:
Process Groups: Executing
Knowledge Areas: 4- Integration 5 – Scope 8 – Quality
- 5.1 Plan Scope Management
- 5.2 Collect Requirements
- 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 Requirements: The Old Way and The New Way
Leave a Reply