Upload
vinod-sankaranarayanan
View
331
Download
3
Embed Size (px)
DESCRIPTION
Transferring ownership from one group or organisation to another is much more than transferring knowledge. This presentation aims to underscore some of the critical points in that process.
Citation preview
1 7 t h J u n e 2 0 1 4 OWNERSHIP TRANSFER
AGENDA
Introduction 6 dimensions on OT Knowledge Transfer Engineering Continuous Business Infrastructure Culture Process Methodology How much would it take?
WHY THIS TOPIC
High Risk
WHITE SPACE
Subverted due to people issues
Not well thought through
?
OWNERSHIP
Its more than knowledge
Its more than experience
It demands empowerment
It builds over time
Investment is key BRING HOME
THE CHILD
ORBITS OF INFLUENCE
Development Teams
Customers
Infrastructure
Product Teams
Business Teams
Enabling Functions
Human Resources
Finance
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
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
ENGINEERING
Not just the application –
but the means to change the application
Tools and processes
Versioning – version integrity
Disruption bringing in opportunity
CONTINUOUS BUSINESS
Three Angles
Releases Business Continuity
Business Value
Don’t let the project succeed and the product fail Changing pilots aflight
INFRASTRUCTURE
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
CULTURE
Pairing Technical Debt Not invented here
Of Process and Practices
PROCESS
Executions
Releases
Inceptions
Testing
Production Support
Project Costing
Team Role Changes
Governance
Feature vs Product Teams
New team will do things differently
INFRASTRUCTURE
Understand the real scope
METHODOLOGY
Create a framework
Plan
Execute
HOW DO YOU ASSESS EFFORT
Domain
Gap
Skill
Gap
Agile Fluency
Gap
W.W.W
v i n o d s a n @ t h o u g h t w o r k s . c o m 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
Used Icon
Slide-3
Slide-4
?
Used Icon
Slide-5
Slide-6
Used Icon
Slide-7
Slide-8
Used Icon
Slide-9
Slide-10
Used Icon
Slide-11
Slide-12
Used Icon
Slide-13
Slide-14
W.W.W