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.
Fucking 4 days.
Well, in Dave’s CEO’s defense, it was just Google Ads.
Just, you know, that thing that largely provides the income for a world top-ten company.
deleted by creator
agile is the communism of software developers
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.
How many story points is it to get to 2nd base?
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.”
