Back to Course
Agile Manager Learning Path
0% Complete
0/0 Steps
-
Week 1 - Intro to Agile and Scrum
Scrum 101 - Part 1 | Scrum Basics -
Scrum 101 - Part 2 | The Scrum Process
-
Scrum 101 – Part 3 | Scrum Values
-
Scrum 101 - Part 4 | Scrum Terms Review
-
Webinar - Thinking of Agile Adoption? Start HERE
-
Webinar - A Journey Through the Agile Lifecycle
-
Week 2 - Agile Team Roles and ExpectationsAgile Team – Part 1 – Team Characteristics
-
Agile Team – Part 2 – The Leadership Triangle
-
Agile Team – Part 3 – The Product Owner Role
-
Agile Team – Part 4 – The ScrumMaster Role
-
Agile Team – Part 5 – The Team
-
Agile Team – Part 6 – Technical Leadership
-
Agile Team – Part 7 – Agile Coach
-
Agile Team – Part 8 – Generalizing Specialist
-
Agile Team – Part 9 – The Agile Business Analyst (BA)
-
Agile Team – Part 10 – The Agile Developer
-
Agile Team – Part 11 – The Agile Tester
-
Agile Team – Part 12 – Agile Sponsors & Stakeholders
-
Agile Team – Part 14 – Real World Agile Role Challenges
-
Agile Team – Part 15 – The Agile Team Space
-
Agile Team – Part 16 – Agile Software Tools
-
Agile Managers - We’ve disrupted your role
-
Week 3 - Agile Leadership & High Performing TeamsHigh Performing Teams – Part 1 – Foundations of High Performing Teams
-
High Performing Teams – Part 2 – Team Maturity Stages
-
High Performing Teams – Part 3 – Servant Leadership
-
High Performing Teams – Part 4 – Shifting Towards Servant Leadership
-
High Performing Teams – Part 5 – Self-Organizing Teams
-
High Performing Teams – Part 6 – Understanding Team Motivators
-
High Performing Teams – Part 7 – Team Forming Stage
-
High Performing Teams – Part 8 – Team Norms & Agreements
-
High Performing Teams – Part 9 – Team Storming Stage
-
High Performing Teams – Part 10 – One-on-One Coaching Tips
-
High Performing Teams – Part 11 – Emotional Intelligence
-
High Performing Teams – Part 12 – Correcting Dysfunctional Team Member Behavior
-
High Performing Teams – Part 13 – Resolving One-on-One Conflict
-
Webinar - Adaptive Leadership Journey
-
Week 4 - Release Planning & Cross-Team PI PlanningAgile Simulation - Part 15 Release Planning
-
Agile Simulation – Part 16 Iteration Pre- Planning | Backlog Refinement
-
Release Planning Meeting – Part 9 – Facilitating the Top 10 Agile Meetings
-
Release Planning Meeting Real World Tips – Part 10 – Facilitating the Top 10 Agile Meetings
-
Iteration Zero Planning Meeting – Part 13 – Facilitating the Top 10 Agile Meetings
-
PI Planning - Feature Readiness
-
PI Planning - Backlog, Alignment and Event Space Readiness
-
PI Planning - Keeping the Program Board Active
-
PI Planning - Anti-Patterns and Positive Patterns
-
Preparing for PI Execution
-
Week 5 - Backlog Management, Prioritization and EstimationAgile Simulation - Part 10 Building the Backlog | Writing User Stories
-
Agile Simulation - Part 11 Story Slicing
-
Agile Simulation - Part 13 Prioritization | Ranking
-
Backlog/Story Writing Meeting – Part 6 – Facilitating the Top 10 Agile Meetings
-
Story Writing Meeting Real World Tips – Part 7 – Facilitating the Top 10 Agile Meetings
-
Estimation & Planning Overview
-
Agile Simulation - Part 14 Story Point Sizing
-
Release Planning Rapid Sizing Method – Part 11 – Facilitating the Top 10 Agile Meetings
-
Release Planning Story Sizing Demo – Part 12 – Facilitating the Top 10 Agile Meetings
-
Webinar - Agile Estimating and Planning
-
Week 6 - Iteration Execution & CeremoniesAgile Simulation - Part 17 Sprint Planning Meeting
-
Agile Simulation - Part 18 Mid Iteration Activities
-
Agile Simulation - Part 19 Team Interruption During Iteration
-
Agile Simulation - Part 20 Conflict Management Using Team Norms
-
Iteration Planning Meeting – Part 15 – Facilitating the Top 10 Agile Meetings
-
Daily Standup Meeting – Part 16 – Facilitating the Top 10 Agile Meetings
-
Daily Standup Meeting Real World Tips – Part 17 – Facilitating the Top 10 Agile Meetings
-
Agile Simulation - Part 21 The Dysfunctional Daily Standup
-
Agile Simulation - Part 22 Demo
-
Sprint Review Meeting Demo – Part 19 – Facilitating the Top 10 Agile Meetings
-
Sprint Retrospective Meeting – Part 20 – Facilitating the Top 10 Agile Meetings
-
Week 7 - Technical AgilityWhat is Technical Agility
-
Tech Lead Role on the Team - Part 1
-
Tech Lead Role on the Team - Part 2
-
Technical Excellence
-
Agile Managers & Technical Excellence
-
What DevOps Really Means
-
Unlock Team Potential with DevOps - Daniel Gruesso
-
DevOps Radar Assessment Overview
-
The 3 Elements of Quality
-
Creativity & Innovation
-
Week 8 - Team Metrics & GrowthTeamHealth Radar Explainer
-
Top Challenges with Measuring Team Health
-
Using TeamHealth Radar as a Scrum Master
-
TeamHealth and Performance Metrics - Case Study
-
Evolving a Continuous Improvement System - Case Study
-
Program Level Standard Metrics
-
How Healthy Is Your Agile Team?
-
Week 9 - Intro to KanbanIntroduction to Kanban
-
Visualize Your Workflow
-
Limit Your Work In Process (WIP)
-
Measure and Optimize Flow
-
Make Process Policies Explicit
-
Implement Feedback Loops
-
Eliminate Blockers
-
Improve Collaboratively and Evolve Experimentally
-
Setting Up Your Kanban Board
-
Value Stream Board
-
Portfolio Kanban
-
ScrumBan
-
Sample Kanban Board: Reports Team
-
Sample Kanban Board: Marketing Team
-
Sample Kanban Board: Support Team
-
Sample Kanban Board: Claims Management Board
Lesson 59 of 100
In Progress
Agile Simulation – Part 19 Team Interruption During Iteration
Watch as the team gets interrupted during the middle of the Iteration and how the Scrum Master reacts! A Sponsor/VP walks in and has a ‘quick fix for a report’ she wants done. Since she needed this done quickly, Kellie, our ScrumMaster gently reminded her of the team rules and suggested finding another team or person who can complete the new story. Another popular approach is to add the item to the backlog and have the Product Owner prioritize it and decide when the team should pull it.
Responses
You must be logged in to post a comment.
But what to do if the security guy or any other guy can’t help either?
This is an excellent question! Ultimately, the decision is left to the Stakeholder to decide after the Scrum Master has exhausted all alternative resources. The Stakeholder may determine the new item is a higher priority than the previously agreed upon work and understand a story may not be complete as originally planned.