Aún no tienes acceso a esta clase

Crea una cuenta y continúa viendo este curso

Prepare for the next iteration

21/27
Recursos

In this lesson you will learn how to correct and report your Bugs, add more User Stories to fix your Bugs and reprioritize your User Stories.

Challenge: using your knowledge of the Bug Correction process answer this True or False quiz.

Aportes 15

Preguntas 0

Ordenar por:

¿Quieres ver más aportes, preguntas y respuestas de la comunidad? Crea una cuenta 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’s 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’s future directions.

  6. Instruct each person to show his/her model and talk a little about it and their view on the group’s 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

Bonuses are almost great as the lessons

I love you bonus… teacher ❤️

  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?

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?

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…how will you make it?