News for hackers. Stuff that matters.
Re:“It would be career limiting “ by Seattle3503 on Tuesday November 08, 2022 @02:28PM (#33523157)
Yeah, it seems like scope needed to be reduced in order to deliver an MVP on time.
Re:“It would be career limiting “ by Mathnerd314 on Tuesday November 08, 2022 @02:39PM (#33523283)
It seems like Agile would have been a great fit. Too many requirements, no real information - it's exactly the situation where throwing out prototypes and getting feedback can lead to a solution.
Re:“It would be career limiting “ by TremendousJudge on Tuesday November 08, 2022 @02:49PM (#33523399)
I don't think hiring some certified Agile gurus and reshuffling all the teams in the middle of the project would have improved the chances of delivery.
Re:“It would be career limiting “ by ajmurmann on Tuesday November 08, 2022 @02:57PM (#33523487)
It depends if you do certified Agile™ or apply some core agile principles. Getting something that works ASAP and then iterate is a huge win whenever possible. Losing steam on a project that hasn't met any useful milestone yet must be one of the main sources of waste in our industry. Granted, 15 months in might make it tough to correct course towards a shippable milestone. Definitely worth the exercise tough.
Re:“It would be career limiting “ by tootie on Tuesday November 08, 2022 @03:11PM (#33523642)
Agile is great for running execution teams and gives you real-time feedback on progress, but if you have a contract with fixed scope and timeline, you're just boxed in. Agile requires flexibility on time and/or scope and it's not amenable to a services contract unless you have a very trusting customer.
Re:“It would be career limiting “ by Mathnerd314 on Tuesday November 08, 2022 @03:35PM (#33523947)
It's not clear how long the project lasted but it was at least 3.5 years. So the time-line couldn't have been that rigid; yes there was a Gantt chart but those are like horoscopes. And since the requirements kept coming in there was no fixed scope.

As far as the customer goes you can say something like "we'd like to deliver a prototype early" and then it sounds like you're exceeding the contract. You just have to get them to prioritize features while avoiding discussing the fact that it's impossible to deliver all the features they requested. Basically you treat the lists as a wishlist rather than a requirements list. Maybe you come clean later once they like the prototype.

I'm not saying it would work, I'm just saying it's better than giving up and saying "the project is doomed" like OP did.

Re:“It would be career limiting “ by mandevil on Tuesday November 08, 2022 @03:27PM (#33523845)
Here is where the outsourcing happening in this story comes back to bite, though. It's basically impossible to write a good contract for an Agile development process. (The only time I've seen it at all is in gov't work, where cost-plus is the default way to pay, and it doesn't often produce good software.)

If I'm the customer, why would I accept anything less than X for the amount of money I'm paying, and if I'm the developer, then Y is a perfectly good MVP, and since X >> Y, who determines when you are finished?

Re:“It would be career limiting “ by mcv on Tuesday November 08, 2022 @03:35PM (#33523949)
Contracts for non-Agile processes are pretty worthless too if the project happens like this. If I understand correctly, the client ended up swallowing the cost for being intentionally lied to.

In an Agile process, the client would be much more closely involved with the development, attend sprint reviews, ask questions, and be available for questions about whether to drop features or extend the deadline. The client can make an informed decision and sound the alarm when too much time is spent on things they don't need.

Re:“It would be career limiting “ by mandevil on Tuesday November 08, 2022 @04:15PM (#33524411)
Agreed that software development outsourcing rarely works!
Re:“It would be career limiting “ by mcv on Wednesday November 09, 2022 @03:36AM (#33528820)
It can work, and it has to, because the vast majority of companies in the world simply cannot write their own software. The problem is big software companies that mostly exist to leech of those other companies' lack of understanding of software. Basically every company that outsources software still needs to have at least one person who understands software development and project management sufficiently to keep an eye on the development process and check that they're not being scammed.
Re:“It would be career limiting “ by pyrolistical on Tuesday November 08, 2022 @02:36PM (#33523241)
I wonder if we have conditioned clients to expect everything now. Are we harming our own customers by allowing them to make demands that in turn only harm themselves in the long run?

Do we have too much of a revolving door for an organization to see this trend?

Re:“It would be career limiting “ by rayiner on Tuesday November 08, 2022 @02:40PM (#33523298)
Yes. If you need more time ask for it and explain why it’s necessary and why the delay couldn’t have been anticipated. It’s better to be late than be late and also delivery a shoddy product.
Re:“It would be career limiting “ by HeyLaughingBoy on Tuesday November 08, 2022 @03:49PM (#33524109)
Sounds a lot like the discussion I had with my 12 year-old about his Science term paper :-)
Re:“It would be career limiting “ by rayiner on Tuesday November 08, 2022 @04:56PM (#33524866)
Being transparent and communicating roadblocks early is just a good way to get through life. Nobody likes to hear something will take longer than expected, but what people really hate is non-communication that leads to unexpected delay, or even worse, poor work that's delivered late.
Re:“It would be career limiting “ by throwawaysleep on Tuesday November 08, 2022 @03:16PM (#33523707)
Pretty much. I have never seen a product manager/project manager see a multi year project through to the end.

I also suspect a lot of it comes down to it not being the problem of anyone until the end of the project. Sales can promise whatever they want. Tech can put it off for a while.

Re:“It would be career limiting “ by origin_path on Tuesday November 08, 2022 @03:39PM (#33523999)
"Are we harming our own customers by allowing them to make demands that in turn only harm themselves in the long run?"

It sounds paternalistic but yeah, that can happen. I've been in this sort of office politics situation where that was an issue.

The problem in that case was that the projects were quite long and touched many different people inside the customer companies, many of whom had differing agendas. In particular the customers were banks and their security people had a habit of demanding very specific changes that would clearly sink the entire project a couple of years down the line, and even contradict the original justifications for it.

Unfortunately the company I worked for at the time had a lot of difficulty with this concept. The upper management tended to abstract the political complexity inside these banks as "the customer wants X so why aren't we giving them X" where in reality there was no "the customer", just lots of people inside big orgs who weren't really talking to each other. The notion that "the customer" could be incoherent and we needed to manage that somehow just wasn't there at all, they just saw it as anti-social arguing. So it was in fact career limiting for me to point out these issues.