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...
Próximos SlideShares
Carregando em…5
×

Breaking Down Knowledge Silos

2.541 visualizações

Publicada em

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.

Publicada em: Tecnologia
0 comentários
0 gostaram
Estatísticas
Notas
  • Seja o primeiro a comentar

  • Seja a primeira pessoa a gostar disto

Sem downloads
Visualizações
Visualizações totais
2.541
No SlideShare
0
A partir de incorporações
0
Número de incorporações
121
Ações
Compartilhamentos
0
Downloads
11
Comentários
0
Gostaram
0
Incorporações 0
Nenhuma incorporação

Nenhuma nota no slide
  • Because silos can also bemissle silos, producing this shock and awe
  • - Silo: Barriers that have been created (by organization layout, role definition, project management, or indiscriminately) that keep something separate- Developer knowledge
  • Every developer has a unique experience with the software they work onMuch of that can be useful to other developers, present and future
  • In the end, highest priority is delivery of quality software that meets the needs of the customerThis can be done with very stringent silos, but we want to raise the odds of meeting that goal by taking them down, allowing developers to gain bits of the knowledge that others, possibly more familiar with the app, have already gained
  • This could be you or someone else; Bad if it’s you, obviously; Bad if it’s someone else, because now you have their work to do How do people get run over: horrible accidents, funding changes, new projects, new jobs, and more horrible accidents
  • Good for you and good for the project: Decrease the chances that you’ll be the one getting the late night phone call: - The code has had more eyes all over it, it’s hopefully more stable - The call could go to anyone because anyone should be able to fix it
  • Like manure at the farm Likelihood that the team that will eventually maintain the product will receive one or some of the original developers Developers have great knowledge of many systems (or in the case of MMS, the universe of msny mgmt as a whole).
  • - Mention of ping pong pair prg’ing? owner rotation ideas: day, half day- Present other ideas for pair programming, maybe general principles: New pair every iteration, owners (knowledge transfer’ers) have to be someone who has worked on it at any time during the project – most recent makes the most sense
  • Each dev owns storiesDedicates some time to helping the other pair member on their stories
  • And gets help in returnEach teach and learn
  • A mess if we try to map it out
  • More organicJust happens
  • - Developer-driven
  • - The idea that I have in my head is where developers feel responsible for the stories they have and for the product as a whole, and they realize that total health will be bettered long-term as the tribal knowledge of the product is spread around.
  • - Finishable in a day- Well-defined
  • Dev/mgmt – willing to tackle / willing to assign anything to anybody Strikes fear: Mevl/moderation/CPF/Script*/Letters/Transfer Override/SeniorAssignmentMeetingBean/FormProcessingServlet
  • - Feel pride for your work – which is now everything
  • Consider how you can open knowledge silos you’ve been privy toConsider what silos you don’t but should probably know something aboutConsider how you’ll influence the organization to form fewer silos
  • 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 />

    ×