PMI-ACP® Study Facilitation Program (Agile Scrum)


                                                                                                                                                        Training Module     : PMI-ACP® Study Facilitation Program (Agile Scrum)
Duration                     : 3 Days 
Who should attend?
Organizations which are having Agile Project Management Practices or those Organizations who are strategically planning to inculcate Agile Project Management practices for their business are recommended to have their resources formally trained to understand and practically implement Agile Practices.
In order to have a complete understanding as well as integrities of Agile Project Management Methodology and its nuances to implement it practically PMI has come up with Agile Certified Practitioner Certification. Uniqueness of ACP® certification is the right balance between theoretical understanding, practical approach and International standard Methodologies.

Certification Pre-requisites:

  • 2,000 hours of general project experience working on teams. A current PMP® or PgMP® will satisfy this requirement but is not required to apply for the PMI-ACP.
  • 1,500  hours  working  on  agile  project  teams  or  with  agile  methodologies.  This requirement is in addition to the 2,000 hours of general project experience.
  • 21 contact hours of training in agile practices.
Learning Objectives:
The course will enable participants to …
  • Explore various agile methodologies, knowledge, skills, techniques, beyond just scrum
  • Learn various knowledge & skills as described in PMI-ACP exam content outline
  • Learn various tools & techniques as described in PMI-ACP exam content outline
  • Solve about 100+ questions in class to get a feel of actual examination
  • Confidently face the PMI-ACP examination
Course Outline:
Day 1

  • Quick ice breaker test
-    Introduction
-    About PMI-ACP exam – procedure, eligibility, fees, etc
-    Introduction to incremental and iterative way of product development
-    How it is different, why
-    What challenges it addresses
-    Introduce agile, agile manifesto, principles
Scope management in agile
  • Role modeling, prototyping, wireframes, extreme characters, personas, brainstorming, mind maps, NGT
  • Story maps, user stories, epics, themes, product backlog
-    Risk adjusted backlog, spike, complex stories
-    3C’s, INVEST, split and combine stories
Value based prioritization of product backlog
  • Financial prioritization – NPV, ROI, payback period
-    Risk vis-à-vis value based prioritization
-    Kano model (Desirability based)
-    Theme screening
Day 2
Estimating work involved
  • Relative sizing
-    Story points, ideal days, T-shirt sizing
-    Planning poker
Planning agile projects
  • Release planning
-    Sprint planning – capacity based and velocity based
Slacks
Risk multiplier and risk adjusted burn charts Estimating velocity
Sprint length – how

Monitoring agile projects
  • Release burn down bar charts
-    Sprint burn down bar charts
-    Burn up charts
-    Burn down bar charts
-    Cumulative flow diagram
-    Parking lot charts
Daily stand up Sprint review
Sprint retrospective
  • Mute mapping
  • Star fish
-    PDCA
  • Force field analysis Agile modeling and TDD  Day 3

Introduction to Lean

  • WIP limits
-    Value stream mapping
-    Systems thinking
-    Kanban
-    Scrum vs Kanban
-    Fish bone diagram, 5-why technique
Building quality in scrum projects
  • Continuous integration
-    Escaped defects
-    Definition of done
-    MMF
-    Continuous delivery
Communication on agile projects
  • Self-managed and self-organized teams
-    Team room – big visible charts, information radiators
-    Osmotic communication
-    Collocation
Miscellaneous
  • Suitable contract types for agile projects
-    Challenges with scaled projects, distributed teams

Comments

Popular posts from this blog

Cloud Computing in simple

How to Write an Effective Design Document

Bookmark