The classic triangle: People, Process, Tools

Process is one of those holy grails or holy cows that are sacrosanct in software development not open to questioning. A question posed is enough to label a person heretic, rebel, bad influence or any such thing.

There are three fundamental parts to the execution of a project. The classic trio of people, process and tools/technology. Any failure can be attributed to one of them and fixed appropriately ensuring it doesn't repeat itself.

The most common response to a broken process, causing issues downstream, is an additional process introduced to check it. Seldom have I seen people looking at the real cause before applying the fix on the process part. Isn't that the part project managers love most.

The right way out would be to first analyze why the process was broken, adding a process to avoid breakage of another is a self serving cycle with no gain for anyone but the process itself.

The people part in this triangle can offset the other two, but not vice-versa. Hence, it is extremely important to identify people failures and then treat them as such. A process cannot offset for a person not doing his job right.

In most of the cases, adding processes to offset for incompetent people(team) ends up in a bureaucratic team. And an over-process environment _slows_ everything down giving an impression of number of mistakes going down. Processes become tools for assigning blames in case of failures rather than being tools to stop them.

If you ever face issues in this trio, fix the people issues first and rest will fall in place in time.

Comments (0)