Program/business Requirements are to “traceable” representatives determine and the decisions made by the validate the business value of Product Owner system functions and features The stories are prioritized and Program/business organized into the “product representatives make decisions backlog” within the repository about the priority of functions Stories are selected on a priority and features basis for inclusion in a Sprint by All necessary tasks/deliverables the cross-discipline team are identified in the baselined The Product Owner monitors the Project Schedule backlog, Scrum Team progress, Key specification documents and work completed making – (e.g., contracts, requirement adjustments (or grooming) the specifications, and/or contract backlog as needed deliverables) and software The Product Owner makes products are under formal decisions concerning configuration control as defined unanticipated business in the Configuration requirements Management Plan Scope management includes Specific acceptance and the use of Scrum ceremonies – delivery requirements are Sprint Planning Meeting, Daily defined for each deliverable Scrum meeting, Sprint Program/business Review/Demonstration Meeting representatives sign off and Sprint Retrospective approval/acceptance at project Meeting milestones and product delivery Scrum team and Product Owner points utilize the lessons learned from the Sprint Retrospectives to improve Velocity and completion results for subsequent Sprints Scope change control practices are being executed in accordance with the documented approached (i.e. Scope Management Plan,
Program/business representatives determine and validate the business value of system functions and features Program/business representatives make decisions about the priority of functions and features All necessary tasks/deliverables are identified in the baselined Project Schedule Key specification documents (e.g., contracts, requirement specifications, and/or contract deliverables) and software products are under formal configuration control as defined in the Configuration Management Plan Specific acceptance and delivery requirements are defined for each deliverable Program/business representatives sign off approval/acceptance at project milestones and product delivery points Scope change control practices are being executed in accordance with the documented approached (i.e. Scope Management Plan, Requirements are “traceable” to the decisions made by the Product Owner The stories are prioritized and organized into the “product backlog” within the repository Stories are selected on a priority basis for inclusion in a Sprint by the cross-discipline team The Product Owner monitors the backlog, Scrum Team progress, and work completed – making adjustments (or grooming) the backlog as needed The Product Owner makes decisions concerning unanticipated business requirements Scope management includes the use of Scrum ceremonies – Sprint Planning Meeting, Daily Scrum meeting, Sprint Review/Demonstration Meeting and Sprint Retrospective Meeting Scrum team and Product Owner utilize the lessons learned from the Sprint Retrospectives to improve Velocity and completion results for subsequent Sprints
SIMM45G_2017-1205.docx