مدیریت پروژه چابک براساس استاندارد مدیریت پروژه
سیزدهمین کنفرانس بینالمللی مدیریت پروژه در بهمن ماه سال 1396 در ایران-تهران-محل تالار همایشهای بینالمللی رازی، با حضور و مشارکت بیش از هزار نفر از کارشناسان و مدیران سازمانهای گوناگون کشور برگزار گردید.
دکتر محمد احمدزاده در این همایش، بعنوان اولین ایرانی دارنده مدرک بین المللی مدیریت پروژه چابک و همچنین به عنوان مشاور و مدرس دوره های مدیریتی، در کارگاه تخصصی خود با عنوان «مدیریت پروژه چابک با رویکرد استاندارد مدیریت پروژه (ویرایش ششم)»، ضمن بیان مفاهیم و زیرساختهای مدیریت پروژه چابک، به بررسی نمونههای عملیِ پیادهشده در سازمانهای ایرانی پرداختند.
پرزنت این ارائه در اینجا به اشتراک گذاشته شده است.
جهت اطلاع از سایر خدمات آموزشی و مشاوره ای دکتر محمد احمدزاده، به آدرس وب سایت ایشان مراجعه فرمائید.
(www.mohammad-ahmadzadeh.com)
#PMBOK
#مدیریت_پروژه
چابک#
The 13th International Project Management Conference was held in Iran-Tehran in February 2018 at the Forum of International Razi Conferences, with the participation of more than 1,000 experts and managers from different organizations of the country.
At this conference, Dr. Mohammad Ahmadzadeh (Ph.D., PMP, ACP) as the first Iranian holder of international Agile Certified Practitioner (ACP) from PMI and also as the consultant and lecturer in management courses, presented the topic of "Agile Project Management Based on PMBOK-V6" (Sixth Edition).
He not only expressed the concepts and infrastructure of agile project management, but also reviewed the practical examples of the Iranian organizations.
His presentation shares here and for more information about Dr. Mohammad Ahmadzadeh educational and consulting services; you may click on his website.
(www.mohammad-ahmadzadeh.com)
21. 09128238168و2748640-021
WWW.MOHAMMAD-AHMADZADEH.COM
M.AHMADZADEH.GH@UT.AC.IR
• Predictive (Waterfall)
• scope, time, and cost are determined in the early phases of the life cycle
• Iterative
• Project scope is generally determined early in the project life cycle, but time and cost
estimates are routinely modified as the project team’s understanding of the product
increases.
• Iterations develop the product through a series of repeated cycles
• Incremental
• the deliverable is produced through a series of iterations that successively add
functionality within a predetermined time frame.
• Adaptive (Agile Or Change Driven, Iterative & Incremental)
• The detailed scope is defined and approved before the start of an iteration.
• Hybrid (combination of a predictive and an adaptive life cycle)
• Those elements of the project that are well known or have fixed requirements follow
a predictive development life cycle, and those elements that are still evolving follow
adaptive development life cyle.
Development Life Cycle
PMBOK-2017 Page 19.
Development Life Cycles
38. 09128238168و2748640-021
WWW.MOHAMMAD-AHMADZADEH.COM
M.AHMADZADEH.GH@UT.AC.IR
Considerations For Agile (Integration)
Agile promote the engagement of team members.
Team members determine how plans and components should integrate.
Control of the detailed product planning and delivery is delegated to the team.
The PM’s focus is on building a collaborative decision-making environment
PM Ensures the team has the ability to respond to changes.
In Agile, deliverables are developed over multiple iterations where a detailed scope is defined
and approved for each iteration when it begins.
Customer representatives should be continuously engaged with the project to provide
feedback on deliverables as they are created.
Customer representatives should ensure that the product backlog reflects their current needs.
PMBOK-2017 Page 74 & 131.
40. 09128238168و2748640-021
WWW.MOHAMMAD-AHMADZADEH.COM
M.AHMADZADEH.GH@UT.AC.IR
Considerations For Agile (Scope)
Two processes (Validate Scope and Control Scope) are repeated for each iteration.
Validate Scope occurs with each deliverable or phase review and Control Scope is an ongoing
process.
Agile methods deliberately spend less time trying to define and agree on scope in the early
stage of the project and spend more time establishing the process for its ongoing discovery
and refinement.
agile methods purposefully build and review prototypes and release versions in order to refine
the requirements. As a result, scope is defined and redefined throughout the project.
In agile approaches, the requirements constitute the backlog.
If an agile approach is used, epics can be decomposed into user stories.
PMBOK-2017 Page 133 & 160.
43. 09128238168و2748640-021
WWW.MOHAMMAD-AHMADZADEH.COM
M.AHMADZADEH.GH@UT.AC.IR
Considerations For Agile (Schedule)
The project management team selects a scheduling method, such as critical path or an agile
approach.
Iterative scheduling with a backlog (Form of rolling wave planning based on Agile)
Agile use short cycles to undertake work, review the results, and adapt as necessary.
Agile provides rapid feedback on the approaches and suitability of deliverables.
In Agile, the activity list will be updated periodically as the project progresses.
Decision Making (a Voting method that is often used in agile-based projects is called the fist of
five (also called fist to five).
Meetings: (In Agile approach, team conduct sprint or iteration planning meetings to discuss
prioritized product backlog items (user stories) and decide which of these items the team will
commit to work on in the upcoming iteration.
PMBOK-2017 Page 178 & 185, 203.
45. 09128238168و2748640-021
WWW.MOHAMMAD-AHMADZADEH.COM
M.AHMADZADEH.GH@UT.AC.IR
Considerations For Agile (Control Schedule)
PMBOK-2017 Page 224.
Determining the current status of the project schedule by comparing the total amount of work
delivered and accepted against the estimates of work completed for the elapsed time cycle;
Conducting retrospectives (scheduled reviews to record lessons learned) for correcting
processes and improving, if required;
Reprioritizing the remaining work plan (backlog);
Determining the rate at which the deliverables are produced, validated, and accepted (velocity) in
the given time per iteration (agreed-upon work cycle duration, typically 2 weeks or 1 month);
Determining that the project schedule has changed.
Managing the actual changes as they occur.
46. 09128238168و2748640-021
WWW.MOHAMMAD-AHMADZADEH.COM
M.AHMADZADEH.GH@UT.AC.IR
Considerations For Agile (Quality)
PMBOK-2017 Page 276, 290.
In agile, stakeholder engagement with the team ensures customer satisfaction is maintained
throughout the project.
For better change management, agile calls for frequent quality and review steps built in throughout
the project rather than toward the end of the project.
Recurring retrospectives regularly check on the effectiveness of the quality processes.
Looking for the root cause of issues then suggest trials of new approaches to improve quality.
In order to facilitate frequent, incremental delivery, agile methods focus on small batches of work,
incorporating as many elements of project deliverables as possible.
Small batch systems aim to uncover quality issues earlier in the project life cycle when the overall
costs of change are lower.
In agile projects, quality management is performed by all team members throughout the project.
48. 09128238168و2748640-021
WWW.MOHAMMAD-AHMADZADEH.COM
M.AHMADZADEH.GH@UT.AC.IR
Considerations For Agile (HR)
PMBOK-2017 Page 310.
Self-organizing teams: where the team functions with an absence of centralized control.
In projects that have self-organizing teams, the project manager (who may not be called
a project manager) role provides the team with the environment and support needed and
trusts the team to get the job done.
Collaboration is intended to boost productivity and facilitate innovative problem solving.
Collaborative teams may facilitate accelerated integration of distinct work activities,
improve communication, increase knowledge sharing, and provide flexibility of work
assignments.
49. 09128238168و2748640-021
WWW.MOHAMMAD-AHMADZADEH.COM
M.AHMADZADEH.GH@UT.AC.IR
Team charter is a document that establishes the team values, agreements, and operating guidelines for team.
It establishes clear expectations regarding acceptable behavior by project team members.
It decreases misunderstandings and increases productivity.
Discussing areas such as codes of conduct, communication, decision making, and meeting etiquette allows
team members to discover values that are important to one another.
It can be reviewed and updated periodically to ensure a continued understanding of the team ground rules and
to orient and integrate new team members.
The team charter may include but is not limited to:
Team values,
Communication guidelines,
Decision-making criteria and process,
Conflict resolution process,
Meeting guidelines, and
Team agreements
Considerations For Agile (HR)-Team Charter
61. 09128238168و2748640-021
WWW.MOHAMMAD-AHMADZADEH.COM
M.AHMADZADEH.GH@UT.AC.IR
Short, daily standup meetings, where the achievements and issues of the
previous day, and plans for the current day’s work, are discussed with the project
team and key stakeholders.
team member access to information, frequent team checkpoints, and
collocating team members as much as possible.
Posting project artifacts in a transparent fashion, and holding regular
stakeholder reviews are intended to promote communication with management
and stakeholders.
Considerations For Agile (Communication)
PMBOK-2017 Page 364.
62. 09128238168و2748640-021
WWW.MOHAMMAD-AHMADZADEH.COM
M.AHMADZADEH.GH@UT.AC.IR
Considerations For Agile (Risk)
PMBOK-2017 Page 400.
Use of frequent reviews of incremental work products and cross-functional project
teams to accelerate knowledge sharing and ensure that risk is understood and
managed.
Risk is considered when selecting the content of each iteration, and risks will also be
identified, analyzed, and managed during each iteration.
Requirements are kept as a living document that is updated regularly, and work may
be reprioritized as the project progresses, based on an improved understanding of
current risk exposure.
Performing Qualitative Risk Analysis process is conducted before the start of each
iteration.
64. 09128238168و2748640-021
WWW.MOHAMMAD-AHMADZADEH.COM
M.AHMADZADEH.GH@UT.AC.IR
Considerations For Agile (Procurement)
PMBOK-2017 Page 465.
Specific sellers may be used to extend the team.
This collaborative working relationship can lead to a shared risk procurement model where
both the buyer and the seller share in the risk and rewards associated with a project.
Larger projects may use an adaptive approach for some deliverables and a more stable
approach for other parts.
In these cases, a governing agreement such as a master services agreement (MSA) may
be used for the overall engagement, with the adaptive work being placed in an appendix or
supplement.
This allows changes to occur on the adaptive scope without impacting the overall
contract.
65. 09128238168و2748640-021
WWW.MOHAMMAD-AHMADZADEH.COM
M.AHMADZADEH.GH@UT.AC.IR
Considerations For Agile (Stakeholders)
PMBOK-2017 Page 465.
Client, user, and developer exchange information in a dynamic co-creative
process that leads to more stakeholder involvement and higher satisfaction.
In order to accelerate the sharing of information within and across the
organization, agile methods promote aggressive transparency.
The intent of inviting any stakeholders to project meetings and reviews or
posting project artifacts in public spaces is to surface as quickly as possible any
misalignment, dependency, or other issue related to the changing project.