1
Beyond Rituals…
By
Saket Bansal
iZenBridge Consultancy Private Limited (PMI – REP)
2
Do IT Projects fail?
• The majority of them fails to meet cost and schedule
baselines
3
Top Reasons
• Unclear Business Objectives
• Changing Requirements
• The team is not aligned of Focused
• Unrealistic schedule / Reactive Planning
• Poor Risk management
4
Tom Demarco and Tim Lister’s Five Core Risk
Areas
• Intrinsic Schedule Flaw
• Specification Breakdown
• Scope Creep
• Personnel Loss
• Productivity Variation
5
Wonder !!
• No one spoke about project failing because of any
given methodology !!!!
6
Agile Has a Solution
7
Agile Has a Solution
Issue Individual &
Interaction
Working
Software
Customer
Collaboration
Responding
to Change
Unclear
Business
Objectives
Changing
Requirements
Team is not
aligned or
Focused
Unrealistic
schedule
8
Tom DeMarco and Tim Lister’s Five Core Risk
Areas
Individual &
Interaction
Working
Software
Customer
Collaboration
Responding
to Change
Intrinsic
Schedule Flaw
Specification
Breakdown
Scope
Creep
Personnel
Loss
Productivity
Variation
9
But the problem is… many projects still fail…
10
Companies moving from one methodology to
another and not finding solution …
11
Do You Agree With Ken Schwaber?
“I estimate that 75% of those
organizations using
scrum will not succeed
in getting the benefits
that they hope for from it.”
12
Major Reason of Agile Project Failure…
• Company Philosophy – Culture mismatch
13
Sprint Planning
Expected
• What can be done this Sprint?
• Team Identify how the chosen
work gets done?
Observed
• PO Already Committed the sprint
goals
• Scrum Master leads the sprint
planning
Sprint is understood as
timeboxed and fixed-commitment iteration
14
Daily Standup
Expected
• Inspect progress toward the Sprint
Goal
• The team plan to accomplish the
Sprint Goal
• Followed by discussions to adapt
or re-plan
Observed
• Implements not shared
• Status Report to Scrum master
• Little done to bring things on track
Daily standup is just looked at as a Status Meeting
15
Sprint / Product Review
Expected
• The team demonstrates the
working software to stakeholders
• The Product Owner discusses and
project likely completion dates
based on progress
• Review of the timeline, budget,
potential capabilities, and
marketplace for the next
anticipated release of the product.
Observed
• PO / Stakeholders keeps asking
the project completion date
forecast
• Scrum master projects when
things are going to finish
• Stakeholders disappear for long
and when they come back they
are shocked
16
Retrospective
Expected
• Inspect how the last Sprint went
with regards to people,
relationships, process, and tools
• Create a plan for implementing
improvements
Observed
• Focus on who did what
• Scrum master asking questions
• Team Complaining to Scrum
master
• No or little action on actions
identified in previous retrospective
17
Coaching / Mentoring
Expected
• Coaching
• Theory Y
Observed
• Directing
• Theory X
18
Missing ….
19
Performance Monitoring
Outcome
Output
Activities
20
New Waste …
Documents Meetings
21
It's Difficult to Get
• Value Without customer engagement
• Self-organization and Ownership Without employee
engagement
22
• If members of a team don't care
about a project, nothing can
save it.
- Kent Beck , Extreme
Programming Explained
23
Fertilizer Project
24
Strategy
Portfolio
Product Roadmap
Release
Iteration
Day
25
Customer / Vendor
Release
Iteration
Day
Project /
Account
Road Map
Portfolio
Strategy
Portfolio
Strategy
26
The Value Stream
27
OVERVIEW OF PMI-ACP®
28
• For practitioners, PMI-ACP® helps:
Demonstrate a level of professionalism in Agile
principles, practices, tools and techniques
Increase professional versatility in project
management
• For organizations, PMI-ACP® demonstrates a
practitioner’s:
Knowledge of Agile practices, which shows the
practitioner has greater breadth and depth as a PM
The Value of PMI-ACP®
29
Requirement Description
Educational Level Secondary degree or higher
General Project
Experience 2,000 hours working on project teams.
Agile Experience 1,500 hours working on Agile project teams.
Agile Training 21 contact hours
Examination Tests knowledge of Agile fundamentals and ability to apply to
basic projects
Maintenance 30 PDUs/3 CEUs every 3 years in Agile project management
Cost $435 member; $495 non-member
PMI-ACP – Eligibility Requirements
30
Stay Connected
Email : [email protected]
YouTube : www.youtube.com/izenbridge
Twitter : @Saket_tg
Website : www.pmi.org ; www.iZenBridge.com
31
Questions?