|Find available class and register:
||Classroom - 3 Days | Virtual - 6 Days
|Why to Take This Course:
This Unique course prepares you for both CPRE-FL and CPRE-AL RE@Agile certificates, hence truly fast tracking your career.
The IREB Certified Professional for Requirements Engineering – Foundation Level (CPRE-FL) course is designed for requirements engineers, business analysts and testers wanting to build their skills in requirement engineering and business analysis. This course provides practical knowledge and requirements engineering tools and techniques which are fundamental to delivering high quality requirements specifications.
Requirements Engineers are often at a loss when it comes to perform their Requirements Engineering (RE) work in an informal and fast paced Agile environment. The situation often increases the project risk. The Advance Level CPRE-AL RE@Agile certification prepares you for taking on the challenge and make your project successful.
So by attending this course, you prepare for both the certifications and be ready to advance your career in the Agile world.
- Understand the impact of requirement errors on project failure
- Learn the rationale for Requirements Engineering as a formal and systematic discipline
- Learn various sources of requirements and techniques to capture the required information
- Learn how to remove ambiguity in language
- Understand how to record requirements
- Examine the quality assurance aspects of the requirements and requirements documentation
- Learn how to deal with disagreement on requirements and conflict resolution
- 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 artefacts.
- Describe the importance of and steps in a Scrum retrospective.
- Participate in a class retrospective.
- Introduction and Foundations
- Four major activities of RE
- Role of communication in RE
- Skills of a requirements engineer
- Three kinds of requirements
- Role of quality requirements
- 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.
- System and System Context
- Understand System context, Relevant environment and Irrelevant environment
- Sources of the requirements
- Sync of the requirements
- Requirements Elicitation
- Requirements sources
- Significance of requirements sources and consequences of missing requirements sources
- The most important information of the stakeholder documentation
- Principles in dealing with stakeholders (stakeholder rights and duties)
- Using the content and significance of the Kano model
- Influencing factors for the choice of elicitation techniques
- Advantages and disadvantages of elicitation techniques - survey, creativity techniques, document-centred techniques, observation techniques and supporting techniques
- 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
- Requirements Documentation
- Key reasons for requirements documentation
- Three perspectives of functional requirements
- Advantages and disadvantages of natural language requirements documentation
- The most important model-based requirements documentation form
- The advantages of mixed form of requirements documentation
- The advantages of standardised document structures
- One widespread document structures
- Important points for a tailored standard structure
- Activities building on requirements documents
- Using quality criteria for requirements documents
- Using quality criteria for requirements
- Most important style rules for requirements
- Using contents and importance of a glossary
- Using rules for handling the glossary
- Natural Language Requirements Documentation
- Five transformational processes in the perception and writing of natural language and their consequences on the formulation of requirements
- Five steps for formulating requirements using a requirements template
- Model Based Requirements Documentation
- “model” and the properties of models
- Elements of a conceptual modelling language
- Advantages of requirements models
- Importance of goals in requirements engineering
- Two types of goal decomposition
- Modelling and using of goal relationships as and/or trees
- Modelling of and using use case diagrams
- Specification of and using use case specifications
- Three perspectives on requirements
- Data perspective on requirements
- Entity relationship diagrams and UML class diagrams
- Functional perspective on requirements
- Data flow diagrams and UML activity diagrams
- Behavioural perspective on requirements
- Using UML statecharts
- Requirements validation and negotiation
- Significance of validating requirements
- Significance of conflicts with regard to requirements
- Three quality aspects of requirements
- Validation criteria for the quality aspects "content”, "documentation” and "agreement”
- Six principles for requirements validation
- Using the principles of requirements validation
- Techniques for requirements validation
- Using the validation techniques: commenting (expert opinion), inspection, walkthrough, perspective-based reading, validation via prototypes and use of checklists
- Activities for requirements negotiation
- Types of requirements conflicts
- Various conflict resolution techniques
- Documentation for conflict resolution
- Checking and Reconciling Requirements
- Requirements Management
- Purpose and definition of attribute schemes
- Important attribute types for requirements
- Views on requirements
- Prioritising requirements
- Determination of business value
- Business Value, Risks, and Dependencies
- Estimating User Stories and Other Backlog Items
- Pechniques for prioritising requirements
- Requirements traceability
- Classes of traceability relationships
- Representation for traceability relationships
- Versioning of requirements
- Formation of requirements configurations
- Formation requirements baselines
- Fequirements changes
- Functions and members of a Change Control Board
- Elements of a requirements change request
- Different classes of change requests
- Process to handle change requests
- Scaling RE@Agile
- Roadmaps and Large-Scale Planning
- Organizing teams to handle larger and more complex problems
- Examples of scaling frameworks
- Tool Support
- Features of a requirements management tool
- Knowing the five aspects in the introduction of requirements engineering tools
- Knowing the seven views of requirements engineering tools
||To help assimilate the tools and techniques learned, there is a mixture of various kinds of exercises throughout the course. A lively role play and case study help reinforce concepts learned. Students will need to be prepared for a high level of participation. Each participant will receive a comprehensive student guide complete with examples and workshop solutions.
|Who Should Attend:
- Requirements Engineers, Business Analysts, Software Engineers, Test Engineers, Project Managers, Product Owners, Scrum Masters looking to improve their hands-on requirements engineering skills.
- Anyone seeking to develop in-depth understanding of what constitutes quality requirements and how to achieve this objective in Agile environment.
- Anyone who wants to earn the fastest growing CPRE-FL and CPRE-AL RE@Agile certification form IREB.
||There are no prerequisites for this course, but some experience on defining requirements will be useful.
|What You Will Receive:
Both our Traditional and Virtual classes use the same materials:
- Comprehensive study guide with PowerPoint slides and detailed notes to serve as both an in-class guide and on-the-job reference
- Example case study running throughout the course
- Class discussions and exercises to reinforce the information presented
|Find available class and register: