Editing UNITA Agile Management Guide (section)

== Changes ==

Adopting the Agile perspective implies recognising and to welcoming the natural evolution of the project scope. As a project progresses, both the project team and the stakeholders gain a better understanding of the problems to be tackled and how to address them.  
UNITA 2 fully embraces this perspective, limiting the project planning to the activity level, and giving the TT's full freedom to develop these activities into specific actions. This way, all the benefits of incremental and iterative development, and of frequent feedback, will permeate through the project. The Agile methodology is also an excelent way to channel and profit from the enormous creativity and potential of a project team formed by hundreds of academics, students and staff.  
It may happen, however, that certain events require structural changes in the project, beyond the range of what can be tackled at the TT level with individual actions. These changes may arise as a consequence of, for example:
* changes in scope,
* new requirements,
* identified issues or potential risks,
* political decisions that affect the project baselines (scheduling, staffing or budget).

This sort of changes must be discussed and approved at the MC level. Thus, when they are proposed by a Task Team, the TT co-leaders will commnicate them to the WP co-leaders, who will bring the proposal to the MC. If the decision has a strategic or political potential impact, the MC will also seek the approval of the GB.