Well said! We often force the decision stuff by going ahead and making the decision ourselves. This particularly works well if you have domain knowledge. But, regardless, you're doing something, making something, which the user can react to. And, if they react negatively, they get to choose between fixing what you did (when you'd otherwise be idle) OR putting it at lower priority, giving you more work to do, and making sure that they are there to make decisions (now that they know they see the consequences, otherwise). (whew, long sentence)
Go to the Scrum Discussion group on egroups if you run into problems and want other people's advice.
Ken
Slashdot Mirror
Well said! We often force the decision stuff by going ahead and making the decision ourselves. This particularly works well if you have domain knowledge. But, regardless, you're doing something, making something, which the user can react to. And, if they react negatively, they get to choose between fixing what you did (when you'd otherwise be idle) OR putting it at lower priority, giving you more work to do, and making sure that they are there to make decisions (now that they know they see the consequences, otherwise). (whew, long sentence) Go to the Scrum Discussion group on egroups if you run into problems and want other people's advice. Ken
The techniques were way agile; we were shooting for an OOPSLA release and were behind schedule. Sorry.