Developing Better Project Requirements
Coursalytics is an independent platform to find, compare, and book executive courses. Coursalytics is not endorsed by, sponsored by, or otherwise affiliated with Georgia Tech Professional Education.Full disclaimer.
It's always good to begin a project knowing the requirements to lay a more solid foundation for a smoother rollout. Whether you are developing in a more traditional “waterfall” world or moving to the Agile, iterative world, this course will help you develop techniques to clarify the scope of your product. You will explore the traditional “requirements upfront” methods and distinguish those from the processes of current, more adaptive environments. The course presents the problems associated with scope definition and management. Explore planning your requirements strategy, uncovering key stakeholders, organizing your team, assembling a good story, and writing clear and concise statements. The course will present techniques for determining client wishes from needs, prioritizing the needs, and validating that what you build is what you promised.
What You Will Learn
- Iterative methodologies
- Estimation techniques
- Project requirements
- Problem statements
How You Will Benefit
- Separate customer needs from customer desires.
- Prioritize customer needs.
- Improve communication with the customer about information technology requirements.
- Ensure customer understanding of requirements before project approval.
- Use walkthroughs to validate requirements.
INTRODUCTION TO BETTER REQUIREMENTS
- How good requirements make a difference
- The high cost of rework
- The difference between project and product requirements
- Types of requirements
- Product quality attributes
- Critical success factors for information technology requirements
PLANNINGS: PLAN-DRIVEN VERSUS ITERATIVE
- The importance of the organizational environment
- Waterfall organizations
- Environments for adaptive projects
- The Agile manifesto
- Agile principles
UNCOVERING: ELICITATION STRATEGIES
- The challenges of collecting requirements
- Why stakeholders make a difference
- Which project stakeholders to involve
- The key role of product owner
- How to identify misleading intentions
- The power of "why"
ORGANIZING: THERE’S NOTHING LIKE A GOOD STORY
- User stories and user scenarios: the benefits
- How to create user scenarios -- step-by-step approach
- How to address exceptions
- How to develop requirements from user scenarios
WRITING: CLEAR, CONCISE, COMPLETE
- The anatomy of a good requirement
- Guidelines for writing good requirements
- How to derive requirements from user scenarios
- How to recognize requirement problems
ANALYZING: WANTS VERSUS NEEDS
- The search for "soon-to-be" problems
- How to elicit, analyze, and negotiate -- the iterative approach
- How to define system boundaries
REVIEWING: VERIFYING AND VALIDATING
- Analysis versus validation
- When a requirement document is needed
- How to format the SRS
- Validation best practices
- How to check against standards
- Inspections and test cases
- Results of poor requirement management
- The critical success factors in managing requirements
- How to trace requirements -- forwards and backwards
- Requirements management tools
Who should attend
This course is designed for Scrum Masters, project managers, product owners, business analysts, as well as Project Management Professionals seeking annual Professional Development Units.