Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Breaking DownKnowledge Silos<br />Within a Software Project<br />Fun with Jake Trent<br />
Blowing upKnowledge Silos<br />Within a Software Project<br />More! fun with Jake Trent<br />
What is in the silo<br />
Developer Knowledge<br />Business requirements<br />How the code works<br />Design, paradigms<br />The why<br />Pitfalls<b...
Why you want to blow stuff up<br />
Customer Smiles<br />Better product<br />   Meets requirement<br />   Best practices<br />       Stable<br />       Mainta...
Truck Factor<br />Number of people that need to be run over before your project’s in trouble<br />
Helpful Team Members<br />Versatile<br />No problems beyond your ability<br />
Limit Liability<br />No single point of failure<br />
Maintenance<br />Spread across teams<br />
How the team can help<br />
dev / mgmt<br />Pair Programming<br />Devs talking to devs<br />Pairs change more<br />
dev / mgmt<br />Pair Programming<br />Owner-Visitor<br />
c<br />Stories<br />c<br />Stories<br />
c<br />Stories<br />c<br />Stories<br />
c<br />c<br />Stories<br />Stories<br />c<br />c<br />Stories<br />Stories<br />
dev / mgmt<br />Culture<br />Developer-driven<br />
dev<br />Introspective<br />What don’t I know about?<br />What’s high risk?<br />What’s highest priority?<br />What’s the ...
dev / mgmt<br />Mental Picture<br />Story owners<br />More fluid partnerships<br />
dev / mgmt<br />Tasks<br />Well-defined<br />Small<br />
dev / mgmt<br />Fear<br />…leads to suffering<br />
dev<br />Ownership<br />Total product<br />
Now, go blow up some silos!<br />(Knowledge silos only)<br />rockycode.com/blog/tech/project-management/<br />Attributions...
Upcoming SlideShare
Loading in …5
×
Upcoming SlideShare
The silo effect the peril of expertise and the promise of breaking down barriers pdf
Next
Download to read offline and view in fullscreen.

0

Share

Download to read offline

Breaking Down Knowledge Silos

Download to read offline

Barriers are created all the time on software projects (by organization layout, role definition, project management, or indiscriminately) that keep developer knowledge separate. We can create better teams and products for our organizations if we can blow up these silos.

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all
  • Be the first to like this

Breaking Down Knowledge Silos

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

Barriers are created all the time on software projects (by organization layout, role definition, project management, or indiscriminately) that keep developer knowledge separate. We can create better teams and products for our organizations if we can blow up these silos.

Views

Total views

2,845

On Slideshare

0

From embeds

0

Number of embeds

121

Actions

Downloads

11

Shares

0

Comments

0

Likes

0

×