6 Common Traps to Avoid When Collaborating on Requirements
Posted by EdmontonPMMay 9
Live Webinar May 15th, 2013 – 1:00 pm – 2:00 pm EDT
Duration: 1 Hour Credits: 1 PDU Category B – Free PDU
Featured Sponsor : Jama
Product delivery teams get caught in traps that prevent them from effectively eliciting, documenting, or managing requirements. It is no wonder they often get out of sync on what they are supposed to build and why. How confident are you that everyone is in sync?
Learn from Jama Software and Karl Wiegers, the renowned author and speaker on requirements management, as he shares symptoms that you might be getting caught in a requirements trap, along with suggestions for avoiding and escaping the trap. Avoiding such traps will create more effective engagement across the entire organization and help your teams deliver successful projects.
The traps discussed in this webinar include:
- Inadequate stakeholder involvement
- Vague and ambiguous requirements
- Analysis paralysis
- Scope creep
- Ineffective change process
- Ineffective change process
- Poor version control
Over the years I’ve found that many software organizations struggle with the same issues when it comes to requirements. Such troublesome topics include:
- how to define project scope;
- the connection between use cases and functional requirements;
- distinguishing requirements from design; and…
- how to use requirements management tools effectively.
Some of the questions I’m asked repeatedly don’t have simple answers.
– Karl Wiegers
This presentation addresses six such common traps when collaborating on requirements.
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 6 Common Traps to Avoid When Collaborating on Requirements
Leave a Reply