Product over Project
A project is a way to organize work. However, in many organizations projects has become an end in itself….
What’s the problem with projects then? There are mainly two reasons:
- The division between project and maintenance leads to “handover” and loss of knowledge
The best way to maintain a software product is to have the same people maintaining it, as those who created it. So why not start maintaining from day one of production creation?
- Managers tend to “manage” resources and assign people to projects based on specialization
“Respect for people” is an important principle of lean. When you manage people like a “resource” there’s little room for respect of the individual.
Why does this matter to architects and the way they engage within an organization?