Back

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.

How do you have waterfall without known requirements? What does waterfall have to do with anticipating work?

Can you elaborate in detail what the problem is? It’s not apparent from what you’ve detailed so far.