Irregular verbs 9.3

1234567891011121314151617181920212223242526272829303132333435363738394041424344
Across
  1. 1. — The Scrum Master ______ that the Daily Scrum should focus on progress toward the Sprint Goal. (decir)
  2. 3. — The delayed release ______ the company an important business opportunity. (costar)
  3. 6. — The Product Owner ______ by the decision to prioritize customer value over additional features. (mantenerse firme)
  4. 7. — The team's velocity ______ after two experienced developers left the project. (caer / disminuir)
  5. 9. — The team ______ the client's confidence by delivering working software frequently. (ganar)
  6. 10. — The Product Backlog ______ more manageable after the team refined the highest-priority items. (volverse / convertirse)
  7. 12. — The company ______ a new collaboration tool to support its distributed Agile teams. (comprar)
  8. 13. — The Product Backlog ______ considerably after the first customer interviews. (crecer)
  9. 15. — The Scrum Master ______ to protect the team from unnecessary interruptions. (luchar)
  10. 17. — The team ______ unnecessary features from the first version of the product. (eliminar / recortar)
  11. 19. — The team ______ several new backlog items after talking to customers. (escribir)
  12. 21. — The Scrum team ______ a realistic goal for the two-week sprint. (establecer)
  13. 23. — The developers ______ their focus on the Sprint Goal when new requests appeared. (mantener)
  14. 24. — The developers ______ a serious defect before the Increment reached the customer. (detectar / atrapar)
  15. 26. — The developers ______ about their progress and obstacles during the Daily Scrum. (hablar)
  16. 27. — The developers ______ one low-priority feature for a future sprint. (dejar)
  17. 29. — The team ______ several changes after receiving feedback from stakeholders. (hacer)
  18. 30. — The developers ______ the customer's needs better after observing users interact with the product. (comprender)
  19. 33. — The developers ______ several tests before presenting the Increment to stakeholders. (realizar / ejecutar)
  20. 34. — The Product Owner ______ the most valuable items from the Product Backlog. (elegir)
  21. 36. — The team ______ a simple diagram to visualize the new workflow. (dibujar)
  22. 39. — The team ______ useful information from users during early product testing. (obtener)
  23. 40. — The developers ______ a working prototype during the first sprint. (construir)
  24. 41. — The organization ______ close attention to user feedback throughout the Agile project. (prestar / pagar)
  25. 44. — The Scrum team ______ a Sprint Retrospective after completing the iteration. (realizar)
Down
  1. 2. — Customer feedback ______ many of the changes in the next product iteration. (impulsar)
  2. 3. — Several unexpected requirements ______ from stakeholders during the project. (venir / surgir)
  3. 4. — The developers ______ about different ways to solve the customer's problem. (pensar)
  4. 5. — Team members ______ more confident after clarifying the Sprint Goal. (sentirse)
  5. 6. — The company ______ the first version of the product after several successful iterations. (vender)
  6. 8. — The team ______ difficulty completing all the planned work during the sprint. (tener)
  7. 11. — The Product Owner ______ a discussion about the priorities for the next release. (liderar)
  8. 12. — The Sprint Review ______ several problems with the product to the team's attention. (traer)
  9. 14. — Customer satisfaction ______ after the team delivered several useful improvements. (subir / aumentar)
  10. 16. — The stakeholders ______ valuable feedback during the Sprint Review. (dar)
  11. 18. — The team ______ valuable time because several requirements were unclear. (perder)
  12. 20. — The team ______ an improvement in productivity after changing its workflow. (ver)
  13. 21. — The Product Owner ______ updated information to the stakeholders after the Sprint Review. (enviar)
  14. 22. — The Scrum Master ______ action when an obstacle affected the team's progress. (tomar)
  15. 23. — The team ______ that some requirements could change during development. (saber)
  16. 25. — The team ______ too much time discussing a low-priority backlog item. (pasar / gastar)
  17. 27. — The team ______ an important lesson from the unsuccessful sprint. (aprender)
  18. 28. — The team ______ an important problem during product testing. (encontrar)
  19. 31. — The Scrum team ______ with several unexpected problems during the sprint. (lidiar / tratar)
  20. 32. — The development team ______ the sprint with a clear set of priorities. (comenzar)
  21. 35. — The Product Owner ______ different opinions from stakeholders during the Sprint Review. (oír / escuchar)
  22. 37. — The developers ______ the user stories carefully before estimating the work. (leer)
  23. 38. — The Product Owner ______ the most valuable feature at the top of the Product Backlog. (poner)
  24. 42. — The developers ______ additional testing before releasing the Increment. (hacer)
  25. 43. — The developers ______ the Sprint Goal despite several technical difficulties. (cumplir)