Back to Course
Agile Simulation Videos
0% Complete
0/0 Steps
-
Agile Simulation - Part 1 Meet the Agile Team
-
Agile Simulation - Part 2 Agile Lifecycle Overview
-
Agile Simulation - Part 3 Purpose, Agenda, Team Norms
-
Agile Simulation - Part 4 Visioning I
-
Agile Simulation - Part 5 Visioning II
-
Agile Simulation - Part 6 Stakeholder Analysis
-
Agile Simulation - Part 7 User Personas
-
Agile Simulation - Part 8 Use Case Diagrams
-
Agile Simulation - Part 9 Process Diagram and UI Flow
-
Agile Simulation - Part 10 Building the Backlog | Writing User Stories
-
Agile Simulation - Part 11 Story Slicing
-
Agile Simulation - Part 12 Non-Functional Foundation Stories
-
Agile Simulation - Part 13 Prioritization | Ranking
-
Agile Simulation - Part 14 Story Point Sizing
-
Agile Simulation - Part 15 Release Planning
-
Agile Simulation – Part 16 Iteration Pre- Planning | Backlog Refinement
-
Agile 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
-
Agile Simulation - Part 21 The Dysfunctional Daily Standup
-
Agile Simulation - Part 22 Demo
-
Agile Simulation - Part 23 Sprint Retrospective
Knowledge Checks
Lesson 19 of 23
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.