don't know it? you don't own it - securing intellectual assets for product managers
TRANSCRIPT
You don't know it?You don't own it.
Securing Intellectual Assets with the Knowledge Ticket
January 2013 AUG London
Colm Byrne – Product Manager
Email: [email protected]
Product Management Lectures
2
Knowledge Ticket in Product ManagementThe ownership imperative in Product Management
If you are building a product and outsourcing development - then you'll need to know how it was developed - architecturally, internally, and every algorithm used to the point where it could be taken back internally at any point.
The knowledge ticket helps address this issue for product managers. It allows the product development to be outsourced while the knowledge is retained internally.
Why you should use it.
How to implement it in other parts of the business
3
The Problem & RiskProduct Managers own the delivery but not the process
Outsourcing: If your devs don't know it, you don't own it. • 3rd parties build high value products. You pay for it, they know
how it works.
• Black box delivery.
• 'Self-documenting code' fallacy.
Insourcing: Knowledge is Cordoned off• 5 hats problem
• Top producers producing nothing.
Scaling is hampered/Errors reproduced
4
The Agile Fallacy – “Self-documenting”
Products today have larger code bases than ever. 2.5 million lines of code on average.
“Complexity increases exponentially with size” - Juval Lowey
Systems interconnect.
Who really knows how your product works. Algorithms, formulas, patterns.
5
The Opportunity
Make Essential knowledge always available• Only the information needed is maintained
• Easily accessible through Workflow tools. E.g. Wikis, Jira and Confluence
• Does not explain code – explains know-how
Outsource while securing your intellectual assets– Put all tools and code in the cloud; Git, Maven, Crucible, Fisheye
Scale quickly by providing essential knowledge to noobs. • Knowledge base shows 'this is how it works'
6
The Knowledge TicketAdd a 'Knowledge Ticket' to each major story
Jira task tied to each user story in planning• Complex stories with calculations, flow. E.g. a Credit check, risk
evaluation
• Dev and Product owner decide if KT needed at planning and retro.
3 Parts to the ticket: Rules/Calculations/Context
Dev explains in The Demo how his piece works using the KT
7
Workflow: Jira & Confluence
Create the ticket in Jira
Put the KT in Jira
Put KT links in Confluence stories
8
