Course Outline
Basic Concepts
- Definition and classification of requirements – levels and types of requirements for government projects.
- The importance of requirements in ensuring project success for government initiatives.
- The process from identifying needs to developing solutions.
- Typical activities involved in managing requirements for government projects.
Requirements Acquisition
- Sources of requirements for government projects.
- The business model as a source of requirements – scenarios and business processes relevant to government operations.
- Stakeholder analysis for government stakeholders.
- Techniques for eliciting requirements in the context of government projects.
- Methods for obtaining additional information, including constraints and risks specific to government projects.
Requirements Development
- Organizing requirements – understanding relationships and dependencies within government projects.
- Attributes that define good requirements for government use.
- Ensuring the quality of requirements through testing and defining acceptance criteria for government standards.
- Documenting requirements using various methods, comparing traditional and agile approaches suitable for government workflows.
Requirements Management
- Organizing work – defining roles and responsibilities and integrating requirements engineering into the broader project context for government projects.
- Developing a requirements architecture and ensuring traceability for government initiatives.
- Principles of creating a requirements repository tailored to government needs.
- Prioritizing requirements based on government priorities and resource availability.
- Managing scope and changes in requirements for government projects.
- Quality assurance for requirements – adhering to standards, guidelines, and checklists specific to government projects.
Summary
- A summary of the workshop focused on requirements management for government.
- Best practices and checklists for effective requirements management in government projects.
Requirements
Basic understanding of the IT product life cycle.
Familiarity with terminology used in software development and IT project implementation.
Recommended experience in at least one IT project.
Level
3
Goals
To gain knowledge about requirements management activities and their typical outputs.
To learn effective techniques for gathering requirements from diverse sources, including the business model.
To understand how to document requirements, including through modeling.
To master the principles of creating a requirements architecture and repository.
To develop the skills needed to specify and model requirements and solutions using recognized methodologies and notations.
Advantages
Training delivered by an expert with extensive experience in the IT industry and deep knowledge of IT processes for government.
Focus on practical application — theoretical concepts are reinforced with real-world project scenarios.
Utilization of tools commonly used in requirements engineering, providing hands-on experience with essential functionalities.
Opportunity to apply learned skills during the training sessions.
Upon completion, participants will receive a self-developed template for the requirements management process, which can serve as a reference or guideline for their professional tasks.
Addressed to
System and business analysts, product owners, business stakeholders, analysis team leaders.
Business representatives responsible for defining business needs.
Software and system engineers.
Testers, quality assurance (QA) professionals, and those responsible for ensuring the quality of information systems and software.
Testimonials (2)
The framework of BA
Puguh - PT PLN INDONESIA POWER
Course - PMI Professional in Business Analysis (PBA) Certification Preparation
As it is lot of content I really liked the working exercises
