• Save
The Knowledge Ticket - Securing Intellectual Assets
Upcoming SlideShare
Loading in...5
×
 

The Knowledge Ticket - Securing Intellectual Assets

on

  • 319 views

 

Statistics

Views

Total Views
319
Views on SlideShare
314
Embed Views
5

Actions

Likes
0
Downloads
0
Comments
0

1 Embed 5

http://www.linkedin.com 5

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • 1 min
  • 2 min
  • 2 min
  • 1 min
  • 1 min
  • 3 min
  • 1 min
  • 3 min

The Knowledge Ticket - Securing Intellectual Assets The Knowledge Ticket - Securing Intellectual Assets Presentation Transcript

  • The Knowledge Ticket Securing Intellectual Assets Colm Byrne – Knowledge Architect Email: colmxbyrne@gmail.comJanauary 2013
  • 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 Writer2
  • Knowledge Ticket  What problem is it trying to solve?  Why youd want to use it.  How to implement it in other parts of the business3
  • The Problem & Risk  If you dont know it, you dont own it. • 3rd parties build high value products. We pay for it, they know how it works. • You dont speak Ukranian -youre tied to 3rd party. • Agile manifesto is misinterpreted --- badly  Knowledge is Cordoned off • 5 hats problem • Top producers producing nothing.  Scaling is hampered/Errors reproduced4
  • 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
  • The Problem  If you dont know it, you dont own it. Big Risk. • 3rd parties build high value products. We pay for it, they know how it works. • You dont speak Ukranian -youre tied to them. • Agile manifesto is misinterpreted --- badly  Knowledge is Cordoned off • 5 hats problem • Top producers producing nothing.  Scaling is hampered/Errors reproduced6
  • 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 works7
  • 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 KT8
  • Jira & Confluence  Create the ticket in Jira  Put the KT in Jira  Put KT links in Confluence stories9
  • 10
  • Thank you Colm Byrne – Knowledge Architect Link to me on Linked-in colmxbyrne@gmail.comJanuary 2013