My old manager sent out invitations to the bride‘s family before telling me I was the groom.
(he publicly announced the new product‘s price and release date before telling the dev team that there will be a new product)
I've never had a boss who didn't do this. Promise, set timeline and price, get contracts signed, then come to the development team to ask whether it's possible to do by Wednesday. Many years ago I had a boss who promised a major client that we'd provide an entire online advertising network to rival Google Ads, and gave us 4 days to design, develop and deliver it. Then when it wasn't ready he threw one of the developers under the bus in a meeting with the customer. He actually used the words, "This is Dave's fault." Dave was professional and didn't argue. Good look for a CEO. I'm sure he thought he had won. The project went nowhere because all the execs had different ideas about what it was supposed to do, and the dev team was oddly unmotivated to help them out.
Research projects:
"I've set the wedding date. I'm not sure they exist."
The grant proposal:
"They definitely exist, and this marriage will change the world. The wedding must be funded now or else we risk someone else marrying them and getting all the credit for the wedding."
Isn't this what Agile* is supposed to solve?
*The actual principles of Agile, not whatever bastardised version your team is doing!
How many story points is it to get to 2nd base?
We're saving ourselves for marriage, that's not part of the MVP
Propely done Agile is more to solve the "We have the general idea of what we need but will only know for sure the details of how it will work once the users see it and start playing around with it".
You still need to upfront know that a wedding is actually needed, but have a process for figuring out and trying out the details of the various elements of it (say, as part of deciding what kind of food will there be for the reception, actually preparing and trying various options) before the whole things actually gets "delivered".
Agile also works well for environments were software is developed to serve the kind of business which is are constantly changing (for example, certain areas of Finance) or is something totally new being created from the ground up (i.e. many if not most Startups) because the business itself is a sort of a neverending "we'll figure out what we need and if it works well when we get there and try it out" which matches almost perfectly the fast and scope-limited definition->implementation->feedback cycles of the Agile software development process.
agile is the communism of software developers
How many fully stacked devs does it take do scrum her to the altar?
My experience has been more like:
"We've scheduled the wedding. Not only have I not asked her out, but the [potential] bride is guaranteed to be completely turned off by the whole idea. I won't know that because I'm not going to ask her opinion about anything until she ghosts me three weeks before the wedding."
I once had a customly designed project for an external client of a web-development company were I was technical lead and the sales guy who sold it to the customer without ever consulting us about it had the project management responsability.
On the very first day the guy got me, the junior developer and the designer together for the project launch meeting and started saying how we would have to work extra to make it fit his (ridiculously short) deadlines and I just said "No, it's not at all possible to fullfill those deadlines so that's not going to happen" and when he tried to argue with "what about the client" I replied that "You came up with those estimates and gave them to the client without even talking to us, the experts in that domain, so managing the fallout with the client from that is your problem not ours".
I fondly remember all that because of the transition from downtrodden and unhappy to absolute happiness visible on the face of the junior developer when, after the sales guy / project manager gave us the "work extra hard" spiel I (as the tech lead) replied with "No, that's not going to happen".
(Ultimatelly the project took twice as long as the sales guy's estimates)
The whole "putting the cart in front of the oxen" (as we say in my country) of this meme reminded me of that one (and that memory invariably puts a smile on my face).
English is normally "putting the cart before the horse". Mind if I ask what country uses ox for such a similar saying? I just like language quirks
Also fuck that guy and good on you for telling him to fuck off with his nonsense.
The version, with the ox is from Portugal. Specifically the Portuguese saying literally translates as "put the cart in front of the oxen" (so we use plural oxen rather than horse).
Working for a global consulting firm I can agree.
My delivery manager says he committed to a date. I’m a software engineer - I never commit to anything, and certainly not dates.
Sometimes external actors set the date for you and it’s your job to figure out how. I worked in health care IT and heath care regulators don’t play around. You can and will be fined heavily for missing deadlines.
me irl
