The metaphor I use is Archery. Getting a project to deliver is like hitting a moving target. Sometimes better ways of getting things done come along in the middle of a project. Things change (priorities, new technology), stuff happens - expect to live with a bit of ambiguity whilst you move forward.
Typically as soon as you set the goal, you find the goal posts move a little further out or your asked to cover a wider remit.
Then of course things happen... priorities changes. Something was overlooked.... and of course then there are disruptions... new technologies, new ideas.
So, scope creep happens like trying to hit the bullseye on a target 100 meters distant whilst there is a continual erratic earthquake happening.
Lets turn to how to make it happen without trying:
Put your users and technical teams in silos... Put the process team in another. Set your project up with individual workstream focused on separate areas. Never discuss the nitty gritty. Rush through the requirements..
Have no one think about the number of key clicks, mouse movement or bandwidth required to produce to execute individual steps. Stop all the What if X happens conversations.
Keep the project picking up momentum going by never double checking that you've covered the essential requirements. Never look at the interdependencies.
Keep the guy who's been making everything run completely isolated and off the project.
Result: The budget gets spent. You'll wind up with Change Requests to cover all the Must-DO requirements... Lots of work needs to happen to make it more usable, faster, etc.
Whilst you might hit a bit wide of your original target, you might have missed seeing that you should have changed your aim to hit a different target.
Hope this helps in some small way.
All the best,
Alison
posted 7 days ago
No comments:
Post a Comment