80 likes | 198 Vues
This document outlines the resourcing strategy for Q4 2007 through Q2 2008, focusing on succession planning, promotion schedules, and lessons learned for effective future implementations. Key assumptions regarding current R4 resourcing levels and testing timelines for SPU and regression tests are discussed. The document also presents options for managing unassigned time in January and beyond, as well as necessary staffing adjustments. Insights on future improvements and the roadmap for Retalix are included, emphasizing engagement and risk management.
E N D
Contents • Q4 2007 / Q1 and Q2 2008 Resourcing • Succession Planning / Promotions Schedule • Lessons Learned / Future Improvements • Retalix Roadmap
Q4 2007 / Q1 and Q2 2008 Resourcing - Assumptions • Current planned level of R4 resourcing continues to year-end, mid-Nov to end-Dec will be fixing issues/ad hoc test requests/regression testing • Support Pack Upgrade (SPU) will require equivalent to a single ITC cycle per live country • UK / AU / NZ / US • No GSS Product Test / V+P required • Overall resourcing for SPU testing will therefore be as per current test tracks – NZ regression and US regression will require same level of resourcing as current ITC progression tracks • ANZ regression for SPU conducted by BDC • SPU testing timeframes are 21/1/8 until end Feb 08 • Test Prep for NL/PL cannot start until May 08 • NL/PL test team size will be equivalent to current overall R4 test team size • NL/PL progression testing is equivalent to ANZ progression testing • Regression testing for US/UK/ANZ can be scoped down to provide resource capacity for NL/PL PT
Q4 2007 / Q1 and Q2 2008 Resourcing - Resource Profile December is currently contingency rather than hard planned May is Test Prep for NL/PL Ramp-up back to R4 levels for NL/PL Execute Year End BDC Headcount = 16 • IBM Unassigned Time • Three weeks in January, pre SPU • March / April – post SPU, pre NL/PL • IBM January time = 21FTE x 3 weeks = 21 x 5days/week x 3 weeks = 315 mandays (unavoidable – retention required for SPU) • IBM March/April time = 21FTE x 2 months = 21 x 22days/month x 2 = 924 mandays • BDC Unassigned Time • Two weeks in January – post patch test, pre SPU • March / April – post SPU, pre NL/PL • BDC January time = 16FTE x 2 weeks = 16 x 5days/week x 2 weeks = 160 mandays (unavoidable – retention required for SPU) • BDC March/April time = 16FTE x 2 months = 16 x 22days/month x 2 = 704 mandays
Q4 2007 / Q1 and Q2 2008 Resourcing - Options • Option One – downsize to skeleton crew for March/April • What’s the minimum staff that we can reduce to, and still ramp-up from? • Key individuals / skillsets required to be retained? • Option Two – utilize capacity in March / April to do maintenance release activity • UK to Release 4? • AU to Release 4? • Patch release for AU/UK/US? • Option 3 – SPU is extended to be ECC6 upgrade • Reduces gap to be only April as this scope increase adds one month to SPU test timeline • Gap therefore becomes 352 mandays (BDC), 462 mandays (IBM) • Utilise reduced capacity to do reduced version of Option Two
Succession Planning / Promotions Schedule • UK resources promoted in 2007 where new rates apply from Jan 1st 2008 • Chris Griffiths, others? • Succession planning for Chris • Anticipating he won’t want to remain in testing forever(!): • who’s heir apparent? Zoe? • capability gap / risk associated with successor? • Utilising experience on program in another role somewhere on program? • Confirming time in role from this point for key BDC resources • E.g. Peter Hrnciar • Previous action to publish forecast promotions during 2008 • Progress update on early rolloffs • Redeployment of resource currently in notification window to other billable work
Lessons Learned / Future Improvements • UK resources promoted in 2007 where new rates apply from Jan 1st 2008 • Chris Griffiths, others? • Succession planning for Chris • Anticipating he won’t want to remain in testing forever(!): • who’s heir apparent? Zoe? • capability gap / risk associated with successor? • Utilising experience on program in another role somewhere on program? • Confirming time in role from this point for key BDC resources • E.g. Peter Hrnciar • Previous action to publish forecast promotions during 2008
Retalix Roadmap • Or…..defining the end-state for Retalix test schedule • aspiration to remove a cycle of product test etc. • How do we move this forward?! • Ownership? • Retalix engagement? • Risk / concerns • If we ‘blackbox’ it, do we risk getting longer elapsed time quotes for delivery from Retalix?