PMI Agile Certified Practitioner

(PMI-ACP) ®

Ahmed Yousry Abdelaziz

CEO, Portolearn & Nileage LLC
ahmedyabdelaziz
PMI Agile Certified Practitioner
(PMI-ACP)®
INTRODUCTION
 Introduction

One of the fastest growing certifications in the field of project

management.

Earning a PMI-ACP® certification helps demonstrate your knowledge of

agile principles and your skill with agile techniques.

This course will help prepare you to sit for the exam.

PMI, ACP are registered marks of the Project Management Institute, Inc.
 PMI-ACP® Exam Prep.
Objectives

• By the end of this course, you will understand:

 Agile Mindset and Methodologies.
 Value-driven and Adaptive Planning.
 Agile Estimation, Metrics, and Risk Management.
 Stakeholder Engagement, Agile Communications, Practices, and Agile Tools.
 Agile Development, Quality, and Testing Practices.
 Agile Team Dynamics, Performance, and Leadership.
 Agile Problem detection, resolution & Agile Continuous Improvement.
 Adopting and Applying the Agile approach to an Organizational Level.
 Applied Agile on the Project Management Profession.
 Course Content

Introduction: About the PMI-ACP® Exam Chapter 4: Team Performance

Chapter 1: Agile Principles and Mindset Chapter 5: Adaptive Planning
Chapter 2: Value-Driven Delivery Chapter 6: Problem Detection and Resolution
Chapter 3: Stakeholder Engagement Chapter 7: Continuous improvement
PMI Agile Certified Practitioner
(PMI-ACP)®
Exam Information and Requirements.
Exam Timeline & Audit Process.
Certification Fees & Renewal.
PMI Agile Certified Practitioner (PMI-ACP)®
Exam Requirements, Timeline & Audit Process
PMI Agile Certified Practitioner (PMI-ACP)®
Exam Requirements, Timeline & Audit Process
PMI Agile Certified Practitioner (PMI-ACP)®
Exam Requirements, Timeline & Audit Process
PMI Agile Certified Practitioner (PMI-ACP)®
Certification Fees & Renewal
PMI Agile Certified Practitioner (PMI-ACP)®
Certification Fees & Renewal
PMI Agile Certified Practitioner (PMI-ACP)®
Exam Information
Questions
‫اﻷﺳﺌﻠﺔ‬
‫‪Break‬‬
‫إﺳﺘﺮاﺣﺔ‬
INTRODUCTION

What is Agile?
 INTRODUCTION
What is Agile?

Agile is a philosophy, Agility is a mindset.

Agile, by itself, is not a methodology.

Agile embodies practices, tools & a culture.
 What is Agile?

Agile is an iterative and incremental or evolutionary approach to project

