Document states: button click and real actions
We all realise that changing a task status only reflects the actual activities of the person who performed the task: writing staging or code, running test cases, or doing something else. And we never reduce the status change to simply moving the task to another column. But when the analyst thinks, for instance, about the work with the order, the actual activity is left out of his/her mind, and he/she thinks only about the work with the system. As a result, solutions are created that are not suitable for real life, although formally, the system has all the necessary features.
The talk will consider examples of such problematic situations. It will show how changing the status of documents reflects the task flow just like the familiar task flow on the board, including the decomposition of a large task into several tasks and bundling tasks into release packages.