A√ļn no tienes acceso a esta clase

Crea una cuenta y contin√ļa viendo este curso

End an iteration

22/27
Recursos

In this lesson you will go over how to: Plan your next iteration, Estimate again and learn from your data (velocity).

Challenge: use your knowledge of Iterations to solve this quiz. What can I do if my team… finished in a rush, finished early, finished late.

Aportes 14

Preguntas 2

Ordenar por:

¬ŅQuieres ver m√°s aportes, preguntas y respuestas de la comunidad? Crea una cuenta o inicia sesi√≥n.

  • Why the test plan always finish in a rush?

  • What do you think that happen?

Think about this… I share a picture of example, it is in Spanish, but it is a clear example:

And about what to do when we can not meet the deadline. Once I had this issue, it was nothing like this you have explained along the course. Well, what we did that time was to renogotiate the terms. We will have more time, but we also have to do more things to deliver the whole project. But with that meeting we could detect several mistakes to correct, that it may not affect the whole process at fisrt, but they will eventually do.

What would I do in these cases? KEEP TESTING!!! You never know what scenario could be missing.

You know what it came to my mind with this? The patches and updates of videogames. Someday you came back from the job, just wanna sit down and play for a while and you find and update of 4 GB. I think that now I understand this a little better.

I think for all three cases the most important thing is to evaluate why and discuss it with the team.
Finishing in a rush might be because tasks were underestimated, finising too early because of task overestimation, and finishing late may be either because of the first case or because there were problems. In any case, communication is key

Ni pa all√° voy a mirar

vucabulary:
takeaways: conclusiones o ense√Īanzas (similar to key learnings)
painpoints: areas of opportunity

about the questions:
what should I do if my team finish early? A/ I should take this time and divide it 70-30 and the 70% of the time i should use it for make test and find bugs, or looking for a better result, I would ask, how can we improve this result in these ‚Äúfree days‚ÄĚ? and the 30% part I would use it like a gift or like a prize for my team because if all the team achive the goal some days before deadline, and that work was made in a outstanding way they deserve a recognition as a result of their good work.

if my team finished late. I would use the ‚Äúsandwich‚ÄĚ technique to give them feedback and first find the reasons why the work wasn¬īt done on time, look if that reasons are their fault or if there were any factors that could cause the delay. all this process with empathy‚Ķ

When I worked, We always finished late our work.
What happen when we are not agree with the estimation times?
Our boss had estimated the time, but we never finished on time.

If my team finished in a rush, we must review the causes and explore if we can estimate better.
If my team finished early, I will take other user stories, and we would try to develop before for avoid possible lack of time.
If my team finished late, we must review the causes and explore if we can estimate better or divide the user story, may be, it is very complex.

If you don’t finish the job in the deadline, the best of can you make is communicate with your client in advance and set that the project will be delayed until date in question and explain the reason.

_Use your time wisely. Get one of your
highest priority User Stories
programmed for the next Iteration
and start!
_

What are the takeaways of the sprint?

Plan your next iteration
Retrospective session
- Keep it positive
- Standard set of questions
‚óč What did we do well?
‚óč Takeaways after this sprint?
‚óč Areas of opportunity?
‚óč Pain points?

Estimate again and learn from your data (VELOCITY)
Calculate your metrics and make sure you are readjusting after the iteration.

ADJUST!