You can define project management in many ways. I’d say the definition will differ depending on the project you actually run, its size, the customer on the far end etc. And definitely there are projects which could be at least partially defined as getting ass-covers.
It will happen usually when (either one):
• Client constantly changes the scope of the project.
• There is significant delay which can’t be clearly ascribed to one of sides.
• Project teams don’t like each other.
• Choosing a vendor was a political decision.
Sure, that mode of running a project isn’t a favorite one for most people, but it’s rarely you who is decision-maker. Usually you just follow whatever rules apply. If you’re unfortunate to work in ass-covering mode you better go and get some of those.
Otherwise you’ll end adding a number of features which weren’t planned. Or reconfiguring the environment multiple times instead of doing it once. Or being blamed for issues you weren’t responsible for. Or paying forfeits which aren’t quite fair. Nothing pleasant here.
On the other hand when you have to run a project that way, which I really recommend to avoid whenever possible, it can be quite a joy to have your ass-cover when you really need one.
Subscribe RSS feed
Follow on Twitter
Subscribe by email
