Para que un plan de iteración esté completo debe cumplir con ciertos criterios, uno de ellos es su estructura, ésta debe estar compuesta por: tareas de documentación, tareas de diseño, tareas de codificación y tareas de testing, el equipo que sigue el plan debe tener asignada una tarea de cada tipo, por lo menos. Ya que eso es lo que hace a los miembros del equipo desarrolladores y puedan ejecutar el plan para que se logre el objetivo de terminar todas las tareas de la iteración y generar y poder entregar un producto funcional.
Now that we know how we did in the last iteration, the good things we achieved and the mistakes made, it's time to put all that retrospective into practice, week one of real work of iteration 2 begins and we have to start implementing all the solutions or changes that we have found in the retrospection phase.
We do not expect that the changes will solve 100% of the bugs of iteration 1, however they will take us closer to perfection, and the closer we are, the better the overall development process of any software product will be.
If this is not the case, we can say that it happened for one of these two main reasons:
1.- The retrospection was not carried out correctly or the problems of the past iteration were not internalized or there was not enough time to analyze that part well.
2.- The work of iteration two became much heavier or the workload increased (either in process or documentation), or simply the delivery times along with the pressure of new requirements intensified.
Whatever the future holds, we know we are capable of delivering a complete product, even though we have almost no experience developing products of this size.
I learned how important my role is for the team, that all roles are essential, the project cannot be carried out if one of them is missing. I have understood that everyone in the team must participate in all stages of product development, that no one is left doing nothing and that we all know what is being done, from requirements to testing.
Last time we didn't include milestones in our plan and that had consequences for the product. Placing milestones strategically serves as a goal, as a warning and helps to créate plan recovery strategies.
Thanks to what we found on iteration 1 and all the mistakes we did, we can build a better iteration olan, which will result in a better job and better outcome. In case we need to add tasks or remove them, we'll have to make a change request, so that every change is documented. After that, every developer has to complete their own planned tasks and fulfill their role completely.