A good team can make any of these strategies work. A bad team will make a mockery out of them all. Most teams are neither good or bad, and stumble forward, or backwards, doing the motions
In some situations with some people yes.
It’s really hard to separate the project and team.
Usually, projects I have seen start with the best plans and methods, or at least vague good intentions, but later pretend they never met them. Like a cheap date.
There are some projects that naturally lend themselves to one approach or other, and they last longer following the original guidelines ; but if a project lives long enough these guidelines become the enemy.
I think the only projects that follow any set of guidelines for longer than a few years; they have a narrow purpose for being. Straightforward evolution or needs
A good team can make any of these strategies work. A bad team will make a mockery out of them all. Most teams are neither good or bad, and stumble forward, or backwards, doing the motions
Waterfall is much more expensive than any of the agile methods, even with good requirement gathering and management
In some situations with some people yes. It’s really hard to separate the project and team.
Usually, projects I have seen start with the best plans and methods, or at least vague good intentions, but later pretend they never met them. Like a cheap date.
There are some projects that naturally lend themselves to one approach or other, and they last longer following the original guidelines ; but if a project lives long enough these guidelines become the enemy.
I think the only projects that follow any set of guidelines for longer than a few years; they have a narrow purpose for being. Straightforward evolution or needs