Agile Product Management Course (100% Accurate)

User Story correct answers high level requirement used by developers to produce a high level estimate - used to document a products functional requirement 1/2 day and 2 days to develop.. anything longer is a feature or an epic and needs to be split into mult stories Brief description (of user story) correct answers starts with the end user then what they want to do and the value to the customer (the user role) Parts of a user story card correct answers Title, brief description, story points, can add note at the bottom User Story Structure correct answers before writing your story ask: who is the user and their role? what they are trying to achieve? why they want to achieve it? "As a user type I want to do something so that I can derive a benefit" INVEST correct answers independent, negotiable, valuable, estimable, small, testable Acceptance Criteria correct answers satisfaction criteria, 7 Acceptance Testing correct answers - WHOLE team responsibility - not complete and cant be assigned to sprint without the criteria - can be added at anytime by any team member - PO sits down with engineering and QA to define the acceptance criteria Acceptance Test Structure correct answers Given, When, Then ex: given the customer is logged in, when they click on the account management link, then they are taken to the edit account management page. Non functional requirements and constraint cards correct answers (remain true across iterations) browser support, tech decisions, interface standards, number of users, response time List of Documentation's correct answers product visions and roadmaps project charters business case market needs MRD Product description PRD problem scenarios use cases functional and technical specs user interface guidelines