A method of ientifying and developing senior and/or junior engineers and managers through the completion of compressed projects using the SCRUM methodology

1. SCRUM (Mid Level Engineers Talent Awareness & Development Through Project Work)

2. Scrum Pilot Overview 1. Sponsoring Director (‘Product Owner’) selects a current business need for a 30 day project 2. Sponsoring Director and HR discuss project and SCRUM process and adapt as necessary 6. Project commences with ScrumMaster being identified and first ‘Sprint’ activity undertaken 5. Product Owner describes the project task and deliverables expected 8. Implement 30 Day project. 7. SCRUM process proceeds with involvement of Product Owner and observation/coaching by HR 10. Enhanced development and new opportunities discussed by HR with Head of Discipline 4. Principles of SCRUM presented to the SCRUM team members by HR 3. Eight HIPO’s identified and invited to partake 9. HR undertakes personal lessons learnt with each team member and HIPO identification with Sponsoring Director Throughout the project HR and the Sponsoring Director meet to review observed behaviours against the standard leadership competency framework

3. The SCRUM Process ‘ Product Backlog’ A prioritized and business value list of what will be delivered and in order of importance. Those with a higher ROI are given greater priority ‘ Sprint backlog’ The list of work that the team must address during the next ‘sprint’. ‘ Sprint’ Short bursts of work of typically between 4-16 hours. Tasks never assigned; Team members self select a task from the list to undertake, promoting self buy-in and commitment ‘ Shippable Product’ The end ‘product’ delivered with a higher degree of certainty of ‘fit for purpose’ and ROI, due to the iterative method of project delivery 30 days 24 Hours Scrum Process

5. Scrum Breakdown Impediments Spring Review The Team Sprint Backlog Daily Scrum ScrumMaster Product Backlog Sprint Planning Product Owner Lists Meetings Roles

8. SCRUM A 30 Day Project Methodology Roy Mark 22/09/2010

12. The SCRUM Process ‘ Product Backlog’ A prioritized and business value list of what will be delivered and in order of importance. Those with a higher ROI are given greater priority ‘ Sprint backlog’ The list of work that the team must address during the next ‘sprint’. ‘ Sprint’ Short bursts of work of typically between 4-16 hours. Tasks never assigned; Team members self select a task from the list to undertake, promoting self buy-in and commitment ‘ Shippable Product’ The end ‘product’ delivered with a higher degree of certainty of ‘fit for purpose’ and ROI, due to the iterative method of project delivery 30 days 24 Hours Scrum Process

13. Scrum Breakdown Impediments Spring Review The Team Sprint Backlog Daily Scrum ScrumMaster Product Backlog Sprint Planning Product Owner Lists Meetings Roles

14. Three Roles In this methodology whilst others are interested in the outcome of the project their jobs and reputations are not ‘on the line’ and so there may be a degree of indifference from them or lack of responsiveness. Consequently whilst such stakeholders needs, desires, ideas and influences are taken into account, they are not allowed to get in the way of the actual Scrum project, eg, by requesting reviews; sign-offs; socialisation; etc. True Team ‘Stakeholders’ (its their jobs on the line) Removes Impediments Budget Responsibility Cross Functional Enforces the Scrum Features Self Organising Team Servant Product Vision The Team ScrumMaster Product Owner

15. Three Meetings “ What impediments stand in your way?” Team commits to Product Owner Must represent potentially shippable product (“looking onto” and “arranging a meeting” are not a product) “ What will you do today?” Team analyzes tasks involved and creates Sprint Backlog Presented by Team to Product Owner at end of a Sprint “ What did you get done yesterday?” Product Owner and Team review Product Backlog Sprint Review Daily Scrum Sprint Planning

28. Process – Measuring ‘Burndown’ Progress

33. Scaling Through the Scrum of Scrums

34. Scrum of Scrums of Scrums