Did you have this problem before?
Do you know somebody in our team that experience same issue?
Introduction
Welcome to this Course for Developers in English
Communicate with your customer accurately
Customer-oriented requirements
How iteration cycles work
Planning considering priorities
Review: communicate with your customer accurately
Understand your customer and the requirements
Prioritizing requirements
Backlog and Milestone 1.0
Organize your tasks!
Organizing your time into user stories and tasks
Stand-up meetings, analyze and design
Review: organize your tasks!
Create deliverable design
Creating deliverable design
Refactoring, meetings and release
Protect your very valuable software
Understanding the principles of defensive development
Functional and unit testing
Review: protect your very valuable software
Understanding Continuous Integration (CI) and testing
Types of software testing
Handle accidents when building the code and what CI means
Test your Software!
TDD Test-Driven Development
Review: test your software!
Be ready for the end
Prepare for the next iteration
End an iteration
Fix your bugs!
Handle bugs to fit your process
Continuous integration test delivery method
Review: fix your bugs!
Conclusion
We've come to an end!
No tienes acceso a esta clase
¡Continúa aprendiendo! Únete y comienza a potenciar tu carrera
Si ya tienes una cuenta,
Iniciar sesión
Prepare for the next iteration
20/25Recursos
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 “Wins”.
- 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 “entran 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:
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
-
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’s future directions.
-
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.
Bonuses are almost great as the lessons
- 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?
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’s 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’s 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’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
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’s future directions.
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
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’ll 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…how will you make it?
¿Quieres ver más aportes, preguntas y respuestas de la comunidad?
o inicia sesión.