This event has been UPDATED since it was first published. View the UPDATED & Detailed Scrum Developer Training course for beginners Information here.

4 Weekends Scrum Developer Training is a 4 weekends long Instructor-led and guided training being delivered February 13, 2021 - March 7, 2021 US Pacific time taught over 16 hours, 2 sessions per weekend, 2 hours per session.

• This course is meant for beginners who would like to learn everything about Scrum.
• Instructor-led and guided training
• Practical Hands-On, Highly Interactive training
• This course will be taught in English language
• All Published Ticket Prices are in US Dollars

4 Weekends Only Scrum Developer Training Course Schedule

• February 13, 2021 - March 7, 2021 US Pacific time
• 4 Weekends | 2 Hours on Saturdays, 2 Hours on Sundays every weekend US Pacific time
• 7:30 AM - 9:30 AM US Pacific time each of those days
• Please click here to add your city name and check your local date and time for the first session to be held on February 13, 2021 at 7:30 AM US Pacific Time.

Features and Benefits

• 4 weekends, 8 sessions, 16 hours of total Instructor-led and guided training
• Training material, instructor handouts and access to useful resources on the cloud provided
• Practical Hands-on and highly interactive training
• Real-life Scenarios

Course Objectives

• To ensure that students understand the basics of Scrum
• To enable Scrum Team members to effectively contribute to a Scrum project.
• To enable Scrum Team members to apply Scrum effectively in Scrum/Agile projects.

Audience Profile

This is highly recommended for everyone in a company who works in a Scrum Team or anyone who interacts with any Scrum Team. This will also be very useful for those who are interested in understanding the basics of Scrum and how this method could be used effectively.

Prerequisites

There is no formal prerequisite for this certification.

Course Outline

1. Introduction

• Scrum Overview
• Scrum Principles
• Scrum Aspects
• Scrum Processes
• Scrum Summary
• Scrum Advantages

2. Organization

• Core Roles- Product Owner, Scrum Master, Scrum Team
• Non-core Roles

3. Business Justification

• Responsibilities of Scrum Roles in Business Justification
• Factors used to Determine Business Justification
• Business Justification Evaluation Techniques
• Tools for Planning Value
• Continuous Value Justification
• Summary of Responsibilities

4. Quality

• Quality Defined
• Acceptance Criteria and the Prioritized Product Backlog
• Quality Management in Scrum
• Quality Planning
• Continuous Integration and Sustainable Pace
• Quality Control and Quality Assurance
• Summary of Responsibilities

5. Change

• Unapproved and Approved Change Requests
• Change in Scrum
• Balancing Flexibility and Stability
• Achieving Flexibility
• Changes to a Sprint
• Impact of Expected Change on the Length of Sprint
• Managing Changes through Prioritized Product Backlog Grooming
• Managing Changes During Demonstrate and Validate Sprint

6. Risk

• What is Risk?
• Risks and Issues
• Risk Management Procedure
• Risk Identification
• Risk Assessment
• Risk Assessment Techniques:
• Risk Mitigation
• Risk Communication
• Minimizing Risks through Scrum
• Summary of Responsibilities

7. Introduction to Scrum Project Phases

8. Initiate Phase

• Process 1: Create Project Vision
• Process 2: Identify Scrum Master and Stakeholder(s)
• Process 3: Form Scrum Team
• Process 4: Develop Epic(s)
• Process 5: Create Prioritized Product Backlog
• Process 6: Conduct Release Planning

9. Plan and Estimate Phase

• Process 1: Create User Stories
• Process 2: Approve, Estimate, and Commit User Stories
• Process 3: Create Tasks
• Process 4: Estimate Tasks
• Process 5: Create Sprint Backlog

10: Implement Phase

• Process 1: Create Deliverables
• Process 2: Conduct Daily Standup
• Process 3: Groom Prioritized Product Backlog

11. Review and Retrospect Phase

• Process 1: Convene Scrum of Scrums
• Process 2: Demonstrate and Validate Sprint
• Process 3: Retrospect Sprint

12. Release Phase

• Process 1: Ship Deliverables
• Process 2: Retrospect Project

13: Scaling Scrum

• Scalability of Scrum
• Transition to Scrum
• Resistance to Change
• Mapping Traditional Roles to Scrum
• Importance of Executive Support