1. All Rights Reserved © Alcatel-Lucent 2010 ALMR Project Management in Agile mode Olivier PONY – October 2010

2. 2 ALMR Project Management in Agile mode Agenda 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. 3 ALMR Project Management in Agile mode ALMR Product Roadmap Q4 2010Q1 2011Q2 2011Q3 2011Q4 2011 Business view of detailed ALMR enhancement priorities is <3 months So we commit on release scope, check, and deploy every 3 months Commit Check Deploy In Waterfall Projects, 1 project = 1 commitment/check/deployment ALMR 5ALMR 6ALMR 7ALMR 8ALMR 9 In Agile Projects, 1 project = X commitments/checks/deployments Next slides show the IT gates ALMR 5ALMR 6ALMR 7ALMR 8ALMR 9

4. 4 ALMR Project Management in Agile mode ALMR Product Roadmap and IT Project Gates - Waterfall Style Q4 2010Q1 2011Q2 2011Q3 2011Q4 2011 Req GateFailsafeGL ALMR 5ALMR 6ALMR 7ALMR 8ALMR 9 Launch Exit Project Definition Financials Approvals Testing Go/no Go Criteria Risk Management Security Checks Planning Requirements OCM Plan Lessons Learned Next slide show the Agile style

5. 5 ALMR Project Management in Agile mode ALMR Product Roadmap and IT Project Gates - Agile Style Q4 2010Q1 2011Q2 2011Q3 2011Q4 2011 Req GateWIPDeploy ALMR 5ALMR 6ALMR 7ALMR 8ALMR 9 Launch Exit Project Definition Financials Approvals Testing Go/no Go Criteria Risk Management Security Checks Planning Requirements OCM Plan Lessons Learned 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. 6 ALMR Project Management in Agile mode Agile Software Development Timeline Week 2Week 3Week 4Week 1 Sprint 1Sprint 2 Remaining Effort Sprint 1 Backlog CommitCheck Workshops & Development Sprint 2 Backlog Burn-down Chart Sprint Review & Retrospective Planning Meeting Daily Scrum Meetings ALMR Product Backlog ALMR ERs … etc Product Owner Dev Team Burn-down Chart ALMR Users Deployment every ~6 sprints Demos & Retrospective Next slide shows how we however keep a long- term view

7. 7 ALMR Project Management in Agile mode ALMR Release Plan Q4 2010Q1 2011Q2 2011Q3 2011Q4 2011 Req GateDeploy ALMR 5ALMR 6ALMR 7ALMR 8ALMR 9 ALMR Product Backlog ALMR ERs ALMR Users WIP Product Owner 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. 8 ALMR Project Management in Agile mode Motivations 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. 9 ALMR Project Management in Agile mode Measuring 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