Requirements Engineers are often at a loss when it comes to perform their Requirements Engineering (RE) work in an informal and fast paced environment. The situation often increases the project risk. This certification prepares you for taking on the challenge, become a key member of your Agile team and make your project successful.
Why take this course:
• Prepare participants for RE@Agile Certification exam offered by IREB, Germany
• Describe agile values and principles, emphasizing the importance of RE work on an Agile project.
• Describe the Requirement Engineer’s role on Agile projects.
• Key principles of performing RE activities on Agile projects.
• Explain Scrum roles and responsibilities, focusing on the role of the Requirements Engineer.
• Define Agile requirements with user stories to build a product backlog.
• Release planning:
- Discuss the important role the requirements engineer plays in release planning.
- Describe the steps in release planning.
- Create a release plan.
• Groom the product backlog:
- Understand the importance of elicitation and requirements analysis in getting the detail necessary to build the product increment.
- Use just enough requirements modelling to groom the product backlog.
• Explain the importance of Scrum ceremonies and artifacts.
• Describe the importance of and steps in a Scrum retrospective.
• Participate in a class retrospective.
What is RE @Agile
• Bridging RE and Agile Principles towards RE@Agile
• RE@Agile as a cooperative, iterative and incremental approach
• Four goals of RE@Agile
- knowing the relevant requirements at an appropriate level of detail (at any time during system development),
- achieving sufficient agreement about the requirements among the relevant stakeholders,
- capturing the requirements according to the constraints of the organization,
- performing all requirements related activities according to the principles of the agile manifesto.
Starting for successful system development
• Vision and Goal Specification
• Specifying the System Boundary
• Stakeholder Identification and Management
• Balancing of Vision and Goals, Stakeholders, and Scope
Handling Functional Requirements
• Different levels of requirements granularity
• Identification, documentation and communication of functional requirements
• Working with user stories
• Splitting and grouping techniques
• Knowing when to stop decomposing
• Project and Product Documentation of Requirements
Handling Quality Requirements and Constraints
• Understanding the importance of quality requirements and constraints
• Adding Precision to Quality Requirements
• Quality Requirements and Backlog
• Making Constraints Explicit
Prioritizing and Estimating Requirements
• Determination of business value
• Business Value, Risks, and Dependencies
• Estimating User Stories and Other Backlog Items
• Road-maps and Large-Scale Planning
• Organizing teams to handle larger and more complex problems
• Examples of scaling frameworks