Introducing Scrum to an Organization
•
9 gostaram•5,379 visualizações
Introducing Scrum to an Organization. My presentation at Boost New Media in Wellington, Septe
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (20)
Semelhante a Introducing Scrum to an Organization
Semelhante a Introducing Scrum to an Organization (20)
Último
Último (20)
Introducing Scrum to an Organization
- 1. Introducing Agile to your organization Kane Mar & Boost New Media
- 2. About Me Kane Mar Scrum Trainer and Coach http://Scrumology.com Boost New Media http://Boost.co.nz info@Boost.co.nz
- 3. What is Scrum? • Scrum is a framework for iterative, incremental development. • Three roles: Product Owner, ScrumMaster and the Team. • Four meetings: Sprint Planning meeting, Daily Scrum, Sprint Review and Retrospective
- 5. Scrum is ‘Hard and Disruptive’ “Change is extremely difficult and fraught with conflict, and may take many years of sustained effort. Turnover of staff and management can be expected.
- 6. Scrum is Systemic Change “When the five shifts are undertaken simultaneously, as systemic change, the result is sustainable change that is markedly productive for the organization, more congenial to innovation, and more satisfying both for those doing the work and those for whom the work is done. • Ref: http://www.forbes.com/sites/stevedenning/ 2011/05/12/reinventing-management-requires-systemic- change/
- 7. So why would you want to do it? “An enterprise can use Scrum as a tool to become the best product development and management organization in its market. Scrum will highlight every deficiency and impediment that the enterprise has so the enterprise can fix them and change into such an organization.
- 8. Top Down • Scrum adoption is introduced and lead by Senior management ... • Who decide that they want software to be quicker, faster and cheaper • They decide the way to do this is by adopting Agile software development
- 9. Top Down • This is done without understanding the implications of Scrum, and without understanding how this changes: • How people work • How people collaborate • Impact to other business partners
- 10. Bottom Up • Scrum adoption is introduced and lead but the people who do the work ... • Who decide that they want better quality products, delivered at a sustainable pace • They decide the way to do this is by adopting Agile software development
- 11. Bottom Up • This is done without understanding the implications of Scrum, and without understanding how this changes: • Middle and Senior management perceptions • Change to the roles, responsibilities expected of management • Impact on other business partners
- 12. Kane’s secret formula 1. Top Down and Bottom Up both at the same time 2. Start small and plan for a growing number of Scrum projects 3. Target failed or at risk projects ... 4. With contained financial and political risk
- 13. Questions? • I have some questions for you! • How far up (or down) the organization is Scrum supported within your organization? • Does your management see problems as a learning opportunity? • Is your organization open to changing it’s culture?
- 14. Thank you! • Kane Mar Scrum Trainer and Coach http://Scrumology.com • Boost New Media http://Boost.co.nz