Return to Question

Heavy processes are common, unfortunately. Some people - especially management - religiously imagine that processes produce products. So they overdo the processes and forget that it's really a handful of hard-working, smart people who actually create the products. For upper management, it's frightening to even think that their business is in the hands of few geeks, and so the close their eyes from the reality and think of their dear "process" instead, which gives them the illusion of control.

 

That's why agile startups with a handful of good engineers can beat big, established corporations, whose workers spend 95 % of their energy on process and reporting.

Back It Up! means that your answers must be based on either:

 

• Something that happened to you personally
• Something you can back up with a reference

Heavy processes are common, unfortunately. Some people - especially management - religiously imagine that processes produce products. So they overdo the processes and forget that it's really a handful of hard-working, smart people who actually create the products. For upper management, it's frightening to even think that their business is in the hands of few geeks, and so the close their eyes from the reality and think of their dear "process" instead, which gives them the illusion of control.

That's why agile startups with a handful of good engineers can beat big, established corporations, whose workers spend 95 % of their energy on process and reporting.

Back It Up! means that your answers must be based on either:

• Something that happened to you personally
• Something you can back up with a reference

I realize that we're not Wikipedia. We're not even Skeptics.SE. We can afford to be a little more lax.

I realize that we're not Wikipedia. We're not even Skeptics.SE. We can afford to be a little more lax.

I refer to this answer from http://programmers.stackexchange.com/q/92508/3249 for which the question itself was actually the subject of a previous meta question. Quoted here in the unlikely event of changes:

I refer to this answer from Too much version control and bug tracking overhead per change? for which the question itself was actually the subject of a previous meta question. Quoted here in the unlikely event of changes: