this post was submitted on 13 Mar 2025
7 points (100.0% liked)
Engineering Managers
465 readers
3 users here now
Discussion, rants, questions, and more about engineering management.
Resources:
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It depends on what your chief complaint is.
If there’s a good reason to deliver a project using a waterfall approach and the only complaint is that you don’t like waterfall, then I’d advise remembering that a core philosophy of the agile manifesto is “people over processes” and suggest being flexible.
If there’s a pragmatic argument to be made, then have that conversation and see if you can agree on a path forward.
@natecox I'm fairly certain I'm beyond the point of "let's not do this because I, personally, don't like it" in my career 😅
No, the point is that I just cannot anticipate the work that needs to be done. But that is what I would have to do to provide them with what they want.
It sounds like you need a design sprint; which fits fairly neatly into waterfall as an early step.
Google (even though I loathe suggesting anything google these days) has comprehensive documentation on how they do their two week design sprints; I have done them a few times and they do a damn fine job of helping you to find the work you need to do.
https://designsprintkit.withgoogle.com/
@natecox Damn! That's an excellent idea, actually! Thank you so much.
You’re welcome! Good luck with your project, friend.