# SCRUM Taskforce - Q6 - ![](https://i.imgur.com/FrJPJvK.png) - During a Sprint Retrospective the Develop Team proposes moving the daily scruum to only occur on Tuesdays and Thursdays - Q12 - ![](https://i.imgur.com/2ZoEGKm.png) - What are two ways that architecture and infrastructure are handled in Scrum - Q22 - ![](https://i.imgur.com/iOpKl1m.png) - Q31 - ![](https://i.imgur.com/PFHI6YR.png) - Q48 - ![Uploading file..._jacwh0wig]() - max 4h in 1month sprint - Q61 - ![](https://i.imgur.com/eS0f6DO.png) - It is a complete list of all work to be done in a Sprint. - > Mikhail: The Scrum Guide says “The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.” So, Sprint Backlog is items + plan. Another definition from the Scrum Guide: “The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment.” So, it is a forecast about functionality and work. The suggested answers do not contain the full definition of the Sprint Backlog. B and D contain only a half of every definition (work without functionality and plan without items). - Q72 - ![](https://i.imgur.com/BNzX3mm.png) - 1. The item in the Increment this Sprint should not be included - 2. Put the undone product backlog items on the Product Backlog for the Product owner to decide what to do with it - Q1 - ![](https://i.imgur.com/GlUG3GU.png) - Monitor communications between them and facilitate direct collaboration. - Q11 - ![](https://i.imgur.com/cR7se0k.png) - Who defines the definition of done - organizational Standart - Multiple Teams should have the same sprint start date - No - During the sprint retro high priority improvements - Sprint backlog - Which outcome is expected as Scrum Teams mature - They will improve their definition of "Done" to include more stringent criteria. - How should Product Backlog items be chosen when multiple Scrum teams work for the same product backlog - The Development Teams pull in work in agreement with the Product Owner. - Sprint planning time box - 8 hours or shorter -> DoD - When is implementation of a Product Backlog item considered complete - item has no work remaining in order to be potentially released. - A scrum team is only allowed to meet with the stakeholders during sprint review - false --- ![](https://i.imgur.com/Bd1X4Xk.png) --- ![](https://i.imgur.com/GlflhAz.png) --- ![](https://i.imgur.com/LbyrRpm.png) > The Sprint Backlog contains user stories popped off the top of the Product Backlog during Sprint Planning. => true --- ![](https://i.imgur.com/pnBBOWK.png) What would be good advice to give the Product Owner? Tell the Product Owner that his primary concern is the flow of value reflected in the ordering of the Product Backlog. --- ![](https://i.imgur.com/ERD31fY.png) A, C, D --- ![](https://i.imgur.com/LdDnZAr.png) --- ![](https://i.imgur.com/RNZxxoz.png)