Software Requirements: 10 Traps To Avoid
With Karl E. Wiegers
Posted by
EdmontonPM
Nov 9
Live Webinar November 17th, 2016 1:00 pm – 2:00 pm EST
Activity Type: Education – Course or Training 1 Hour 1 PDU free
Provider: Modern Analyst
For a terrific Print & Learn opportunity check out
Project Management Best Practices With Karl Wiegers
Successful software projects are built on a foundation of well-understood requirements.
However, many development organizations get caught in traps that prevent them from effectively collecting, documenting, or managing their requirements.
This presentation describes ten typical requirements problems that can sabotage your project.
Several symptoms that indicate you might be getting caught in each trap are presented, along with suggestions for avoiding or escaping from the trap.
The requirements traps discussed are:
- Confusion about what a requirement is
- Inadequate customer involvement
- Vague and ambiguous requirements
- Unprioritized requirements
- Building functionality no one uses
- Analysis paralysis
- Scope creep
- Inadequate requirements change process
- Insufficient change impact analysis
- Inadequate requirements version control
Presenter: Karl E. Wiegers (LinkedIn profile) Principal Consultant Process Impact has provided training and consulting services worldwide on many aspects of software development, management and process improvement.
Karl is the author of many books including:
- Practical Project Initiation: A Handbook with Tools (Best Practices)
- Creating a Software Engineering Culture,
- Peer Reviews in Software: A Practical Guide
- Software Requirements
- More About Software Requirements: Thorny Issues and Practical Advice
Click to register for:
Software Requirements: 10 Traps To Avoid
0 | 0 | 1.0 |
Technical Project Management | Leadership | Strategic & Business Management |
NOTE: For PMI® Audit Purposes – Print Out This Post! Take notes on this page during the presentation and also indicate the Date & Time you attended. Note any information from the presentation you found useful to your professional development and place it in your audit folder.
Leave a Reply