1. The Knowledge Ticket
Securing Intellectual Assets
Colm Byrne – Knowledge Architect
Email: colmxbyrne@gmail.com
Janauary 2013

2. What I do
 Train the Brains
• Implement Jira and Confluence & Get adoption
• Onboards teams into specific Agile practices
• Jira & Confluence training and best practices
 Protect intellectual assets - Own what you build
• Set up process with third party contractors to retain know-how
• Retrieve knowledge after the fact/Reverse Engineer
• Implement internal doc policies
 Technical Writer
2

3. Knowledge Ticket
 What problem is it trying to solve?
 Why you'd want to use it.
 How to implement it in other parts of the business
3

4. The Problem & Risk
 If you don't know it, you don't own it.
• 3rd parties build high value products. We pay for it, they know
how it works.
• You don't speak Ukranian -you're tied to 3rd party.
• Agile manifesto is misinterpreted --- badly
 Knowledge is Cordoned off
• 5 hats problem
• Top producers producing nothing.
 Scaling is hampered/Errors reproduced
4

5. The Agile Lie – “Self-documenting”
 Systems today are bigger than ever before
 “Complexity increases exponentially with size” - Juval
Lowey
 Systems need to be interconnected
 Who really knows how your system works.
5

6. The Problem
 If you don't know it, you don't own it. Big Risk.
• 3rd parties build high value products. We pay for it, they know
how it works.
• You don't speak Ukranian -you're tied to them.
• Agile manifesto is misinterpreted --- badly
 Knowledge is Cordoned off
• 5 hats problem
• Top producers producing nothing.
 Scaling is hampered/Errors reproduced
6

7. The Opporunity
 Essential knowledge always available
• Only the information needed is maintained
• Easily accessible through Jira and Confluence
• Does not explain code – explains know-how
 Help implement best practices
 Scale quickly by adding new employees.
• Knowledge base full of 'this is how it works'
7

8. The Knowledge Ticket
 Jira task tied to each user story in planning
• Usually complex stories
• Dev and Product owner decide if KT needed
 3 Parts: Rules/Calculations/Context
 Dev explains in The Demo how his piece works using the
KT
8

9. Jira & Confluence
 Create the ticket in Jira
 Put the KT in Jira
 Put KT links in Confluence stories
9

10. 10

11. Thank you
Colm Byrne – Knowledge Architect
Link to me on Linked-in
colmxbyrne@gmail.com
January 2013