Breaking Down Knowledge Silos

Teams have to work together, sharing knowledge, to create the best products.

Transcript

1. Breaking Down
 Knowledge Silos Within a Software Project Fun with Jake Trent
2. Blowing up
 Knowledge Silos Within a Software Project More! fun with Jake Trent
3. What is in the silo
4. Developer Knowledge Business requirements How the code works Design, paradigms The why Pitfalls
5. Why you want to blow stuff up
6. Customer Smiles Better product Meets requirement Best practices Stable Maintainable
7. Truck Factor Number of people that need to be run over before your project’s in trouble
8. Helpful Team Members Versatile No problems beyond your ability
9. Limit Liability No single point of failure
10. Maintenance Spread across teams
11. How the team can help
12. Pair Programming Devs talking to devs Pairs change more dev / mgmt
13. Pair Programming Owner-Visitor dev / mgmt
14. c c Stories Stories
15. c c Stories Stories
16. c c c c Stories Stories Stories Stories
17. Culture Developer-driven dev / mgmt
18. Introspective What don’t I know about? What’s high risk? What’s highest priority? What’s the hardest/easiest? Why? What has the least/most bugs? Why? What’s behind/ahead of schedule? Why? dev
19. Mental Picture Story owners More fluid partnerships dev / mgmt
20. Tasks Well-defined Small dev / mgmt
21. Fear …leads to suffering dev / mgmt
22. Ownership Total product dev
23. Now, go blow up some silos! (Knowledge silos only) jaketrent.com Attributions: Silos image (modified)- CC Attribution - http://www.flickr.com/photos/see-through-the-eye-of-g/4283298553/in/photostream/ Explosion image (modified) - Public domain - http://www.flickr.com/photos/ctbto/4926598654/ Menkaya font - free - http://www.dafont.com/menkaya.font YolksEmoticons font - free, non-commercial - http://www.dafont.com/yolks-emoticons.font