The Project Management Institute (PMI) was founded in 1969 and now has 283 chapters worldwide and around 470,000 professional members. It develops and implements standards for project, program, and portfolio management as well as certification programs. The PMI Kyiv Chapter provides training and certification in Ukraine to help professionals implement PMI's standards and frameworks for effective project delivery.

1. PMI Kyiv Chapter
Ukraine

2. Project Management Institute
● Основан в 1969 году
● 283 представительств по всему миру
● Около 470,000 профессиональных членов
● Разработка и внедрение стандартов
● Cертификационные программы

3. Фундаментальные стандарты
● Project Management Body of Knowledge Guide
● The Standard for Program Management
● The Standard for Portfolio Management
● Organizational Project Management Maturity Model

4. Управление проектами
A Guide to the Project Management Body of
Knowledge (PMBOK® Guide)
Глобальный стандарт управления проектами,
прошедший ISO сертификацию.
Дает профессионалам управления проектами
необходимые фундаментальные практики.

5. Управление программами
The Standard for Program Management
Предоставляет инструментарий для комплексной
реализации проектов в масштабе организации.
Рассматривает эффективную и действенную
коммуникацию проектов, их конкуренцию за
ресурсы.

6. Управление портфелем
The Standard for Portfolio Management
Управление проектами и управление программами
учат как управлять проектами правильно.
Управление портфелем учит как управлять
правильными проектами.

7. Модель зрелости
Organizational Project Management Maturity Model
Зрелость организации в управлении проектами.
Привязка к стратегии предприятия, управление
целями, установка приоритетов и выбор проектов.

8. Практические стандарты
● Project Risk Management
● Earned Value Management
● Project Configuration Management
● Work Breakdown Structures
● Scheduling
● Project Estimating
● Project Manager Competency Development
Framework

9. Сертификация
● Project Management Professional
● Certified Associate in Project Management
● Program Management Professional
● Portfolio Management Professional
● PMI Risk Management Professional
● PMI Scheduling Professional
● PMI Professional in Business Analysis
● PMI Agile Certified Practitioner

10. Сертификации PMI

11. Сертификация в Украине
PMP 391
PgMP 1
PMI RMP 3
PMI ACP 22

12. Отличия сертификации PMI
● Единая международная сертификация
● Разделение обучения и сертификации
● Постоянное подтверждение (PDU)

13. PMI Agile Certified Practitioner
Стоимость: $495 ($435)
Требования для допуска:
2,000 часов общего опыта работы в проектах
1,500 часов работы по Agile методологиям
21 час формального обучения

14. Формальное обучение
A. PMI Registered Education Providers (R.E.P.s)
B. PMI chapters
C. Employer/company-sponsored programs
D. Training companies or consultants
E. Distance-learning companies
F. University/college academic

15. PMI Agile Certified Practitioner

16. Структура экзамена
Домен Вопросы
Принципы и мировоззрение Agile 16%
Реализация, основанная на ценности 20%
Работа с заинтересованными сторонами 17%
Эффективность команды 16%
Адаптивное планирование 12%
Идентификация и решение проблем 10%
Постоянное совершенствование 9%
100 оцениваемых и 20 неоцениваемых вопросов

17. Agile Principles and Mindset
Task 1 Advocate for agile principles by modeling those
principles and discussing agile values in order to
develop a shared mindset across the team as well as
between the customer and the team.
Task 2 Help ensure that everyone has a common
understanding of the values and principles of agile and
a common knowledge around the agile practices and
terminology being used in order to work
effectively.
Task 3 Support change at the system or organization level by
educating the organization and influencing processes,
behaviors, and people in order to make the organization
more effective and efficient.

18. Value-Driven Delivery
Task 1 Define deliverables by identifying units that can be
produced incrementally in order to maximize their value
to stakeholders while minimizing non-value added work.
Task 2 Refine requirements by gaining consensus on the
acceptance criteria for features on a just-in-time basis in
order to deliver value.
Task 3 Select and tailor the team’s process based on project
and organizational characteristics as well as team
experience in order to optimize value delivery.

19. Stakeholder Engagement
Task 1 Identify and engage effective and empowered business
stakeholder through periodic reviews in order to ensure
that the team is knowledgeable about stakeholders’
interests, needs, and expectations.
Task 2 Identify and engage all stakeholders (current and
future) by promoting knowledge sharing early and
throughout the project to ensure the unimpeded flow of
information and value throughout the lifespan of the
project.
Task 3 Establish stakeholder relationships by forming a
working agreement among key stakeholders in order to
promote participation and effective collaboration.

20. Team Performance
Task 1 Cooperate with the other team members to devise ground
rules and internal processes in order to foster team
coherence and strengthen team members’ commitment to
shared outcomes.
Task 2 Help create a team that has the interpersonal and
technical skills needed to achieve all known project
objectives in order to create business value with minimal
delay.
Task 3 Encourage team members to become generalizing
specialists in order to reduce team size and bottlenecks,
and to create a high performing
cross-functional team.

21. Team Performance
Task 1 Plan at multiple levels (strategic, release, iteration, daily)
creating appropriate detail by using rolling wave planning
and progressive elaboration to balance predictability of
outcomes with ability to exploit opportunities.
Task 2 Make planning activities visible and transparent by
encouraging participation of key stakeholders and
publishing planning results in order to increase
commitment level and reduce uncertainty.
Task 3 As the project unfolds, set and manage stakeholder
expectations by making increasingly specific levels of
commitments in order to ensure common understanding of
the expected deliverables.

