No tienes acceso a esta clase

隆Contin煤a aprendiendo! 脷nete y comienza a potenciar tu carrera

Prepare for the next iteration

20/25
Recursos

La iteraci贸n est谩 llegando a su fin, son los 煤ltimos d铆as de trabajo antes de entregar los resultados del 煤ltimo mes. Antes, tienes que prepararte junto con tu equipo para la pr贸xima iteraci贸n, resolver los imprevistos y buscar una mejora continua en la calidad de trabajo y comunicaci贸n.

Corrige y reporta tus errores

Habr谩 bugs en tu aplicaci贸n, imposible que no los halla. 驴Qu茅 hacer cuando aparece uno?

  • Eventually, your testers are going to find bugs. What happens then? Do you just report the bugs to the team and fix them?
  • Life cycle of a bug:
    • A tester finds the bug.
    • The tester files a bug report.
    • You create a story to fix the bug.
    • You fix the bug.
    • Check the fix and verify that it works.
    • Update the bug report.
    • Reprioritize.

Agrega m谩s historias de usuarios para corregir sus errores

  • You are sure to have bugs in your code. But fixing your bugs will take some time.
  • This creates extra tasks.
  • More tasks mean more user stories, more work, and more time.
  • So reprioritize your tasks.

Vuelve a priorizar sus historias de usuario

Los bugs que aparecen de manera inesperada ocupar谩n tiempo de desarrollo por encima de tareas nuevas. Trabaja con tu equipo para volver a priorizar si es m谩s importante resolver un bug o iniciar una nueva historia de usuario.

  • The time has come to reprioritize your stories based on the bugs.
  • Reprioritization is critical because you want to make sure you are doing the right thing on the project at all times.
  • Reprioritizing user stories will call for adjustments on the fly or once iterations have finished.
  • Take this chance to adjust, adapt, and overcome.
  • Getting feedback and recommendations from other developers can truly make a difference. Ask questions like:
    • What do you suggest we do here?
    • What are your thoughts on this?
    • What do you think should be our number one priority right now?
  • Communication is key!

Sesi贸n de Retrospectiva (RS)

Una reuni贸n de retrospectiva se lleva a cabo al final de una iteraci贸n (sprint). Consiste en que todo el equipo hable sobre qu茅 se hizo bien y hay que mantener y qu茅 se hizo mal y hay que mejorar con respecto a la metodolog铆a de trabajo y comunicaci贸n.

  • An RS is a reflective team meeting at the end of an iteration. You can use it to reflect on what you did well throughout the iteration and talk about possible future modifications.
  • Steps to run an effective RS:
    • Prepare.
    • Set the right culture.
    • Talk about 鈥淲ins鈥.
    • Talk about pain points.
    • Next steps.
  • A Retrospective Session is a great way to finish an iteration, it allows you to make adjustments and reflect on what your team is doing well and what can be improved.

La mejora continua de tu equipo es crucial en el desarrollo de software. Ten en cuenta las tareas que 鈥渆ntran por la ventana鈥 como los bugs, estos ocupar谩n mucho tiempo. Busca la mejora continua con reuniones de retrospectiva y reflexiona acerca del flujo de trabajo.


Contribuci贸n creada por: Kevin Fiorentino.

Aportes 45

Preguntas 0

Ordenar por:

驴Quieres ver m谩s aportes, preguntas y respuestas de la comunidad?

o inicia sesi贸n.

Did you have this problem before?
Do you know somebody in our team that experience same issue?

This is an idea of a retrospective meeting. It鈥檚 excellent鈥

LEGO庐 retrospective
The LEGO庐 retrospective is a fun and stimulating activity that fosters a group conversation about feelings and future directions.

Running the activity

  1. Place the LEGO庐 box at the center of a meeting table (or on the floor).

  2. Ask everyone to sit around the LEGO庐 box, as they will use and share them.

  3. Ask everyone to build an animal with at most 8 LEGO庐 bricks to represent how they are feeling.

  4. Instruct each person to show his/her animal and then talk about it and their feelings.

  5. Ask everyone to build a model with any number of LEGO庐 bricks within 6 minutes to represent the group鈥檚 future directions.

  6. Instruct each person to show his/her model and talk a little about it and their view on the group鈥檚 future directions

This activity creates a playful and sharing environment 鈥 people will share feelings, opinions and LEGO庐 bricks! 鈥 this is especially useful for fostering conversations about feelings and collaboration.

LEGO庐 fosters collaboration and openness on people. LEGO庐 has been used in many workshops and training for creating a learning environment which simulates real work activities or create metaphors for bringing up concepts and conversations.

This activity idea and photos were shared by Alexandre Silva, who ran a retrospective based on a previous LEGO庐 SERIOUS PLAY retrospective blog post by Dominic Krimmer.

Bonuses are almost great as the lessons

  1. do you know any third party library capable to do this better?
  2. should we pay for this service instead of making it by our own?

Correct and report your bugs
The lifecycle of a bug

  • Tester finds a bug
  • Tester files a bug report
  • You create a story to fix the bug
  • You fix the bug
  • Check the fix and verify that it works
  • Update the bug report
  • Reprioritize

