Positioning Stories

Scheduling all stories to be accepted in the last iteration is not only against all agile principles. It is, in fact, ineffective. Since the idea of a quick feedback is lost.

First we learn how to write one requirement. Then we learn how to write many requirements for the whole project, so to accept these requirements within certain iterations.

Actors for a story are not always end-users, but could be internal to a project.

To plan improvement, means to slowly shift from ‘left picture’ to ‘right picture’. What is the logical sequence of tasks to facilitate such ashift? Many folks write that, spending the first week of a project on ‘warm andfuzzy holding hands’ (instead of moving right into the thick of development) is a wrong thing to do.

‍