YES YES, IT'S NOT TIME BUT WE ARE TRACKING IT THAT WAY BUT IT'S IMPORTANT FOR YOU TO NOT THINK OF IT THAT WAY WHEN YOU ESTIMATE BUT WHY DID YOU GO OVER THREE DAYS
Let's all head to the conference room, so we can discuss the definition of a story point for an hour. I'd also like to talk about why we are behind schedule and our velocity is dipping. Let's make it two hours.
It's my favorite Godzilla movie because of this aspect. There's a scene where I lost it in the theater when the >!Prime Minister is completely certain in telling the press that Godzilla will absolutely never, not in a million years, not make landfall.. only to have an underling whisper in his ear that Godzilla just made landfall.!<
I worked for a Japanese company at the time, and could recognize that it wasn't even heightened for parody. That's just exactly how it is.
I don't work in software, I'm a chemical (aka process) engineer.
Some project managers are superfluous if they don't have a background being an engineer of some discipline themselves, but the vast majority I've worked with are excellent because they have a working knowledge of everything required to progress each stage of the project, and deal with most of the client interactions.
Being able to say: "we've done x, but we still need y, z and aa to progress" and then the project manager organising this getting done together with the other discipline leads is a godsend, letting you focus on doing the actual calculations/design/nitty-gritty details. And the fact they manage the annoying role of dealing with clients and the disagreements around that is also great.
This is working as a consultant, but I imagine if you replace clients with higher ups, I'd imagine the same still applies.
Perhaps things are very different in software, but I do think there is some use for them.
But I've never had one check up every 15 mins, more like once a day, and only if something is very time sensitive. Otherwise it's once a week, or by email as required.
At my job, me and another guy were given stuff to work on. But unknown to product, there's a lot of shared code there.
In my imagination, it should be someone's job to coordinate this. Instead, I finished a chunk of mine, he finished a chunk of his, and then there was confusion. Maybe that's just a technical team lead's job.
Good project managers are invaluable. I'd much rather explain status to a sympathetic ear and have them reword it for diplomacy than try and directly advocate with executives - and I celebrate any customer communications I don't have to be a party to.
When PMs act like part of the dev team and handle the communication side of the project it lets devs focus on the important shit... and if your PM is asking for daily updates then they're too green (or you're too unreliable) to have built up a good level of trust. Nobody fucking cares if a project is delivered at 3PM or 4PM, so who the fuck cares about daily or hourly project updates - the status won't be materially different.
It's like managers or fellow developers - good ones are invaluable and shitty ones make everyone's lives harder... the difference is that PM seems to be a position that attracts do-nothing folks so it's more likely you'll get a shitty roll.
When a team of programmers is left to their own devices, they too screw shit up. They all do things in their own way and argue over what is best, and often fail to see the bigger picture.
I watch scope creep and lack of organizational planning from both programmers and managers. It's all personality issues.
I also don't believe anyone actually follows or knows what agile is (not saying I do either). Everyone on every team at every place sure talks about it, but it doesn't seem like anyone actually does it. These are all just labels for "we adapted as we went."
"Quick! Hurry! Scrum! 5 minute stand up team! We need to sort this crisis out NOW!"
"Joe! The building is on fire! Move! RUN!"
"No! We need to have a meeting first! SCRUM! STAND UP! AGILE! SILICON VALLEY!!!1!!!1!! When is the next sprint!?"
Looking for a passionate, motivated team member to be part of a newly refreshed team created to replace an unsuccessful team (RIP) promoting our incredibly competitive product!
You must have at least 40 years experience working with Windows 11.
GENEROUS remuneration package!*
You need to be able to work 26 hours a day 9 days per week.
You will need to bring PASSION! ENTHUSIASM! EXCITEMENT! [synonym not found]!, and GRIT!
*as we are a small start up, we can't afford to pay wages, but when we are successful, we promise to write your name somewhere on an archived version of our website.
Someone watching Silicon Valley could be forgiven for coming away with the impression that most software developers spend 90% of their time screwing around waiting for solutions to unexpected bullshit interruptions...
It's definitely satire, but I feel Silicon Valley did a decent job. Yes they absolutely made things up, but it was more about the backend and pushing updates and servers being erased because someone accidentally sat a drink on a keyboard.
In an interview about silicon valley the creators said they interviewed a lot of people in the industry and had to actually cut out a bunch of stuff because it wouldn't be believable by people outside the industry. One small example was the valuation. The VC people they talked to said pied piper would have gotten a lot more money than what ended up being in the show