Scrum is a simple “inspect and adapt” framework that has three roles, three ceremonies, and
three artifacts designed to deliver working software in Sprints, usually 30-day iterations.
• Roles: Product Owner, ScrumMaster, Team.
• Ceremonies: Sprint Planning, Sprint Review, and Daily Scrum Meeting
• Artifacts: Product Backlog, Sprint Backlog, and Burndown Chart

The Product Owner has the following responsibilities
• 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.
The Product Owner is responsible for the first of the three Scrum ceremonies: Scrum Planning.

The ScrumMaster is a facilitative team leader working closely with the Product Owner. He must:
• Ensures 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.

The Team is cross functional
• 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
• Demos work results to the Product Owner