Add more user stories to fix your bugs
It will take, it will affect your estimates

Reprioritize your user stories
Make sure you are doing the right thing at the right time of the project
Be sure to get feedback

I love you bonus鈥 teacher 鉂わ笍

One question would be:
From our last iteration, do you have any ideas on how we can improve that feature?

How can we do it differently or in another way?

What do you think about this fix in my code?
What do you think?, may be, Am I changing the functionality of this code?

  • Do you have another idea how we can handle this?
  • How this will affect our deadline?

It is important to solve quickly the bugs to deploy them as soon as possible. To help QA team. thanks

Thanks

Thanks 馃槉

thank you teacher

do you know any third party library capable to do this better? should we pay for this service instead of making it by our own?
Make sure you are doing the right thing at the right time of the project Be sure to get feedback
Add more user stories to fix your bugs It will take, it will affect your estimates Reprioritize your user stories
Correct and report your bugs The lifecycle of a bug Tester finds a bug Tester files a bug report You create a story to fix the bug You fix the bug Check the fix and verify that it works Update the bug report Reprioritize
This activity idea and photos were shared by Alexandre Silva, who ran a retrospective based on a previous LEGO庐 SERIOUS PLAY retrospective blog post by Dominic Krimmer.
LEGO庐 fosters collaboration and openness on people. LEGO庐 has been used in many workshops and training for creating a learning environment which simulates real work activities or create metaphors for bringing up concepts and conversations.
This activity creates a playful and sharing environment 鈥 people will share feelings, opinions and LEGO庐 bricks! 鈥 this is especially useful for fostering conversations about feelings and collaboration.
Instruct each person to show his/her animal and then talk about it and their feelings. Ask everyone to build a model with any number of LEGO庐 bricks within 6 minutes to represent the group鈥檚 future directions.
Running the activity Place the LEGO庐 box at the center of a meeting table (or on the floor). Ask everyone to sit around the LEGO庐 box, as they will use and share them. Ask everyone to build an animal with
This is an idea of a retrospective meeting. It鈥檚 excellent鈥 LEGO庐 retrospective The LEGO庐 retrospective is a fun and stimulating activity that fosters a group conversation about feelings and future directions.
Did you have this problem before? Do you know somebody in our team that experience same issue?
Hello

Thanks

馃榾馃榾

Also

Firts

More

Awesome

Hello

FINDING A BUG: It implies creating a new user story to fix it. However, adding a new user story, also implies more tasks, more work, and more time. So, take into account adjusting the timeline or taking into consideration these drawbacks on your estimates.

good
yes

Prepare for the next iteration This is an idea of a retrospective meeting. It鈥檚 excellent鈥

LEGO庐 retrospective
The LEGO庐 retrospective is a fun and stimulating activity that fosters a group conversation about feelings and future directions.

Running the activity

Place the LEGO庐 box at the center of a meeting table (or on the floor).

Ask everyone to sit around the LEGO庐 box, as they will use and share them.

Ask everyone to build an animal with at most 8 LEGO庐 bricks to represent how they are feeling.

Instruct each person to show his/her animal and then talk about it and their feelings.

Ask everyone to build a model with any number of LEGO庐 bricks within 6 minutes to represent the group鈥檚 future directions.

Instruct each person to show his/her model and talk a little about it and their view on the group鈥檚 future directions

This activity creates a playful and sharing environment 鈥 people will share feelings, opinions and LEGO庐 bricks! 鈥 this is especially useful for fostering conversations about feelings and collaboration.

LEGO庐 fosters collaboration and openness on people. LEGO庐 has been used in many workshops and training for creating a learning environment which simulates real work activities or create metaphors for bringing up concepts and conversations.

This activity idea and photos were shared by Alexandre Silva, who ran a retrospective based on a previous LEGO庐 SERIOUS PLAY retrospective blog post by Dominic Krimmer. Correct and report your bugs
The lifecycle of a bug

Tester finds a bug
Tester files a bug report
You create a story to fix the bug
You fix the bug
Check the fix and verify that it works
Update the bug report
Reprioritize
Add more user stories to fix your bugs
It will take, it will affect your estimates

Reprioritize your user stories
Make sure you are doing the right thing at the right time of the project
Be sure to get feedback

good

I like it a lot, learning is good

Correct and report your bugs:

  • A tester finds the bug.
  • Tester files a bug report.
  • You create a story to fix the bug.
  • you fix the bug.
  • Check the fix and verify that it works.
  • Update the bug report.
  • Reprioritize.
    Add user stories to fix bugs:
  • You鈥檒l need to prioritize some tasks and create some extra of them.
    Reprioritize your user stories:
  • Constant communication is critical.
  • Reprioritizing stories will call for adjustments on the fly or once iterations have finished.
  • Aske questions to get recommendations.

The key: Reprioritize your user stories

Did you create the bug documentation?

Define the top 3 functions your website should have no matter what!

Always reprioritize!!

May I ask鈥ow will you make it?