Ownership Transfer of an IT Program


Published on

Published in: Technology, Business
1 Comment
  • very interesting presentation
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Ownership Transfer of an IT Program

  1. 1. 1 7 t h J u n e 2 0 1 4 OWNERSHIP TRANSFER
  2. 2. AGENDA Introduction 6 dimensions on OT Knowledge Transfer Engineering Continuous Business Infrastructure Culture Process Methodology How much would it take?
  3. 3. WHY THIS TOPIC High Risk WHITE SPACE Subverted due to people issues Not well thought through ?
  4. 4.     OWNERSHIP Its more than knowledge Its more than experience It demands empowerment It builds over time Investment is key BRING HOME THE CHILD
  5. 5. ORBITS OF INFLUENCE Development Teams Customers Infrastructure Product Teams Business Teams Enabling Functions Human Resources Finance
  6. 6. BEING AGILE Remote Pairing Code Comfort The end user Plan evolution We have come to value: Individuals interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. Kent Beck, Muke Beedle, Arie van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler, James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick, Robert C. Martin, Steve Mellor, Ken Schwaber, Jeff Sutherland, Dave Thomas ©2001, the above authors
  7. 7. KNOWLEDGE TRANSFER Remote Pairing How do you know it’s working? Giving away is equally difficult Ownership Transfer over releases What happens during the transfer? What is ‘learnt’ over what is ‘taught’ What NOT to transfer
  8. 8.     ENGINEERING Not just the application – but the means to change the application Tools and processes Versioning – version integrity Disruption bringing in opportunity
  9. 9.     CONTINUOUS BUSINESS Three Angles Releases Business Continuity Business Value Don’t let the project succeed and the product fail Changing pilots aflight
  10. 10. INFRASTRUCTURE The cloud Keep machines on both sides running Manual cloning – vs automation Not just production, but also development, testing, NFT environments IS teams being part of the plan
  11. 11.     CULTURE Pairing Technical Debt Not invented here Of Process and Practices
  12. 12.     PROCESS Executions Releases Inceptions Testing Production Support Project Costing Team Role Changes Governance Feature vs Product Teams New team will do things differently
  13. 13. Understand the real scope METHODOLOGY Create a framework Plan Execute
  14. 14. HOW DO YOU ASSESS EFFORT Domain Gap Skill Gap Agile Fluency Gap W.W.W
  15. 15. vino d san @tho u g htworks.com THANK YOU r e s t l e s s t e m p e s t . b l o g s p o t . c o m
  16. 16. Used Icon Slide-3 Slide-4 ?
  17. 17. Used Icon Slide-5 Slide-6
  18. 18. Used Icon Slide-7 Slide-8
  19. 19. Used Icon Slide-9 Slide-10
  20. 20. Used Icon Slide-11 Slide-12
  21. 21. Used Icon Slide-13 Slide-14 W.W.W