Agile for Teams : Practical, Hands-on Agile Training for the Whole Team
Who Should Attend/Prerequisites
This course is designed specifically for agile Team members - individuals and teams new to agile software development or individuals and teams that need to level-set terms, understand the principles that drive agile frameworks and create a common understanding of the roles, meetings, and artifacts that help make Teams successful.
Class Size Limit: 30 (Minimum 12)
Course Overview
Why should ScrumMasters and Product Owners get all the attention? Being a member of an agile Team is a challenging effort that requires special attention and training to be successful. This course focuses specifically on the team-based skills necessary to make the entire team a success. Make everyone around you better – learn how to be a great agile Team Member!
Course Objectives
- Achieve a deep understanding of agile values and principles
- Learn the fundamentals of selected agile frameworks including Scrum and eXtreme Programming
- Understand how the ScrumMaster and Product Owner serve the Team
- Learn communication and collaboration skills that enable high-performing teams
- Understand individual skills and contributions in a collaborative Team environment
- Learn how to become a cross-functional Team
- Learn about Team growth and maturity
- Understand how to write, groom, and estimate User Stories
- Use empirical feedback to achieve continuous improvement
- Discussion and practice in dealing with organizational challenges and impediments
- Learn how to work in a multi-team environment
- Understand the challenges of distributed Teams
- Build a definition of done that makes incremental delivery a reality
Agenda
Agile Values and PrinciplesProcess Control Models: Defined vs. Empirical Agile Manifesto Agile frameworks overview Origins and overview of Scrum ScrumMaster and Product OwnerThe ScrumMaster role What you should expect from your ScrumMaster The unique role of the Product Owner How the Product Owner drives the project What you should expect from your Product Owner
|
Sprint PlanningA practical and effective Sprint calendar Why Sprint Planning? How to plan a Sprint Using Task Packages The Sprint Backlog and Task Board Sprint Review and RetrospectiveCompare plan to result Show your work! The meaning of Continuous Improvement Team Members and the Retrospective Building a great Team Deciding what to do
|
The Team Member RoleTeam size and composition Team and Team Member accountability Team maturity and growth What does it mean to be a great Team Member? Scrum Meetings OverviewWhy meetings? Sprint Planning Daily Scrum Sprint Review Sprint Retrospective Story Time User Stories and the Product BacklogIntroduction to User Stories Three C's Grooming and splitting User Stories INVEST The Product Backlog in context SprintsWhat does "Potentially Shippable" mean? Why Potentially Shippable Defining "done" ScrummerFall and other maladies Technical Debt and how to pay it down Why Sprints? |
Tracking ProgressBurndown/burnup charts Be careful what you measure! Transparency and truthfulness Why track anything? CollaborationWhat is collaboration? Creative conflict is not confrontation! Communication bandwidth Effective workspaces Information radiators Enterprise AgilityAgile at scale How should we start? Scaling teams and roles Inter-team communication and collaboration Communities of Practice What great Teams need from the enterprise |
Cost:
$999 per attendee.