Client with Unrealistic Demands

[Gould The Swimmer]

So I'm working on a system that has had many contractors' dibs all over it.

I've been asked to develop a large piece of UI work to make a lot of existing features configurable. Unfortunately, much of the code isn't compatible with their envisaged design and to progress on my task I am constantly having to refactor / rewrite other components.

None of this was accounted for when the story points for
the task were allocated but the timescale remains tge same.

Turns out that the client I'm working for is getting the work subbed out to them by another outfit that has the relationship with the actual end client.

Consequently the money is rubbish too.

Tempted to explain to them how much extra work I've had to put in bit I get the feeling they have no control over the deadlines so I'm going to have to walk.

Not a decision I take lightly in these times but what they're asking is, in my view, totally unachievable.

A but of a rant I guess but I'm sure we've all been there.

[northernladuk]

Have an internet hug

[GhostofTarbera]

Just up the story points - sorted

Don’t work for free


Sent from my iPhone using Contractor UK Forum

[Fraidycat]

Tempted to explain to them how much extra work I've had to put in bit I get the feeling they have no control over the deadlines so I'm going to have to walk.
Not a decision I take lightly in these times but what they're asking is, in my view, totally unachievable.

High pressure work for low pay.
Sweat shop conditions basically.
Only worth it if you are picking up some good marketable skills that you don't already have.
If you are going to quit anyway you could ask for a big rate bump, they might agree.

The biggest rate increase i ever got in one go was: 36%, £55 an hour to £75.
I have known other contractors who got a lot more when they threatened to quit. But those were during the boom times.
Depends how desperate they are.

[Scruff]

Death March Projects need to be assessed, to determine if the target is unachievable. After discussing it with the end client, they need to accept the risk, or you need to mitigate it by termination.

[eek]

Death March Projects need to be assessed, to determine if the target is unachievable. After discussing it with the end client, they need to accept the risk, or you need to mitigate it by termination.

Given the OP's second paragraph the target isn't achievable.

Once you are refactoring recently delivered code you are in a no win situation.

[Lance]

Who’s going to tell the emperor he is naked???

A professional contractor should..

[Paralytic]

None of this was accounted for when the story points for
the task were allocated but the timescale remains tge same..

Two issues there

1) Story points should not be "allocated" - were you not part of the planning ceremonies?
2) Where is this "timescale" coming from? Sounds like your client/Project Manager/Scrum Master is doing some story points to time calculation, which is always a bad sign.

Your client is one of many who think they can get the benefits of "doing agile" by not fully capturing requirements up front, but then expecting the project to be run as waterfall within a predefined fixed time/scope/plan.

You can either change your client, or you can change your client.

[Paralytic]

Just up the story points - sorted

Don’t work for free

I'd suggest not upping the story points, but ensure that team accurately calculate their velocity before accepting stories into subsequent sprints.

The client will soon get the idea when they're told the team can only accept 1 or 2 stories in the next sprint.

[BlasterBates]

Why not just tell them at the next meeting or even ring up the PM and let him know now, maybe they'll replan i.e. give up on the configurable UI.

Worth a try.

Either they'll believe you and replan or they won't and your project ends now.