That's why you get everything in writing. No change without detailed description of what you're doing and a written reply stating that yes, this is what they want. Otherwise you'll be in a constant refactoring treadmill.

[–] Ikiillpplalot@lemmy.world 6 points 1 year ago (1 children)

I'm working for a big company and our end-user has a lot of ideas of what features he wants. The only issue is that he changes his mind at the end of each sprint or in the middle of it. I am happy he has ideas for making the work more efficient because at the end of the day that's the major point of our work, but he can't lock down a deliverable. We have a business admin that's supposed to work out the actual work we need to do but this end user both won't take no for an answer for his idea and won't stick to his own script. I'd describe it less as a feature creep and more as a bunch of lateral moves and shifting goalposts that doesn't always amount to something better than the first interation yet it's still somehow a major blocker. Not only that but the big picture ideas get lost in his own plans and it becomes all about the small things he didnt articulate when I present the work.

It's getting pretty frustrating.

[–] blackstrat@lemmy.fwgx.uk 3 points 1 year ago

Solid change control. I've seen so many project come undone through lack of change control. You can only develop with stable requirements and changes to requirements should come with a cost. Without it it's basically offering unlimited development forever, often on fixed fee contracts too.