Certified Scrum Master Workshop

Transcription

1 Learn, understand, and execute on the three overarching principles behind Scrum: iterative development, selfmanagement, and visibility. 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. 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. Who Should Attend 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 Anyone wishing to learn more about Scrum is welcome to attend, and please note: registrants of this course do NOT need to have substantial experience working in an Agile environment but it does

2 Course Objectives Details on Scrum roles: Team Member, Product Owner, ScrumMaster Foundational/critical concepts of Scrum with our Certified Scrum Trainer instructional program; How to apply empirical thinking to your project work; How a team's productivity can be adjusted to account for its composition; Importance of organizational agreement on software readiness; Why the ScrumMaster role can be the most satisfying as well as the most difficult job on a project; Conflict resolution's critical role in Scrum; Work on a real-world Scrum project live in the classroom; Learn, practice, and utilize the Scrum Framework; Knowing when software is "Done" under Scrum; Critical characteristics a ScrumMaster must have to succeed; Get to the heart of the matter with Scrum, coaching, and team productivity; Compare traditional and Agile project estimating and planning; Conduct decomposition to estimate a Scrum project; Practice Scrum meetings including: Sprint planning, Daily Scrum, Burndowns, Sprint review, and Sprint retrospective; Achieve the first step in Scrum Alliance -recognized certifications, enabling you to advance to higher levels of recognition; A framework to operate large projects using Scrum; How to maximize your returns using Scrum; Course Outline 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 Management

3 The Scrum Framework The Different Scrum Roles Chickens and Pigs Iterative Development vs. Waterfall Self-Management Concepts Full Disclosure and Visibility The Scrum Framework Overview Implementation Considerations Traditional vs. Agile Methods Overview Scrum: The Silver Bullet The Agile Skeleton A Scrum Launch Checklist Scrum Roles The Team Member The Product Owner The Scrum Master 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 Outsourcing

4 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? The Product Owner: Extracting Value The Priority Guide Product Backlog Refactoring Productivity Drag Factors Fixed Price/Date Contracts Release Management Earned Value Management 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 Sense

5 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 Tools 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