How to Work with Iterations
Nowadays the agile models of project management are increasingly taking part of analysts reality. Scrum is the one of the most known method to apply the agile methods in software projects. An important feature of Scrum is to give to customers the possibility to change the requirements along the project's life cycle without the usual impacts that cause pain and discord among the team. In Plandora, the project leader is able to create for each project an "iteration" entry.
An iteration is used to grain the project in small parts in order to allow an incremental development. At Scrum, iteration is called "Sprint". Then it is possible to nominee a number of Sprints in Plandora using the "project occurrence" feature. With sprints inserted into the tool, the leader can easily to link an requirement (or "backlog item" if you are talking in Scrum language) with a sprint. In agile model, the requirements must be prioritized and allocated into a small period of time (normally sprints has duration between one to for weeks). On the other hand, the remaining requirements (out of the sprint) could be freely changed or even excluded by customer.
At Plandora, the customer changes the prioritization of requirements through the web GUI freely. However according to the agile model rules, when a sprint starts (to do this the project leader must change the status of iteration into the tool), the requirement changing and prioritization will be locked in order to avoid misconfusion in current iteration.