22. Team Performance
Task 1 Create an open and safe environment by encouraging
conversation and experimentation, in order to surface
problems and impediments that are slowing the team
down or preventing its ability to deliver value.
Task 2 Identify threats and issues by educating and engaging the
team at various points in the project in order to resolve
them at the appropriate time and improve processes that
caused issues.
Task 3 Ensure issues are resolved by appropriate team
members and/or reset expectations in light of issues that
cannot be resolved in order to maximize the value
delivered.

23. Problem Detection and Resolution
Task 1 Create an open and safe environment by encouraging
conversation and experimentation, in order to surface
problems and impediments that are slowing the team
down or preventing its ability to deliver value.
Task 2 Identify threats and issues by educating and engaging
the team at various points in the project in order to
resolve them at the appropriate time and improve
processes that caused issues.
Task 3 Ensure issues are resolved by appropriate team
members and/or reset expectations in light of issues
that cannot be resolved in order to maximize the value
delivered.

24. Problem Detection and Resolution
Task 1 Tailor and adapt the project process by periodically
reviewing and integrating team practices, organizational
culture, and delivery goals in order to ensure team
effectiveness within established organizational
guidelines and norms.
Task 2 Improve team processes by conducting frequent
retrospectives and improvement experiments in order to
continually enhance the effectiveness of the team,
project, and organization.
Task 3 Seek feedback on the product by incremental delivery
and frequent demonstrations in order to improve the
value of the product.

25. Techniques and tools
● emotional intelligence
● collaboration
● adaptive leadership
● servant leadership
● negotiation
● conflict resolution
● cycle time
● lead time
● EVM for agile projects
● defect rate
● approved iterations
● work in progress

26. Techniques and tools
● reviews
● Kanban board
● task board
● timeboxing
● iteration and release planning
● variance and trend analysis
● WIP limits
● daily stand ups
● burn down/up charts
● cumulative flow diagrams
● backlog grooming/refinement
● product-feedback loop

27. Techniques and tools
● Kaizen
● the Five WHYs
● retrospectives, intraspectives
● process tailoring/hybrid models
● value stream mapping
● control limits
● pre-mortem (rule setting, failure analysis)
● fishbone diagram analysis
● frequent verification and validation
● continuous integration
● testing, including exploratory and usability

28. Techniques and tools
● risk adjusted backlog
● risk burn down graphs
● risk-based spike
● architectural spike
● ROI/NPV/IRR
● compliance
● customer valued prioritization
● requirements reviews
● minimal viable product (MVP)
● minimal marketable feature (MMF)
● relative prioritization/ranking
● Kano analysis

29. Example of questions
In reference to Scrum, each sprint should produce:
A. In increment of potentially shippable product functionality
B. A set of documented product requirements and
specifications
C. A release with testable and measurable functionality
D. An increment of potentially testable product functionality

30. Example of questions
The primary purpose of a sprint review is for the team to:
A. Demonstrate what was accomplished during the sprint
B. Discuss what went well, what didn’t, ways to improve
C. Prioritize and estimate stories planned for the next sprint
D. Individually provide status updates on user stories in
progress

31. Example of questions
A value stream map is a tool used to identify
A. Waste across the entire process
B. Highest value product features
C. Most valuable team interactions
D. Most likely flow of project risks

32. Example of questions
When estimating initial velocity, the team should most likely
A. Use velocity of past iterations or make a calculated
guess
B. Discuss among the team their expectations
C. Use Kanban workflow to identify steps
D. Discuss with customer their expectations

33. Example of questions
What is the best option to improve project velocity?
A. Shield programmers from interruptions
B. Minimize customer involvement
C. Shorten the iteration length
D. Increase project team size

34. Example of questions
The Scrum Master and the Product Owner disagree on the
value of a Product backlog item. In order to resolve the
disagreement, ScrumMaster should ask:
A. The Product Owner to clarify the requirement
B. The business owner to resolve the problem
C. The business analyst to research the product value
D. Other project manager to resolve the problem

35. Example of questions
Which management style does Agile advocate?
A. Team
B. Task
C. Product
D. Performance

36. Example of questions
The most powerful capability of Scrum team is that they:
A. Are self-organized and empowered
B. Work in timeboxed sprints
C. Work with prioritized backlogs
D. Value individuals and interactions

37. Example of questions
When is the ideal time to hold retrospective?
A. Just before iteration planning
B. Right after iteration planning
C. At the start of next release
D. During the iteration review/demo

38. Example of questions
When interacting with team members, Agile project manager
should:
A. Ask team members to do things by phrasing the
statement as a request rather than as a demand
B. Ignore team member input and emotions when important
decisions have to be made
C. Proceed cautiously when requesting team members to
do something likely to make them unhappy
D. Disagree with the team based on the merit of the issue

39. Подготовка к сертификации
● Место проведения Киев
● Продолжительность 5 дней
● Даты проведения: 2, 9, 10, 16, 23 июня
● 40 PDU

40. Контактная информация
www: pmiukraine.org
Facebook: http://www.facebook.com/pmi.kyiv.chapter
e-mail: mkrukovsky@gmail.com