Updated: Sep 18
We have all seen this type of project happening around us. Very often, we fail to see any value at the end of the project journey, as the project costs are usually bigger than the effective added value.
Is this avoidable? Yes, it is. This usually happens because the user requirements were not captured properly, and consequently, the new systems don’t address the users’ needs.
It is critical to write good user stories following acceptable agile management principles. A simple structure needs to be followed, with all the details of what’s needed but without including a solution to the problem. See a few examples in the table for your journey.