I think that's a pretty smart model - best/worst/most likely.
One thing I found lacking in kabuki agile theatre was that we were ABSOLUTELY NOT supposed to "get into the weeds" in meetings where we talked estimates.
But how does one uncover the best/worst/most likely without doing so?
You can spend 20min writing the most beautiful Acceptance Criteria but if you don't get a bit into detail on what the user actually wants it's all for naught. It could be way simpler (hey what if I just did X) or way more complex (oh well now that you mention it..), etc.
Typically it was engineering manager & engineers sitting in a room discussing requirements with each other. What could go wrong obviously? lol.
But how does one uncover the best/worst/most likely without doing so?
You can spend 20min writing the most beautiful Acceptance Criteria but if you don't get a bit into detail on what the user actually wants it's all for naught. It could be way simpler (hey what if I just did X) or way more complex (oh well now that you mention it..), etc.
Typically it was engineering manager & engineers sitting in a room discussing requirements with each other. What could go wrong obviously? lol.