Breaking DownKnowledge SilosWithin a Software Project

Fun with Jake Trent

Blowing upKnowledge SilosWithin a Software Project

More! fun with Jake Trent

What is in the silo

Developer Knowledge

Business requirementsHow the code worksDesign, paradigmsThe whyPitfalls

Why you want to blow stuff up

Customer Smiles

Better product Meets requirement Best practices Stable Maintainable

Truck Factor

Number of people that need to be run over before your project’s in trouble

Helpful Team Members

VersatileNo problems beyond your ability

Limit Liability

No single point of failure

Maintenance

Spread across teams

How the team can help

Pair Programming

Devs talking to devsPairs change more

dev / mgmt

Pair Programming

Owner-Visitor

dev / mgmt

c

c

Stories

Stories

c

c

Stories

Stories

c

c

c

c

Stories Stories

StoriesStories

Culture

Developer-driven

dev / mgmt

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

Mental Picture

Story ownersMore fluid partnerships

dev / mgmt

Tasks

Well-definedSmall

dev / mgmt

Fear

…leads to suffering

dev / mgmt

Ownership

Total product

dev

Now, go blow up some silos!

(Knowledge silos only)

rockycode.com/blog/tech/project-management/

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.fontYolksEmoticons font - free, non-commercial - http://www.dafont.com/yolks-emoticons.font