This term simply stands as a reminder for, how many people need to get hit by a bus to leave you without anybody being familiar with one of your mission-critical applications. If the number equals one, you might re-consider your strategy…
Don’t forget, there are also more common ways for developers to go somewhere else (better offer, kids, sabbatical etc).
VersionOne have published their 3rd Annual ‘State of Agile Development’ survey: Results are available on this page or as pdf.
Overview of topics covered:
- State of agile methods.
- Mix of participanting companies.
- Reasons for adopting agile methods.
- Concerns against it.
- Practices applied.
- Reasons for failures.
- Where agile creates value.
- What tools are used.
In an article from 1968 with the title “How Do Committees Invent?”, the author Melvin Conway makes the following point, which later became established as “Conway’s Law”:
“Any organization that designs a system will inevitably produce a design whose structure is a copy of the organization’s communication structure.” (Original Article) (Conway’s Law on Wikipedia)
Conway suggested an approach containing the following steps:
- Define your business mission.
- Learn the business processes from the business owners.
- Re-engineer these business processes to match their mission.
- Structure your IT to support no 3.
His concluding points:
- Design according to the need for communication.
- Your design will never be perfect because things change and require your processes to adapt accordingly.
- Reward people who keep the organization lean an flexible.
- Adding more manpower does NOT equal adding productivity into a design effort.