Scrum Master Certification
9/10/2020 - 9/11/2020COURSE LENGTH:
9:00am - 4:30pm
Even projects that have solid, well-defined project plans encounter some degree of change and waste. Shifting market conditions, budget cuts, staff restructuring, or any number of influences will disrupt the best plan while contributing to customer dissatisfaction and staff discouragement. Moreover, projects that begin with changing or unclear requirements make it difficult to even establish project expectations.
AUDIENCE AND PREREQUISITES
Scrum is the agile development process that allows teams to deliver usable software periodically throughout the life of the project, absorbing change and new requirements as the project proceeds.
Beginning with the history of agile development and moving through the disciplines promoted by Scrum, you will gain a comprehensive understanding of the Scrum methodology while specifically reviewing the behaviors expected of a ScrumMaster.
Those practicing or looking to practice the art of the ScrumMaster or anyone involved in Scrum (managers, team members, product managers, etc.)
Team members not certified, including business customers, users, or partners, product owners, team members, acting ScrumMasters who are not certified
Those interested in becoming Scrum certified, including project managers, leads, or sponsors, IT managers/directors, business analysts, developers/programmers
This course qualifies you for the following PMIŽ Professional Development Units (PDUs):
Leadership = 2
Strategic and Business Management = 2
Technical Project Management = 11
Course Cost does not include the cost of the courseware or exam. This course is subject to a minimum enrollment to run. This course may run as a virtual instructor led course if the course has not met the minimum enrollment. For more information, please contact 207-775-0244 or email: email@example.com
1. Agile Thinking How Manufacturing has Influenced Software Development The Origins of Agile Thinking The Agile Manifesto The Complexity of Projects Theoretical vs. Empirical Processes Overview The "Iron Triangle" of Project Management2. The Scrum Framework The Different Scrum Roles Chickens and Pigs Iterative Development vs. Waterfall Self-Management Concepts Full Disclosure and Visibility The Scrum Framework Overview3. Implementation Considerations Traditional vs. Agile Methods Overview Scrum: The Silver Bullet The Agile Skeleton A Scrum Launch Checklist4. Scrum Roles The Team Member The Product Owner The Scrum Master5. The Scrum Team Explored The Agile Heart Bruce Tuckman's Team Life Cycle Patrick Lencioni's Five Dysfunctions of a Team Team Ground Rules Getting Human Resources Involved The Impact of Project Switching The MetaScrum The Scrum of Scrums The Importance of knowing When Software Is "Done" Internal Outsourcing6. Agile Estimating and Planning Product Backlog Features Relative Weighted Prioritization Prioritizing Our Time User Stories Relative Effort Velocity Planning Poker and Story Points Ideal Team Days Team Capacity Projecting a Schedule Why Plan in an Agile Environment?7. The Product Owner: Extracting Value The Priority Guide Product Backlog Refactoring Productivity Drag Factors Fixed Price/Date Contracts Release Management Earned Value Management8. The ScrumMaster Explored The ScrumMaster Aura Characteristics of a ScrumMaster Candidate The Difficulties of Being a ScrumMaster A Day in the Life of a ScrumMaster The Importance of Listening Common Sense9. Meetings and Artifacts Reference Material A Chart of Scrum Meetings The Product Backlog Sprint Planning The Sprint Backlog The Sprint The Daily Scrum The Sprint Demo/Review Why Plan? The Ideal Team Day Scrum Tools10. Advanced Considerations and Reference Material Conflict Management Different Types of Sprints The ScrumMaster of the Scrum-of-Scrums Metrics Dispersed Teams Scaling Developing Architecture Stage Gate/Milestone Driven Development Inter- and Intra-Project Dependencies Task Boards, Project Boards Scrum and CMM, "Traditional" XP