Hybrid approach for project management,9 10-2012
-
Upload
niranjan-nerlige-v-csmcsppmi-acpspc -
Category
Software
-
view
74 -
download
1
Transcript of Hybrid approach for project management,9 10-2012
Hybrid Approach for Project Management – Traditional & Agile
By
Niranjan Nerlige V, M.Tech (IIT, Bombay), PMI-ACP, CSP , CSM
Founder, Agile Coach - Exelplus Services and
Consultant -Unicom
Date: 17th, Oct, 2012
1 Copy Right Protected
1
Project Management Conference Held by On August, 2012, Bengaluru, India
Business in the Past
Copy Right Protected
Stand alone systems
Stable Requirements
Enough Time to Market
Requirements drive custom, “ Complete
Solution”
Changing World – Rapidity in Business
4
Mobile Phones 10-15 years back
Latest Mobile Phones Dynamic Market Requirements
Copy Right Protected
Changing World – Rapidity in Business
5
TVs 10-15 years back
Latest TVs
End Users Needs are changing very fast
Copy Right Protected
Agility?
6
Rapidity in Business Changes
Need for agility to respond more effectively to
change.
Any Enterprise that aspires to respond in real time must have the ability to be agile when needed
Copy Right Protected
Agility = Adaptability
Industry Results Studies , Surveys
Source: WHAT IS THE ROI OF AGILE VS. TRADITIONAL METHODS? An analysis of XP, TDD, Pair Programming, and Scrum (Using Real Options) Dr. David F. Rico, PMP, CSM
Delivery Time, Productivity, Quality , Customer Satisfaction and ROI are high in Agile Methods
Copy Right Protected
7
Industry Results Studies , Surveys
Reasons Respondents (Very High in Agile)
Accelerate Time to Market 77 %
Manage Changing Priorities 83%
Increased Productivity 89%
Better IT Align and Business 65%
Enhance Software Quality 81%
Project Visibility 60%
Reduce Risks 62%
Simple development Process 57%
Agile Development Survey 2011– Version One
Copy Right Protected 8
Applicability of Traditional and Agile
Copy Right Protected
Source: Balancing Agility and Discipline by
Barry Boehm and Turner
Barry Boehm and Turner Radar Chart
Need for Hybrid Approach for Project Mgmt.
• Both Waterfall and Agile has good points
• Need a Right Solution for the Situation at Hand
• Every Project has some constraints and characteristics = Difficulty to fit to any defined standard framework
• There´s no cake recipe for project success.
• An experienced project manager should be able to define the best approach for each project context
10
Copy Right Protected
• Some Clients expect approximate budget, Time
up-front and Initial Scope Commitment – Not easy in Agile approach
Copy Right Protected
Motivation For Hybrid Approach – Contd……
11
What is Hybrid Project Management Approach ?
Copy Right Protected
WATER FALL
Some formality in the beginning
12
Waterfall Approach - Strengths
Copy Right Protected
• Formality • Focused on Requirements • Upfront planning • Expects Predictability
13
Agile Approach - Strengths
Incremental
Iterative
Strengths of Agile development: • Early and Frequent feedback, user engagement, and adaptation • Early mitigation of risks • Early visible progress. • Managed Complexity • Learning within an iteration.
Copy Right Protected 14
How Hybrid Approach Works?
Copy Right Protected
Initiation and Requirements
Execution using Scrum Release
• Project Initiation • High Level
Requirements agreement
• Top level Architecture
• Define the product Back log, • Prioritize user stories, • Sprints Planning, • Daily Stand ups, • Sprint Reviews, • Sprint Retrospectives • TDD approach for Unit
Testing
• Pre Release activities • System testing • Load tests, Stress tests,
performance tests • Light Weight “User
acceptance testing”
Waterfall Agile Waterfall or
Agile - optional
15
Copy Right Protected
Mozilla has also begun using a hybrid model that incorporates elements of both agile and waterfall approaches for its flagship Firefox Web browser. The goal is to more quickly introduce new features -- aided by agile's emphasis on iterative releases
Said Mozilla's director of Firefox, Mike Beltzner:
Really, we're not tied to any specific development model. We're tied to what is effective.
Thank You For Your Time …………..
Niranjan Nerlige V, M.Tech ( IIT-B), PMI-ACP, CSP, CSM. Mobile: 99000 55943 E-Mail: [email protected]
17
Copy Right Protected
The Traditional Approach
22
Requirements Gathering
Design
Development
Testing
Rework
Documentation, Signoffs, Handoff
Documentation, Signoffs, Handoff
Documentation, Signoffs, Handoff
Documentation, Signoffs, Handoff
Job Function A Job Function B Job Function C Job Function D Job Function E
Niranjan Nerlige V, Copy Right Protected
Copy Right Protected
Software Development Methodology
Water Fall Iterative
Agile
Niranjan Nerlige V, Copy Right Protected
Development Methodology Classification
23
Copy Right Protected
Agile: Iterative Software Development
24
Feature A Design Develop Test Rework
Feature B Design Develop Test Rework
Feature C Design Develop Test Rework
Feature D Design Develop Test Rework
Feature E Design Develop Test Rework
Cross-Functional Team (Designers, Developers, Testers)
24 Niranjan Nerlige V, Copy Right Protected
Copy Right Protected
The Agile Manifesto–a statement of values
25
Process and tools Individuals and
interactions over
Following a plan Responding to
change over
Source: www.agilemanifesto.org
Comprehensive
documentation Working software over
Contract negotiation Customer
collaboration over
Niranjan Nerlige V, Copy Right Protected
Copy Right Protected
Business Value
26
100
90
80
70
60
50
40
30
20
10
0
Bu
sin
ess V
alu
e %
Month 1 Month 2 Month 3 Month 4 Month 5 Month 6
Niranjan Nerlige V, Copy Right Protected
Source: Thanks to Peter Deemer
Copy Right Protected
Uncertainty and Risk
27
100
90
80
70
60
50
40
30
20
10
0
Un
ce
rta
inty
an
d R
isk %
Month 1 Month 2 Month 3 Month 4 Month 5 Month 6
Niranjan Nerlige V, Copy Right Protected
Source: Thanks to Peter Deemer
Copy Right Protected
The Problems Many Companies Face
28 Niranjan Nerlige V, Copy Right Protected
Source: Thanks to Peter Deemer
Copy Right Protected
Companies starting to use Scrum to Achieve Success
29
Source: Thanks to Peter Deemer
Copy Right Protected
The Essence of Scrum
31
Time box
Inspect No Changes
Commit
Adapt
Niranjan Nerlige V, Copy Right Protected
Copy Right Protected
Scrum Basics
32
Daily 15-minute
“Stand-up” Meeting
The Team 30-day
“Sprint”
of Work
Product Owner
1
2
3
4
5
6
7
8
Prioritized List
of Requirements
(product back log)
Team Makes
Commitment
for the Sprint (Sprint Backlog)
Sprint Review
Scrum
Master
Input from End-Users, Customers, Team and Other Stakeholders
Team Selects
How Much To
Commit To Do
By Sprint’s End
Potential Shippable
code
Niranjan Nerlige V, Copy Right Protected
Copy Right Protected