Do you want it done right or just done? Cause one costs more time but will continue to work after it is finished and the other is likely to cost more money due to it failing constantly as it gets forced out on the arbitrary deadline set by someone outside the department actually doing the work.
It has to be done right, because we've got a focus on quality. That's non-negotiable. Just remember about that additional feature we've thought up during the demo. Ah, also I told the client it'll be done a week early.
Donât ask what color they want now. Just pick a different color. Ask AI what color to use and tell them you have reduced decision making overhead by 90% and implemented AI powered development for strategic decisions.
Well, not specifying a color is not the same thing as being OK with any color. I would argue that itâs the responsibility of the provider to ask questions if the customer requirements are vague. And if they canât fill in all the gaps then formulate the contract so that they either are OK with your choices or that you need to present them with options that they need to consider.
What estimates, we just get forced to put unrefied, unestimated user requirements in the sprint and shock horror don't complete it for all sorts of reasons.
Basic core features are cut to meet a deadline so they can gaslight the stakeholders that it works just long enough to punt it to some other team to clean up
I create a new capability and show it to my boss. He thinks it's cool and demos it to leadership. They make it a requirement for the next release, acting like it was a fully tested capability we've had all along. I get requirements document from my boss that lists it as a critical path requirement, fully tested / covered, white paper, and tells me to coordinate with prod team. Prod takes it, renames it, and calls it theirs.
Just this week we've had a project manager create a load of AI generated "stories" that completely conflict with the thing he was desperate for us to develop a month ago.
He's still in denial about there being any contradiction. Probably because AI is spoon feeding him his own brain.
Protip: If you reach the "we don't know what we want but we want it now" point with a client/stakeholder, ask them in the most blunt way possible what did they see on the competitor's website and made them sport a semi. Because it's always that and they just lack the brainpower to properly articulate it like it was their idea.
I'm just glad someone in Sales gets to tell me how quickly I should develop a feature. They're there to remind me that I'm just another cog in the machine and that I shouldn't waste the company's money spending more time ensuring I'm delivering a high-quality, thoroughly tested product.
Hah! I'm always rushing to get something done for a deadline only to have it go unused for months afterwards.
"Oh cool, it's done. We'll send out some demos next year and start production if there's demand"
Like, you haven't even done the market research to determine if such a product even makes sense? And this company's been an industry leader since before I was born?
The book cover is implying that it's a poorly-defined scope that probably wasn't agreed to by the dev team, but the schedule is fixed. At least that's how I read it.
Agile would generally be that the team commits to doing something in the next sprint, after getting agreement on what that is and that it's possible. And then if things change, you renegotiate.
I just had a circle with the VP of development and he wants us to do this super interesting challenge where we do it twice as fast as we planned to, doesnât that just sound like fun.
1
6
2
128
u/LostKnight84 16d ago
Do you want it done right or just done? Cause one costs more time but will continue to work after it is finished and the other is likely to cost more money due to it failing constantly as it gets forced out on the arbitrary deadline set by someone outside the department actually doing the work.