Your SlideShare is downloading. ×
The Knowledge Ticket - Securing Intellectual Assets
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

The Knowledge Ticket - Securing Intellectual Assets

152
views

Published on

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
152
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • 1 min
  • 2 min
  • 2 min
  • 1 min
  • 1 min
  • 3 min
  • 1 min
  • 3 min
  • Transcript

    • 1. The Knowledge Ticket Securing Intellectual Assets Colm Byrne – Knowledge Architect Email: colmxbyrne@gmail.comJanauary 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 Writer2
    • 3. 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
    • 4. 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
    • 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 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
    • 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 works7
    • 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 KT8
    • 9. Jira & Confluence  Create the ticket in Jira  Put the KT in Jira  Put KT links in Confluence stories9
    • 10. 10
    • 11. Thank you Colm Byrne – Knowledge Architect Link to me on Linked-in colmxbyrne@gmail.comJanuary 2013