development which is performed in a highly collaborative manner by
self-organizing teams with ‘Just Enough’ ceremony that produces high
quality deliverable in a cost effective and timely manner which meets
the changing needs of its stakeholders.
‫( ﻣﻨﻬﺠﻴﺔ )ﻃﺮﻳﻘﺔ( ﺗﻜﺮارﻳﺔ أو ﺗﺪرﻳﺠﻴﻪ ﻹدارة اﻟﻤﺸﺎرﻳﻊ اﻟﺒﺮﻣﺠﻴﺔ واﻟﻐﻴﺮ ﺑﺮﻣﺠﻴﺔ واﻟﺘﻲ ﺗﺮﻛﺰ ﻋﻠﻰ ﺑﻨﺎء اﻟﻤﻨﺘﺞ ﻋﻠﻰ ﻋﺪة‬Agile)‫ﺗﻌﺘﺒﺮ اﻟـ‬
ً‫ وﻳﻌﺘﺒﺮ ﻫﺬا اﻟﻤﻨﺘﺞ )اﻟﻤﺮﺣﻠﻲ( ﻣﻨﺘﺠﺎً ﺣﻘﻴﻘﻴﺎ‬.‫ ﻣﺘﻤﻴﺰً ﻋﻦ ﺳﺎﺑﻘﻪ ﺑﺨﺼﺎﺋﺺ إﺿﺎﻓﻴﺔ‬،ً‫وﺗﻮﻟﺪ ﻛﻞ ﻣﺮﺣﻠﺔ ﻣﻨﺘﺠﺎ‬ّ ،‫ﻣﺮاﺣﻞ وﺑﻔﺘﺮات زﻣﻨﻴﺔ ﻗﺼﻴﺮة‬
.‫ واﻟﻐﺎﻳﺔ ﻣﻦ ذﻟﻚ ﺗﻘﺮﻳﺐ اﻟﻤﻨﺘﺞ ﻟﻠﻌﻤﻴﻞ ﻟﻘﻴﺎس ﻣﺪي رﺿﺎه ﺑﻤﺮاﺣﻞ ﺗﻄﻮر ﻣﻨﺘﺠﻪ‬،‫ﻳﺴﺘﻄﻴﻊ اﻟﻌﻤﻴﻞ اﻟﺘﻔﺎﻋﻞ ﻣﻌﻪ‬
INTRODUCTION
What is Agile?
Agile Manifesto
THE 4 VALUES OF AGILE MANIFESTO

INDIVIDUALS & INTERACTIONS

OVER PROCESSES AND TOOLS

RESPONDING TO CHANGE
OVER FOLLOWING A PLAN

WORKING PRODUCT
OVER FULL DOCUMENTATION

CUSTOMER COLLABORATION
OVER CONTRACT NEGOTIATION
 12 AGILE PRINCIPLES

CUSTOMER WELCOME DELIVER

SATISFACTION CHANGING FREQUENT

COLLABORATION SUPPORT & TRUST ENABLE FACE-TO-FACE

DAILY MOTIVATE TEAM INTERACTIONS

WORKING PROMOTE PROMOTE TECHNICAL

SOFTWARE SUSTAINABLE PACE EXCELLENCE

MAXIMIZING SELF-ORGANIZING REFLECTS &

THOUGHT SIMPLICITY TEAMS ADJUSTS REGULAR
PRINCIPLES Our highest priority is to satisfy the customer
through early and continuous delivery of valuable
#1 software.

‫ﻫﺪﻓﻨﺎ اﻷﺳﻤﻰ ﻫﻮ إرﺿﺎء اﻟﻌﻤﻴﻞ ﻋﻦ ﻃﺮﻳﻖ اﻟﺘﺴﻠﻴﻢ اﻟﻤﺒﻜﺮ‬

.‫واﻟﻤﺘﻮاﺻﻞ ﻟﺒﺮﻣﺠﻴﺎت ذات ﻗﻴﻤﺔ‬
PRINCIPLES Welcome changing requirements, even late in
development. Agile processes harness change for
#2 the customer's competitive advantage.

.‫اﻟﺘﺮﺣﻴﺐ ﺑﺘﻐﻴﻴﺮ اﻟﻤﺘﻄﻠﺒﺎت وﺣﺘﻲ ﻟﻮ ﻓﻲ ﻣﺮاﺣﻞ ﻣﺘﺄﺧﺮه ﻣﻦ اﻟﺘﻄﻮﻳﺮ‬

‫ﺗُ ﺴﺨﺮ ﻋﻤﻠﻴﺎت )ﻧﻬﺞ( اﻷﺟﺎﻳﻞ ﻟﺘﻨﻔﻴﺬ اﻟﺘّ ﻐﻴﻴﺮات ﻟﺼﺎﻟﺢ اﻟﻤﻴﺰة‬
.‫اﻟﺘﻨﺎﻓﺴﻴﺔ ﻟﻠﻌﻤﻴﻞ‬
PRINCIPLES Deliver working product frequently, from a couple of
weeks to a couple of months, with a preference to
#3 the shorter timescale.

‫ ﺧﻼل‬،‫ﺗﺴﻠﻴﻢ ﻣﻨﺘﺠﺎت ﺻﺎﻟﺤﺔ ﻟﻺﺳﺘﺨﺪام ﻋﻠﻰ ﻓﺘﺮات زﻣﻨﻴﺔ ﻣﻨﺘﻈﻤﺔ‬

‫ ﻣﻊ اﻷﻓﻀﻠﻴﺔ ﻟﻠﻤﺪة اﻟﺰﻣﻨﻴﺔ‬،‫ﻓﺘﺮات ﻣﻦ أﺳﺒﻮﻋﻴﻦ إﻟﻰ ﺷﻬﺮﻳﻦ‬
.‫اﻷﻗﺼﺮ‬
PRINCIPLES
Business people and developers must work
#4 together daily throughout the project.

ً‫ﺑﺎﻟﻤﻬﻨﺔ( واﻟﻤﻄﻮرﻳﻦ ﻣﻌﺎ‬

ِ ‫ﻛﻼ ﻣﻦ اﻟﻤﻬﻨﻴﻴﻦ )اﻟﻌﺎرﻓﻴﻦ‬
ً ‫ﻳﺠﺐ أن ﻳﻌﻤﻞ‬
.‫ﺑﺸﻜﻞ ﻳﻮﻣﻲ ﺧﻼل ﻓﺘﺮة اﻟﻤﺸﺮوع‬
PRINCIPLES Build projects around motivated individuals.
Give them the environment and support they need,
#5 and trust them to get the job done.

‫ ﻣﻊ‬.(‫اﻻﻋﺘﻤﺎد ﻓﻲ ﺑﻨﺎء اﻟﻤﺸﺎرﻳﻊ ﻋﻠﻰ أﻓﺮاد ﻣﺘﺤﻤﺴﻴﻦ )ﻟﻨﻬﺞ اﻻﺟﺎﻳﻞ‬

‫ وﻣﻨﺤﻬﻢ اﻟﺜﻘﺔ ﻣﻦ أﺟﻞ إﻧﺠﺎز‬،‫ﺗﻮﻓﻴﺮ اﻟﺒﻴﺌﺔ اﻟﻤﻨﺎﺳﺒﺔ واﻟﺪﻋﻢ اﻟﻼزم‬
.‫اﻟﻌﻤﻞ‬
PRINCIPLES The most efficient and effective method of
conveying information to and within a development
#6 team is face-to-face conversation.

‫أﻛﺜﺮ اﻟﻄﺮق ﻓﺎﻋﻠﻴﺔ وﺗﺄﺛﻴﺮاً ﻟﺘﻮاﺻﻞ اﻟﻤﻌﻠﻮﻣﺎت ﻟﻔﺮﻳﻖ اﻟﺘﻄﻮﻳﺮ وﺑﻴﻦ‬

.‫أﻓﺮاده ﻫﻲ اﻟﺘﺨﺎﻃﺐ واﻟﺘﻮاﺻﻞ وﺟﻬﺎً ﻟﻮﺟﻪ‬
‫‪PRINCIPLES‬‬
‫‪Working product is the primary measure of‬‬
‫‪#7‬‬ ‫‪progress.‬‬

‫اﻟﻤﻨﺘﺠﺎت اﻟﺼﺎﻟﺤﺔ ﻟﻼﺳﺘﻌﻤﺎل )ﻗﺎﺑﻠﺔ ﻟﻠﻌﻤﻞ ﻓﻮراً ( ﻫﻲ اﻟﻤﻘﻴﺎس‬

‫اﻟﺮﺋﻴﺴﻲ ﻟﻤﺪي اﻟﺘﻘﺪم ﺑﺄﻋﻤﺎل اﻟﻤﺸﺮوع‪.‬‬
PRINCIPLES Agile processes promote sustainable development.
The sponsors, developers, and users should be able
#8 to maintain a constant pace indefinitely.

‫ وﻳﻨﺒﻐﻲ ﻋﻠﻰ اﻟﺮﻋﺎة‬.‫ﻧﻬﺞ اﻷﺟﺎﻳﻞ ﺗﺸﺠﻊ ﻋﻠﻲ اﻟﺘﻄﻮﻳﺮ ﺑﺸﻜﻞ ﻣﺴﺘﺪام‬

‫واﻟﻤﻄﻮرﻳﻦ واﻟﻤﺴﺘﺨﺪﻣﻴﻦ ﻟﻠﻤﻨﺘﺞ أن ﻳﻜﻮﻧﻮا ﻗﺎدرﻳﻦ ﻋﻠﻰ اﻟﺤﻔﺎظ‬
.‫ﻋﻠﻰ وﺗﻴﺮة ﻋﻤﻞ ﺛﺎﺑﺘﺔ ﻋﻠﻰ اﻟﺪوام‬
PRINCIPLES
Continuous attention to technical excellence and
# 09 good design enhances agility.

‫اﻻﻫﺘﻤﺎم اﻟﻤﺴﺘﻤﺮ ﺑﺎﻟﺘﻔﻮق اﻟﺘﻘﻨﻲ )ﻗﺪراﺗﻬﻢ اﻟﻔﻨﻴﺔ( واﻟﺘﺼﻤﻴﻢ‬

.‫اﻟﺠﻴﺪ ﻟﺘﻌﺰﻳﺰ اﻷﺟﺎﻳﻞ‬
‫‪PRINCIPLES‬‬
‫‪Simplicity - the art of maximizing the amount of‬‬
‫‪# 10‬‬ ‫‪work not done.‬‬

‫اﻟﺒﺴﺎﻃﺔ – وﻫﻮ ﻓﻦ ﺗﻌﻈﻴﻢ ﻣﻘﺪار اﻟﻌﻤﻞ ﻣﻦ ﺧﻼل ﻓﻬﻢ ﻣﺘﻄﻠﺒﺎت‬

‫اﻟﻌﻤﻴﻞ ﻣﻊ ﺗﻨﻔﻴﺬﻫﺎ ﺑﺄﺳﻂ اﻟﻄﺮق‪ ،‬واﻟﺤﺼﻮل ﻋﻠﻰ رد ﻓﻌﻞ‪ ،‬ﺛﻢ‬
‫ﺗﺤﺴﻴﻨﻬﺎ وﺗﻜﺮارﻫﺎ ﺣﺘﻰ ﻳﺘﻢ ﺗﻨﻔﻴﺬ اﻟﻘﺪر اﻷﻛﺒﺮ ﻣﻦ اﻟﻤﻨﺘﺞ‪.‬‬
PRINCIPLES
The best architectures, requirements, and designs
# 11 emerge from self-organizing teams.

‫إن أﻓﻀﻞ أﺳﻠﻮب وﻣﻮاﺻﻔﺎت وﺗﺼﻤﻴﻤﺎت ﺗﺨﺮج ﻣﻦ ﻓﺮق اﻟﻌﻤﻞ‬

.‫ذاﺗﻲ اﻟﺘﻨﻈﻴﻢ‬
PRINCIPLES At regular intervals, the team reflects on how to
become more effective, then tunes and adjusts its
# 12 behavior accordingly.

‫ﻓﺮﻳﻖ اﻟﻌﻤﻞ ﻳﻘﻮم ﺑﻤﺮاﺟﻌﺎت ﻋﻠﻰ ﻓﺘﺮات ﻣﻨﺘﻈﻤﺔ ﻟﻜﻴﻔﺔ ان ﻳﺼﺒﺢ‬

‫ ﺛﻢ ﻳﻘﻮم ﺑﺎﻟﺘﺪﻗﻴﻖ ﻣﻊ ﺿﺒﻂ ﺳﻠﻮك اﻟﻌﻤﻞ وﻓﻘﺎ‬،‫أﻛﺜﺮ ﻓﺎﻋﻠﻴﺔ‬
.‫ﻟﻤﺴﺘﺠﺪات اﻟﻌﻤﻞ‬
Questions
‫اﻷﺳﺌﻠﺔ‬
 Comparison between

Waterfall and Agile Methods

 INTRODUCTION
Comparison between Waterfall and Agile Methods

In the case of Waterfall methods:

 Each phase follows the other in linear sequence.
 The analysis phase can only start when the requirements phase is completed.
 Once analysis is done, the high-level design phase can start.
 Similarly, when design is completed, implementation can begin.
 When implementation is over, testing begins.
 Finally, once testing gets over, the team can proceed to deployment.

There is no provision to go back from one-step to its previous step(s).

 INTRODUCTION
Comparison between Waterfall and Agile Methods
 INTRODUCTION
Comparison between Waterfall and Agile Methods

In the case of Agile methods:

 Fixed time-boxed iterations or sprints, there is analysis, design, development & testing.
 A product increment that can be deployed for customer use.
 The team seeks feedback from the customers continuously, and
 Collaborate to add features, refactor the code and incorporate feedback incrementally.

Because of this working style, agile projects are able to respond to change
more flexibly and keep the product features thriving and up-to-date with the
latest developments in the industry.
 INTRODUCTION
Comparison between Waterfall and Agile Methods
 INTRODUCTION
Comparison between Waterfall and Agile Methods
 INTRODUCTION
Comparison between Waterfall and Agile Methods
 INTRODUCTION
Comparison between Waterfall and Agile Methods
Questions
‫اﻷﺳﺌﻠﺔ‬
DOMAIN
TASKS Agile Principles and Mindset

#1
9 Tasks
Exam Percentage: 16%
 Agile Principles and Mindset

Explore, embrace, and apply agile principles and mindset within the
context of the project team and organization.

.‫( وﻃﺮﯾﻘﺔ ﺗﻔﻜﯿﺮﮬﺎ وﻃﺮﻳﻘﺔ ﺗﻄﺒﻴﻘﮭﺎ ﺿﻤﻦ ﺳﯿﺎق ﻓﺮﯾﻖ اﻟﻤﺸﺮوع واﻟﻤﺆﺳﺴﺔ‬Agile)‫إﺳﺘﻜﺸﺎف ﻣﺒﺎدئ اﻟـ‬
 Agile Principles and Mindset

Domain Objectives:
 Agile and The Agile Manifesto
 The Twelve Agile Principles
 Waterfall & Agile Methods
 Agile Methodologies, Frameworks & Processes
 Information Radiators
 Knowledge Sharing
DOMAIN
TASKS Value-driven Delivery

#2
4 Sub-Domains, 14 Tasks
Exam Percentage: 20%
 Value-driven Delivery

Deliver valuable results by producing high-value increments for review,

early and often, based on stakeholder priorities. Have the stakeholders
provide feedback on these increments, and use this feedback to
prioritize and improve future increments.

‫ﺑﻨﺎء ﻋﻠﻰ‬
ً ً‫ ﻣﺒﻜﺮاً وﻣﺘﻜﺮرا‬،‫ﻗﯿﻤﺔ ﻣﻦ ﺧﻼل إﻧﺘﺎج ﻣﻨﺘﺠﺎت ﻋﺎﻟﯿﺔ اﻟﻘﯿﻤﺔ ﺑﺸﻜﻞ ﻣﺘﺰاﻳﺪ ﻟﻠﻤﺮاﺟﻌﺔ ﻣﻦ ﻗﺒﻞ اﻟﻌﻤﻴﻞ‬
ّ ‫ﺗﻘﺪﻳﻢ ﻧﺘﺎﺋﺞ‬
ّ
.‫ وإﺳﺘﺨﺪم ﮬﺬه اﻟﻤﻼﺣﻈﺎت ﻟﺘﺮﺗﯿﺐ اﻷوﻟﻮﯾﺎت اﻟﻤﺴﺘﻘﺒﻠﯿﺔ ﻣﻊ ﺗﺤﺴﯿﻨﮭﺎ‬،‫ ﺗﻘﺪﯾﻢ اﻟﻤﻌﻨﯿﯿﻦ ﻟﻠﻤﻼﺣﻈﺎت‬.‫أوﻟﻮﯾﺎت اﻟﻤﻌﻨﯿﯿﻦ‬
 Value-driven Delivery

Domain Objectives:
 Value & Prioritization
 Product Backlog
 Metrics and KPI’s
 Reviews & Feedback
 EVM Terminologies
 Agile Contracts
DOMAIN
TASKS Stakeholder Engagement

#3
3 Sub-Domains, 9 Tasks
Exam Percentage: 17%
 Stakeholder Engagement

Engage current and future interested parties by building a trusting

environment that aligns their needs and expectations and balances
their requests with an understanding of the cost/effort involved.

Promote participation and collaboration throughout the project life

cycle and provide the tools for effective and informed decision making.

‫أﺷﺮك اﻷﻃﺮاف اﻟﺤﺎﻟﯿﺔ واﻟﻤﺴﺘﻘﺒﻠﯿﺔ اﻟﻤﮭﺘﻤﺔ ﻋﻦ ﻃﺮﯾﻖ ﺑﻨﺎء ﺑﯿﺌﺔ ﻣﻦ اﻟﺜﻘﺔ ﻣﻊ اﻟﺘﻮاﻓﻖ ﺑﯿﻦ إﺣﺘﯿﺎﺟﺎﺗﮭﻢ وﺗﻮﻗﻌﺎﺗﮭﻢ وﺗﻮازن‬
ِ
‫ﺗﻘﺪﻳﻢ‬
ّ ‫اﻟﺘﺮوﻳﺞ ﻟﻠﻤﺸﺎرﻛﺔ واﻟﺘﻌﺎون ﻋﻠﻰ إﻣﺘﺪاد دورة ﺣﯿﺎة اﻟﻤﺸﺮوع ﻣﻊ‬
ّ .‫اﻟﺠﮭﺪ اﻟﻤﺒﺬول‬/‫ﺑﻔﮭﻢ ﻟﻠﺘﻜﻠﻔﺔ‬
ٍ ‫ﻃﻠﺒﺎﺗﮭﻢ وذﻟﻚ‬
.‫اﻷدوات اﻟﻼزﻣﺔ ﻻﺗﺨﺎذ ﻗﺮارات ﻓﻌﺎﻟﺔ وﻣﻄﻠﻌﺔ‬
 Stakeholder Engagement

Domain Objectives:
 Stakeholder Management.
 Project Charter.
 Wireframes, User Story, Personas & Theme and Epic.
 Agile Story Maps & Communication.
 Agile Modeling & Active Listening.
 Agile Negotiation.
DOMAIN
TASKS Team Performance

#4
3 Sub-Domains, 9 Tasks
Exam Percentage: 16%
 Team Performance

Create an environment of trust, learning, collaboration, and conflict

resolution that promotes team self-organization, enhances
relationships among team members, and cultivates a culture of high
performance.

‫ وﺗﻌﺰز اﻟﻌﻼﻗﺎت‬،‫ واﻟﺘﻌﺎون وﺣﻞ اﻟﻨﺰاﻋﺎت ودﻋﻢ ﻣﻔﮭﻮم اﻟﺘﻨﻈﯿﻢ اﻟﺬاﺗﻲ ﻟﻔﺮﻳﻖ اﻟﻌﻤﻞ‬،‫ ﻣﻊ اﻟﺘﻌﻠﻢ‬،‫ﺧﻠﻖ اﻟﺜﻘﺔ ﻓﻲ ﺑﯿﺌﺔ اﻟﻌﻤﻞ‬
.‫ﺑﯿﻦ أﻋﻀﺎء اﻟﻔﺮﯾﻖ وﻏﺮس ﺛﻘﺎﻓﺔ اﻷداء اﻟﻌﺎﻟﻲ‬
 Team Performance

Domain Objectives:
 Team Formation.
 Team Empowerment.
 Team Collaboration and Commitment.
 Communication in Agile Teams.
 Agile Contracting.
 Agile PMO.
DOMAIN
TASKS Adaptive Planning

#5
3 Sub-Domains, 10 Tasks
Exam Percentage: 12%
 Adaptive Planning

Produce and maintain an evolving plan, from initiation to closure, based

on goals, values, risks, constraints, stakeholder feedback, and review
findings.

‫ﺑﻨﺎء ﻋﻠﻰ اﻷﮬﺪاف واﻟﻘﯿﻢ‬

ً ،‫ ﻣﻦ ﻣﺮﺣﻠﺔ اﻟﺒﺪاﻳﺔ وﺣﺘﻰ ﻣﺮﺣﻠﺔ اﻷﻏﻼق‬،‫وﺿﻊ وﺗﻘﺪﻳﻢ ﺧﻄﺔ ﻣﺘﻄﻮرة ﻣﻊ اﻟﻤﺤﺎﻓﻈﺔ ﻋﻠﯿﮭﺎ‬
.‫واﻟﻤﺨﺎﻃﺮ واﻟﻘﯿﻮد وﻣﻼﺣﻈﺎت اﻟﻤﻌﻨﯿﯿﻦ وﻣﺮاﺟﻌﺔ ﻟﻠﻨﺘﺎﺋﺞ‬
 Adaptive Planning

Domain Objectives:
 Multiple Levels of Planning & Estimation
 Measures of Project Size
 Relative Sizing & Story Points
 Estimation Scale
 Wideband Delphi & Planning Poker
 Affinity Estimation
 Estimation Using T-Shirt Sizing
DOMAIN
TASKS Problem Detection and Resolution

#6
5 Tasks
Exam Percentage: 10%
 Problem Detection and Resolution

Continuously identify problems, impediments, and risks; prioritize and

resolve in a timely manner; monitor and communicate the problem
resolution status; and implement process improvements to prevent
them from occurring again.

‫ وﻣﺘﺎﺑﻌﺔ وﺿﻊ ﺣﻞ‬،‫ﺗﺤﺪﻳﺪ اﻟﻤﺸﻜﻼت واﻟﻤﻮاﻧﻊ واﻟﻤﺨﺎﻃﺮ ﺑﺈﺳﺘﻤﺮار؛ ﻣﻊ ﺗﺮﺗﻴﺐ ﻟﻸوﻟﻮﯾﺎﺗﮭﺎ وﺣﻠﮭﺎ ﻓﻲ اﻟﻤﻮﻋﺪ اﻟﻤﻨﺎﺳﺐ‬
. ً‫ﻟﻠﻤﺸﻜﻼت وواﻟﺘﻮاﺻﻞ ﺑﺨﺼﻮﻫﺎ ﻣﻊ اﻵﺧﺮﯾﻦ؛ وﺗﻨﻔﻴﺬ اﻟﺘﺤﺴﯿﻨﺎت ﻋﻠﻰ اﻟﻌﻤﻠﯿﺎت ﻟﻤﻨﻊ ﺣﺪوق اﻟﻤﺸﺎﻛﻞ ﻣﺠﺪدا‬
 Problem Detection and Resolution

Domain Objectives:
 Agile Problem Detection.
 Cumulative Flow Diagrams.
 Agile Problem-Solving.
 Metric and Measure.
 Risk Management in Agile.
 Agile Failure Modes.
DOMAIN
TASKS Continuous Improvement

#7
6 Tasks
Exam Percentage: 9%
 Continuous Improvement

Continuously improve the quality, effectiveness, and value of the

product, the process, and the team.

.‫ﺗﺤﺴﻴﻦ اﻟﺠﻮدة واﻟﻔﻌﺎﻟﯿﺔ وﻗﯿﻤﺔ اﻟﻤﻨﺘﺞ واﻟﻌﻤﻠﯿﺎت وﻓﺮﯾﻖ اﻟﻌﻤﻞ ﺑﺈﺳﺘﻤﺮار‬

ّ
 Continuous Improvement

Domain Objectives:
 Kaizen.
 Retrospectives & Quality in Agile.
 Acceptance Test-Driven Development Cycle.
 Value Stream Mapping & Seven Forms of Waste.
 Agile Flowcharts & Spaghetti Diagrams.
 Written Communication in Agile.
 Facilitated Workshops.
Questions
‫اﻷﺳﺌﻠﺔ‬
‫‪Break‬‬
‫إﺳﺘﺮاﺣﺔ‬
 SHU HA RI
守破離
T H E S TAG E S O F LE ARN IN G TO MAS T E R Y
 SHU
FOLLOW THE RULE
Learning while conforming to the rules
 HA
ADAPTE AND LEARN NEW RULES
Developing one’s own style, breaking some rules
 RI
BE THE RULE
Building one’s own rules
Questions
‫اﻷﺳﺌﻠﺔ‬
‫‪Break‬‬
‫إﺳﺘﺮاﺣﺔ‬
THANKS
ً
‫ﺷﻜﺮا‬