Archive:Why playbacks work: Difference between revisions
wikademia>Chungw Initial behavior page |
wikademia>Wikademia m moved Why playbacks work to Archive:Why playbacks work |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
Apply this concept to a project where users can contribute input during every stage. Provide visibility into how decisions get made, why specific requirements are defined as they are, and when popular features will be implemented. The change management problem becomes a lot easier to handle. | Apply this concept to a project where users can contribute input during every stage. Provide visibility into how decisions get made, why specific requirements are defined as they are, and when popular features will be implemented. The change management problem becomes a lot easier to handle. | ||
== Applies to == | |||
{| | |||
| [[Image:DemocracyGlobe.gif|left|link=Charter for bpm democracy]] | |||
| [[Charter for bpm democracy|Charter for BPM Democracy]] | |||
|} | |||
{{ntnes}} | |||
[[Category:(Anti-)Behaviors of business process management program governance]] | |||
Latest revision as of 22:32, 26 April 2009
Summary
Playbacks, or interactive sessions, where feedback can be provided on a solution at regular intervals is one mechanism to encourage contribution from the end-user population. They are successful because they reduce the surprises that might occur at release time. Users are less likely to be shocked because they have participated all along.
Apply this concept to a project where users can contribute input during every stage. Provide visibility into how decisions get made, why specific requirements are defined as they are, and when popular features will be implemented. The change management problem becomes a lot easier to handle.
Applies to
 |
Charter for BPM Democracy |