Across
- 4. The facilitator for an Agile development team.
- 6. A meeting held at the end of a sprint to discuss what went well and what could be improved.
- 7. a set of attitudes that an Agile or Scrum team should have towards their work.
- 10. A visual representation of the work to be done, in progress, and completed.
- 13. The person responsible for defining the features of the product and prioritizing the product backlog.
- 15. A daily meeting where team members discuss progress and obstacles.
- 16. A method for managing work by balancing demands with available capacity and improving the handling of system-level bottlenecks.
Down
- 1. an obstacle that reduces an Agile team’s productivity or prevents them from completing an Agile project altogether
- 2. A time-boxed period during which specific work has to be completed and made ready for review.
- 3. Story A short, simple description of a feature told from the perspective of the person who desires the new capability.
- 5. A graphical representation of work left to do versus time.
- 8. A large user story that can be broken down into smaller stories.
- 9. Daily 15 minute meeting to discuss their day ahead
- 11. A list of tasks or features that need to be completed.
- 12. A meeting where the team plans the work to be performed during the sprint.
- 14. A shared understanding of what it means for work to be complete.
