2 ms·
I've seen a lot of teams, and a lot of projects either fail or succeed. It boils down to three things: People are the most important, over-generalizations abou
by DanielBMarkham 17y ago
I've seen a lot of teams, and a lot of projects either fail or succeed.
It boils down to three things: People are the most important, over-generalizations about the development process is anathema, and always adapt.
The over-generalization part is especially rampant. Bloggers or authors want to make some sweeping statement about what software engineering is. Team members that worked on one successful project want to repeat that exact experience on another project. Project Managers who measured one thing on a good project become convinced that measuring that thing was part of what made the project successful.
Yes, there is engineering at work in software development. We load test, we plan scalability, we use set theory to model data and relationships. Debugging is about hypothesis formation and testing. There's all kinds of hard empirical science going on.
At the same time, the end result, the goal, is a nebulous thing that appears different ways in everybody's head. Large parts of this process give us the freedom to creatively construct things.
People who forget the engineering part fail projects due to bad design. People who forget the creative part fail projects due to poor user acceptance.
But highly-trained and motivated adaptive teams do just fine no matter what the environment.
The ultimate truth is: there is no ultimate truth.