Todo lo bueno llega a su fin y la iteración o el ciclo del Sprint, también. Al finalizar cada iteración comienzas a planificar la siguiente pensando en las características o features que se desarrollaron la vez anterior y cuál fue su calidad.
Planifica la próxima iteración
El final de la iteración está aquí. ¿Qué hacer ahora?
You have already finished the work for this iteration, so it’s time for the Retrospective Session.
It’s important you have a standard set of questions to review, think about the future, and calculate your metrics.
Ask questions like:
What did we do well in this iteration?
What are our takeaways after this iteration/sprint?
What are our areas of opportunity, and how can we improve?
What are our main pain points?
Once that is done, start again. Follow the standard procedure for iterations:
Speaking to the customer.
Analyzing the requirements.
Coming up with user stories.
Estimating user stories, learn from your VELOCITY.
Playing planning poker to reach consensus.
Start again.
Estime nuevamente y aprenda de sus datos (VELOCIDAD)
Corresponde analizar también el rendimiento de tu equipo. ¿Cumplen con todas las tareas? ¿Quedan tareas sin hacer? ¿Por qué?
Calculate your metrics and make sure you are readjusting after the iteration, your team may be working faster than you thought or more slowly.
Perhaps you could check your tasks' breakdown approach. Adjusting is good.
Finish in a rush?
Probably something was skipped. Test and make sure everything is ok.
Plan some time at the beginning of the next iteration to recover from the “photo finish”.
Review your task breakdown approach and adjust your Velocity.
Finish Early (with extra time):
Is the project going well? Is the anything you haven’t fixed? Do you have any bugs to fix?
Use your time wisely. Get one of your highest priority user stories programmed for the next iteration and start.
Finish late:
Why were you late? Velocity problem? Estimation problem? Procrastination?
Maybe there is some code that hasn’t been completed, so you may expect to get some bugs. Adjust before the next iteration.
Sobre todo, si tienes el rol de liderar el proyecto o el equipo, te corresponde realizar análisis sobre el rendimiento del equipo para transmitir esa información al cliente y buscar una mejora continúe del equipo de trabajo.
