Product Owner: Represents the voice of the customer Define the features of the product; Decide on release date and content; Be responsible for the profitability of the product (ROI); Prioritize features according to market value; Adjust features and priority every 30 days, as needed; and Accept or reject work results. Scrum Master: Maintains the processes in lieu of a project manager Ensure that the team is fully functional and productive Enable close cooperation across all roles and functions Remove barriers; Shield the team from external interferences; and Ensure that the process is followed, including issuing invitations to Daily Scrum, Sprint Review and Sprint Planning meetings. Team: Is cross-functional, with seven (plus/minus two) members; Selects the Sprint goal and specifies work results; Has the right to do everything within the boundaries of the project guidelines to reach the Sprint goal; Organizes itself and its work; and Demos work results to the Product Owner. Stakeholder’s: Customer’s, Vendors, they are only directly involved in the process during the sprint reviews.
On a Scrum project, the team tracks its progress against a release plan by updating a release burndown chart at the end of each sprint. The horizontal axis of the release burndown chart shows the sprints; the vertical axis shows the amount of work remaining at the start of each sprint. Work remaining can be shown in whatever unit the team prefers--story points, ideal days, team days, and so on.
Sprint Review Meeting : A Sprint Review Meeting is held at the end of a sprint Demonstration of potentially shippable product to product owner by product team The Product Owner determines which items on the Product Backlog have been completed in the Sprint Product Owner reprioritize the Product Backlog with team and stakeholder’s for the next sprint Four hour time limit Sprint Retrospective: Led by the Scrum Master team assesses the way they worked together in the sprint and identifies positive ways of working together that can be encouraged as future practice the team also identifies the things that could work better and develops strategies for improvement. The goal is to get a global snapshot of the project discover any new dependencies address any personal needs of committed individuals
A Sprint Review Meeting is held at the end of a sprint Demonstration of potentially shippable product to product owner by product team The Product Owner determines which items on the Product Backlog have been completed in the Sprint Product Owner reprioritize the Product Backlog with team and stakeholder’s for the next sprint Four hour time limit
Sprint Retrospective: Led by the Scrum Master team assesses the way they worked together in the sprint and identifies positive ways of working together that can be encouraged as future practice the team also identifies the things that could work better and develops strategies for improvement. The goal is to get a global snapshot of the project discover any new dependencies address any personal needs of committed individuals
Thank You for watching this Presentation. For any further assistance please contact us at PPMSupport@semanticspace.com
![The Agile (SCRUM) way with PPM Studio ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)