Sprint retrospective sample answers
![sprint retrospective sample answers sprint retrospective sample answers](https://image.slidesharecdn.com/introductiontoscrum-090811143625-phpapp01/95/introduction-to-scrum-42-728.jpg)
Digital asset management Manage and distribute assets, and see how they perform.Resource management Find the best project team and forecast resourcing needs.Intelligent workflows Automate business processes across systems.Governance & administration Configure and manage global controls and settings. The basic structure of a retrospective or debrief is to surface the following in a brief meeting of the whole team: What went well (you’ll want to keep doing these things) What could be improved (went OK, but could be better) What went badly (you want to stop doing these things, if possible, or concentrate on doing them better) A focus for.Streamlined business apps Build easy-to-navigate business apps in minutes.Integrations Work smarter and more efficiently by sharing information across platforms.Secure request management Streamline requests, process ticketing, and more.Process management at scale Deliver consistent projects and processes at scale.Content management Organize, manage, and review content production.
![sprint retrospective sample answers sprint retrospective sample answers](https://i.pinimg.com/736x/3c/eb/db/3cebdb6b7ff9698ce8a753083ce1a658.jpg)
What stopped working during the sprint We didn't meet our delivery date. We were able to demo a working product to the client. What started well during the sprint We completed the user stories we set out to do.
![sprint retrospective sample answers sprint retrospective sample answers](https://image.slidesharecdn.com/sprintreviewandplanningtemplate-130604145644-phpapp02/95/sprint-review-and-planning-template-1-638.jpg)