this post was submitted on 03 Dec 2023
77 points (92.3% liked)
Programming
17416 readers
76 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Go away middle manager, this is not how software development functions. Shoo.
And you avoid making an app that you show to the customer for the first time only for them to say, "What the hell is this?" My company used waterfall for the longest time, and this happened several times. It was really frustrating.
I convinced my managers to move away from waterfall to a more iterative process using a financial analogy. Pretty much everyone understands the concept of compound interest as it applies to both debt and savings.
I framed the release of small but functional components as the equivalent of small, regular deposits to a retirement account, where benefits start to accrue immediately and then build upon each other with every "deposit". I framed the holding off of a major project until completion as the accumulation of debt with no payment plan. I also pointed out that, like a sound investment strategy, the "portfolio" of features might require adjustment over time in order to meet objectives under changing circumstances, adding substantial risk to any monolithic project.
That seems so smart, let's call it something smart, like what about "Agility"?
Did you even read the article BTW?