View Full Version : Is it ever good to....

03-16-2018, 12:20 AM
It is clear to me that some people think an agile approach means you can willy-nilly delete things in the process. This is also true for conventional project, but I do not think for the same reasons. For conventional projects, it seems time pressures cause elimination of certain functions or processes to keep the schedule. For agile, again no study but based on observed discussions, the elimination seems to be because there is no doctrine or perceived process that is required to be adhered. This means things can be arbitrarily altered or changed. That is certainly true, but you must consider what are the consequences of not performing the exercise (for example product demonstration)? What does this product demonstration do, can I eliminate it, and what will likely be the consequences.

For the record, I am not in favor of the above approach of eliminating the product demonstration. I cannot think of a scenario in which that would or could be the best approach, and believe the merits of performing are too high.

confirm delivering the sprint objectives
engage the product owner by evoking feedback on the design instantiation
refine requirements for future work
learn (brainstorm) more about the product with the product owner
provide energy and a sense of progress and accomplishment
demonstrate success

What do you think?