Placeholder – AgileBA content here.
- Understand how business agility is critical to success in a VUCA world
- The meaning behind the values in the Manifesto
- Understand the difference between product and project management and defining the best approach for delivery
- Understand the Scrum values and integrate scrum into AgilePM
- Understand and implement AgilePM
- Understand the impact of Theory of Constraints on projects
- Implement the 9 Principles of Agile Leadership
- Identify and engage with stakeholders
- Understand the role of the Scrum Master and Product Owner
- Define and create an environment for effective collaboration and communication
- Create user stories from requirements and apply MoSCoW prioritisation
- Implement the Project Planning event
- Apply tracking and controls to projects while maintaining agility
- Implement appropriate risk management and governance
The AgilePM foundation level course will give participants a solid introduction to the framework and it’s practical application to every day business.Â
Duration: 3 days
Pre-requisites:
Delegates are required to pass the Scrum Essentials exam (held at the end of Day 1) to proceed to the Foundation level. Additionally, delegates with no formal experience should familiarise themselves with the materials specified in the joining instructions prior to course commencement.
See below for syllabus:
Key Concepts
The definition of Business Agility
The meaning of VUCA
The Agile Manifesto and its enhancement for the Agile project context
The scope of product development and project development and understand the difference between product and project
Why agility is needed in project delivery
Scrum Overview
The definition of Scrum
Scrum values
Scrum roles and purpose
Purpose of the 5 scrum events
Scrum artefacts and commitments
AgilePM Fundamentals
AgilePM philosophy
The AgilePM approach to project constraints
AgilePM principles
Combining scrum with AgilePM
Â
Individuals and Interactions
9 Principles of Agile leadership
Stakeholders and the project team roles
Â
Collaboration & Communication
Collaboration definition
Communication definition
Effective collaboration and communication in the context of a project
Project Lifecycle Framework
Defining and distinguishing between types of increment
The project lifecycle
Purpose, work and potential work-products associated with each of the project lifecycle phases
Requirements, Estimating and Prioritisation
Key concepts and hierarchy of requirements, goals, backlogs, solutions, products and increments
Definition of a requirement
User stories and INVEST model
M.o.S.C.o.W. prioritisation techniques
Requirements throughout the project lifecycle
Estimating
Planning and Control
Planning concepts
Tracking and control concepts
Project Planning event
Integrating AgilePM and Scrum
Risk Management and the Project Approach
Integrated Risk Management
Dealing with uncertainty
Project Approach Questionnaire
Governance, Compliance and the AgilePM Products
Governance and empiricism
The Cone of Uncertainty (Barry Boehm diagram)
Financial governance
Regulatory compliance
The AgilePM practitioner workshop is hands-on application of the theory learnt at the foundation level. In addition to practical application, this workshop includes practitioner exam preparation.
Duration: 2 Days
Pre-requisites:
- AgilePM Foundation exam pass
- Scrum Essentials (or equivalent) pass
Details of the core content is below:
AgilePM Fundamentals
Understand the concepts, roles, principles, processes and approaches relating to AgilePM Fundamentals. Specifically to understand:
- The Philosophy of AgilePM, the components of the AgilePM framework and relationship between them
- Balancing real world needs, demands and constraints – specifically as they relate to Time, Cost, Quality and Features
- AgilePM’s 8 principles – and how the Process, People, Work–Products and Practices elements of make these principles a reality needs, demands and constraints – specifically as they
relate to Time, Cost, Quality and Features
Individuals and Interactions, Collaboration and Communication
Be able to apply and tailor the relevant aspects to a project scenario.
Specifically to:
- Adopt an appropriate style of Agile Leadership, balancing situational style, effective empowerment and embracing a growth mindset
- Apply the 9 Principles of Agile leadership
- Shape an appropriate agile team structure, including acceptable role consolidations or sharing, as this applies to projects with one or more
development teams - Identify agile project leadership and team roles, their responsibilities, and appropriate collaborative relationships and channels of communication between them in the context of the overall project organisation
Be able to identify, analyse and distinguish between appropriate and inappropriate application  to a project scenario. Specifically to analyse, with reasons:
- Whether the 9 Principles of Agile leadership have been applied appropriately
- Whether the roles and responsibilities, and their interactions, have been allocated appropriately
- Whether collaboration and communication is effective
- Whether the events and practices of AgilePM and Scrum are appropriately enacted to enable transparency of process and progress
Risk Management and Project Approach
Be able to apply and tailor the relevant aspects of risk management to a project scenario.
Specifically to:
- Explain how the AgilePM approach, applied with discipline, makes the need for a discrete Risk Management process unnecessary
- Tailor the Project Approach to mitigate risk
Be able to identify, analyse and distinguish between appropriate and inappropriate application of risk management to a project scenario. Specifically to analyse, with reasons:
- Differentiate between VUCA–derived risk and Approach–derived risk
- Identify the relationship between each statement in the Project Approach Questionnaire and the appropriate application of the Principles, Process, People, Work Products and Practices elements of the AgilePM framework
- Use the Project Approach Questionnaire to identify approach based risk in an AgilePM project context
Defining and estimating the work of the project
Be able to apply and tailor the relevant aspects of defining and estimating to a project scenario.
Specifically to:
- Apply key concepts and hierarchy of requirements, goals, backlogs, solutions, products and increments in defining, organising and communicating the work of the project
- Define the work of the project at a level of detail appropriate to the project lifecycle phase
- Estimate the work of the project using approaches appropriate to the project lifecycle phase
- Apply the MoSCoW rules to the prioritization of Solution and Product
Backlogs, in a way that guarantees delivery of the Minimum Usable Subset and aligns the expected outcome of the project with its business case
Be able to identify, analyse and distinguish between appropriate and inappropriate application of defining and estimating  to a project scenario. Specifically to analyse, with reasons:
- Whether the key concepts and hierarchy of requirements, goals, backlogs, solutions, products and increments has been applied appropriately
- Whether the work of the projects has been defined and prioritised appropriately in accordance with project lifecycle phase objectives and the agile practice of leaving detailed analysis to the last responsible moment
- Whether the work of the projects has been defined and prioritised appropriately in accordance with project lifecycle phase objectives and the agile practice of leaving detailed analysis to the last responsible moment
Planning and Controlling the Work of the Project, Governance, Compliance and AgilePM Products
Be able to apply and tailor the relevant aspects of governance to a project scenario.
Specifically to:
- Apply AgilePM planning concepts appropriately to each phase of the project lifecycle
- Track progress and respond to change in context of the overall project, tranche and Sprint timeboxes
- Apply appropriate tailoring to the default Scrum development approach to enable multi–team project planning and dependency management
- Demonstrate control over development when using AgilePM and Scrum
- Assure regulatory compliance in an Agile project
- Explain how financial governance in an AgilePM project (with fixed time and cost and controlled scope) differs from traditional projects (with fixed scope and controlled time and cost)
Be able to identify, analyse and distinguish between appropriate and inappropriate application of governance to a project scenario. Specifically to analyse, with reasons:
- Whether AgilePM planning concepts have been appropriately applied in accordance with lifecycle phase objectives
- Whether tracking and control concepts have been appropriately applied in accordance with lifecycle phase objectives
- Analyse the effectiveness of the AgilePM project planning event and associated customization of the default Scrum approach in multi–team project planning and cross–team dependency management.
- Whether controls have been applied appropriately when using AgilePM and Scrum
- Analyse how regulatory compliance has been integrated with AgilePM approach and the impact it has had on overall agility
- Whether work–products related to regulatory compliance and financial governance have been applied appropriately throughout each of the project lifecycle phases
Q1
Q2
Q3
This course is suitable for project professionals:
- project managers
- PMO managers
- project supporting roles
- product managers / product owners
- scrum masters
- technical architect/authority
- construction site managers
- business analysts
People who attend range from new entrants to seasoned professionals and project directors.
Agile Project Management Certification
Globally recognised qualification from APMG-International, an ISO accredited examining body specialising in qualifications for business professionals. The Agile Project Management examination is taken online.
Foundation level
- 50 simple, multiple choice questions
- 40 minutes
- Closed book
- Pass mark: 30 marks out of 50 (60%)
Practitioner Level
Pre-requisites: AgilePM Foundation level exam and Scrum Essentials exam or listed alternative
- 60 context-based, multiple choice questions
- 120 minutes
- Open book
- Pass mark: 30 marks out of 60 (50%)
Further learning:
All Dates and Times are listed in AEST (UTC +10) unless otherwise specified
