41

Scene: Surprise meeting with the project owner 0-3 days before the go-live date

"Hey team, the business and I have decided to postpone the project release by n=1-3 months because [they aren't ready for it / it isn't finished /regulatory reasons]. And since we have some extra time now, we can tie up all the loose ends on this project (i.e., 'we've added n+1 months worth of backlog items to the MVP')."

I'm still a greenish dev, so maybe this is normal, but I've had the same story going on for over a year now, and it's really starting to burn me out. In the beginning, I was optimistic. Now I just hope for the project to fail, or me to get off somehow, but this thing just won't die.

Anyone with experience on similar projects able to share words of advice? Do they ever end up working out? Seems there's a death spiral, since we are always rushing to a deadline, forgoing tests and quality but never cleaning up our mess because we're already behind. Yet I somehow feel like I'm the crazy one for thinking this 6-month "quick" side project turned 2+ year half-rewrite will have trouble meeting it's Nth deadline.

you are viewing a single comment's thread
view the rest of the comments
[-] Lmaydev@programming.dev 10 points 5 months ago

This sounds like the old waterfall approach to development.

Design the whole system, create the whole system, test the whole system.

The problem with this approach is that requirements almost always change or scope creeps in those timeframes.

Now most companies are bad at agile. But even moving slightly towards it is better than nothing.

This will continue to happen until the project management changes unfortunately.

If the system can't be worked on in small independent chunks this is basically guaranteed to happen.

We do agile very loosely. But we have a two week sprint and at the end we, hopefully, have the features we decided on done and deployed. Then we can get feedback and add the required changes to the backlog for a future sprint.

This way you get feedback a lot quicker and as you pick work every two weeks you can keep things moving forward.

Chances are the company won't change so if it bothers you looking for another job may be a good shout.

this post was submitted on 29 Feb 2024
41 points (95.6% liked)

Programming

16687 readers
282 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS