all rights reserved © alcatel-lucent 2010 almr project management in agile mode olivier pony –...
TRANSCRIPT
All Rights Reserved © Alcatel-Lucent 2010
ALMR Project Management
in Agile mode
Olivier PONY – October 2010
2
ALMR Project Management in Agile modeAgenda
ALMR Product Roadmap Global View Q4 2010 to Q4 2011 IT Project Gates - Waterfall Style IT Project Gates - Agile Style
Details about Agile Agile Software Development Timeline ALMR Release Plan Motivations to move towards Agile Measuring Improvements
3
ALMR Project Management in Agile modeALMR Product Roadmap
Q4 2010 Q1 2011 Q2 2011 Q3 2011 Q4 2011
Business view of detailed ALMR enhancement priorities is <3 months
So we commit on release scope, check, and deploy every 3 monthsCommit
Check
Deploy
In Waterfall Projects, 1 project = 1 commitment/check/deployment
ALMR 5 ALMR 6 ALMR 7 ALMR 8 ALMR 9
In Agile Projects, 1 project = X commitments/checks/deployments
Next slides show the IT
gates
ALMR 5 ALMR 6 ALMR 7 ALMR 8 ALMR 9
4
ALMR Project Management in Agile modeALMR Product Roadmap and IT Project Gates - Waterfall Style
Q4 2010 Q1 2011 Q2 2011 Q3 2011 Q4 2011
Req Gate Failsafe GL
ALMR 5 ALMR 6 ALMR 7 ALMR 8 ALMR 9
Launch
Exit
Project DefinitionFinancials
Approvals
Testing
Go/no Go Criteria
Risk ManagementSecurity Checks
Planning
Requirements
OCM Plan
Lessons Learned
Next slide show the Agile style
5
ALMR Project Management in Agile modeALMR Product Roadmap and IT Project Gates - Agile Style
Q4 2010 Q1 2011 Q2 2011 Q3 2011 Q4 2011
Req Gate WIP Deploy
ALMR 5 ALMR 6 ALMR 7 ALMR 8 ALMR 9
Launch
Exit
Project DefinitionFinancials
Approvals
Testing
Go/no Go Criteria
Risk ManagementSecurity Checks
Planning
Requirements
OCM Plan
Lessons Learned
WIP WIP WIP Failsafe
Go Live
If needed, intermediate deployments
(WIP = Work In Progress)
Not all sections mandatory Next slide focuses
on 1 month to show where are IT commitments
6
ALMR Project Management in Agile modeAgile Software Development Timeline
Week 2 Week 3 Week 4Week 1
Sprint 1 Sprint 2
Remaining Effort
Remaining Effort
Sprint 1Backlog
Commit Check
Workshops &Development
Sprint 2Backlog
Burn-down Chart
Sprint Review& RetrospectivePlanning Meeting
Daily Scrum Meetings
ALMRProductBacklog
ALMRERs
… etc
… etc
ProductOwner
Dev Team
Burn-down Chart
ALMR Users
Deploymentevery ~6 sprints
Demos &Retrospective
Next slide shows how we however keep a long-term
view
7
ALMR Project Management in Agile modeALMR Release Plan
Q4 2010 Q1 2011 Q2 2011 Q3 2011 Q4 2011
Req Gate Deploy
ALMR 5 ALMR 6 ALMR 7 ALMR 8 ALMR 9
ALMRProductBacklog
ALMRERs
ALMR Users
WIP
ProductOwner
ALMR release 5 backlog
ALMR release 6 backlog
ALMR release 7 backlog
ALMR release 8 backlog
ALMR release 9 backlog
Next slide explains motivations for change to agile
approach
8
ALMR Project Management in Agile modeMotivations for ALMR to move towards Agile Software Development
What Does not Change We keep a quarterly ALMR Product Roadmap and Release Plan with
quarterly UATs, Go decisions, user training, cut-over, go live We still have management: planning, reporting, resource, financial,
risks, security, process, quality
Improvements More IT feedback (demos, restrospective) => better visibility and
predictability of ALMR releases => enhanced product ownership, better steering, can expect <1 month reactivity in case of a tactical change
Business provides earlier use cases, acceptance criteria => shorter UATs with less defects, users get what they expect
More IT commitment, every 2 weeks, based on better IT effort estimate More efficient IT testing, automated => less UAT defects More IT transparency internally, more trust Less time spent to prepare and review project gates, reduced x3
9
ALMR Project Management in Agile modeMeasuring Improvements
Quantitative Improvements List of measures:
Percentage of UAT readiness Amount of UAT defects Number of regressions brought by a new release Percentage of test coverage … to be completed
It is needed to collect retro-stats on previous ALMR projects, UATs Then, similar statistics will be gathered at each new ALMR release