Post on 01-Jan-2016
description
Spot a Failing project
Costs a lot more than it should
Its takes longer than anyone expected
The product doesn’t do what it was supposed to
Nobody is happy about it
Why “Agile”? Project priorities change
Increasing need for reduced time-to-market and enabling frequent delivery
Make application releases more predictive
Improve customer involvement
Learning and responding to customer needs is critical in today’s business environment
SCRUM
Continuous Quality up front in process decreases Risk &
Cost!
Demos and Retrospectivesare part of the
Continuous Improvement
loop
Changes/
Requirements from stakeholders or
Project Sponsor go as user stories on
the backlog and get prioritized by the
Chief Product Owner
Deliverable -Working Software!
Choose a pilot project
Form teams by product lines or functional areas
Engage a Champion or Agile Coach if team is new to Agile
Inspect, learn and adapt
Set Agile adoption timeline
…model the same in other projects to get a true Portfolio adoption
Q1 Q2 Q3 Q4
Project 1
Project 2
Project 3
SCRUM SCRUM
SCRUMScaled Agile
Release Plan
PSI 1 PSI 2 PSI 3 PSI 4 PSI 4 PSI 5
2015
10-12 Wks 10-12 Wks 10-12 Wks 10-12 Wks 10-12 Wks 10-12 Wks
Deve
lop
men
t S
pri
nt
1
Deve
lop
men
t S
pri
nt
2
Deve
lop
men
t S
pri
nt
3
Deve
lop
men
t S
pri
nt
4
HIP
Sp
rin
t
Deve
lop
men
t S
pri
nt
1
Deve
lop
men
t S
pri
nt
2
Deve
lop
men
t S
pri
nt
3
Deve
lop
men
t S
pri
nt
4
HIP
Sp
rin
t
Deve
lop
men
t S
pri
nt
1
Deve
lop
men
t S
pri
nt
2
Deve
lop
men
t S
pri
nt
3
Deve
lop
men
t S
pri
nt
4
HIP
Sp
rin
t
Deve
lop
men
t S
pri
nt
1
Deve
lop
men
t S
pri
nt
2
Deve
lop
men
t S
pri
nt
3
Deve
lop
men
t S
pri
nt
4
HIP
Sp
rin
t
Deve
lop
men
t S
pri
nt
1
Deve
lop
men
t S
pri
nt
2
Deve
lop
men
t S
pri
nt
3
Deve
lop
men
t S
pri
nt
4
HIP
Sp
rin
t
Deve
lop
men
t S
pri
nt
1
Deve
lop
men
t S
pri
nt
2
Deve
lop
men
t S
pri
nt
3
Deve
lop
men
t S
pri
nt
4
HIP
Sp
rin
t
Rele
ase
Rele
ase
Rele
ase
Rele
ase
Rele
ase
Project 1
Project 3
Project 2
Project 4
Rele
ase
Product owner cloud
Chief Product Owner
SPAIN
CHINA CANADA
INDIA
TURKEY
JAPAN
UK
BRAZILMEXICO
GERMANY
Scrum Team 2
Scrum Team 3
Scrum Team 4
Scrum Team 5
Scrum Team 1
Identify and Mitigate Risks
Some projects are time bound with hard dates, transition to a new method may cause disruption for in-flight waterfall projects.
Budget considerations for Agile Training
Resource constraints, time commitment is heavy.
Engagement with Systems teams
Choose a pilot project in the initial phases
Tap into internal community of practitioners and champions
Set the staffing plans for project/program with the demand signals for resource needs
Establish working agreements with the Systems teams
Risks Mitigation Plan
Role of Agile Project Manager
Manage stakeholder communication
Enable rather than control
Ensure project meets its goals and objectives
Removes Roadblocks
Benefits of moving to AgileAllows us to become more lean and deliver faster on things that
matter more to business
Flexibility to respond faster to changing customer needs
Manage interdependencies across the Program
Allows for dealing with ambiguity
Fosters Innovation
“Software applications developed through the agile process have three times the success rate of the traditional waterfall method and a much lower percentage of time and cost overruns”**
**Source- 2011 CHAOS report from the Standish Group
Recommendations Co-located Scrum teams with a dedicated collaboration room.
Time commitment from the customer, >20 hours a week. 2- 3 full days or half days every week
Cross-Pollination – Bring Mature Agile teams or Champions from other parts of your organization to set up the pilot Project/Program space
Establish working agreements with shared systems teams
Leadership buy-in and alignment across IT function and customer area
Training sessions for the team and mentoring during transition
Progressively increase Agile capability by evolving into Scaled Agile Framework
Feedback and Questions
I would love to hear from you
Contact me at archmehta@hotmail.com