Software Practices (SCRUM): SCRUM Roles

Course Overview

Scrum is Agile development methodology, and so follows the Agile Manifesto. The Agile Manifesto sets out standards for software design practices that focus on completing and shipping code without some of the overhead and complication associated with traditional software development. In this course, you'll learn about the guiding principles of Scrum, an overview of the process, the makeup of a Scrum team, Scrum artifacts, and the INVEST guidelines.

Target Audience

Software development managers looking to implement Scrum, or software developers looking to work on a Scrum team

Learning Objectives

• describe the Agile Manifesto
• list the 12 principles behind the Agile Manifesto
• describe the Scrum framework
• use the five Scrum values to build a foundation for teamwork and continuous improvement for a team
• describe how inspection, adaptation, and transparency can improve how people work together toward common goals
• describe how the Product Increment is developed throughout the lifecycle of your project
• use the Scrum values and rules to assist the Scrum Master, team members, and stakeholders to protect the Sprints
• use the roadmap release schedule to determine the end of a Scrum project
• list the three core roles defined in the Scrum framework
• define the two types of project members and the rules they must obey in Scrum development
• describe the key Product Owner role in a Scrum software development team
• describe the Scrum Master role in a Scrum software development team
• describe the role of a Scrum Team within a Scrum software development team
• describe the Project Manager's role responsibilities required by the Scrum environment
• describe best practices when assigning Scrum roles
• describe the four Scrum artifacts and their role in the context of the Scrum Team and Scrum Theory
• describe the Product Backlog
• use SPIKEs to discover more information in order to resolve an issue
• describe how User Stories are defined, constructed, prioritized, and groomed for inclusion into the Sprint Backlog during Sprint Planning
• identify fat Product Backlog items (PBIs) that require splitting into smaller User Stories in a Scrum project
• describe the Scrum Sprint Backlog
• describe the Scrum Sprint Burn Down Chart
• describe the Scrum Product Increment
• describe the independence criterion in the INVEST guidelines
• describe the negotiable criterion in the INVEST guidelines
• describe the valuable criterion in the INVEST guidelines
• describe the estimable criterion in the INVEST guidelines
• describe the small criterion in the INVEST guidelines
• describe the testable criterion in the INVEST guidelines