Understanding the Relationship of Optimization, Prioritization, Throughput, Impediments, Métier, Utilization, and Sizing
Some of the key aspects of successful Agility are slicing our work into small chunks, prioritizing this work, and having our people pull the work at a rate they can sustain. How do we do that? What does limiting work in progress mean? Is it more beneficial to have people working across stories individually or swarming on stories? What is the effect when specialists have to work on specific stories due to their unique skill sets? Why do we slice stories? When we choose to not have people remove impediments, what impact can that have?
This session will immerse you in a simulation of what a team goes through when pulling work in an iterative approach such as XP or Scrum. It was created in response to seeing teams make poor choices in what they optimizing; often choosing to optimize the utilization of resources as opposed to maximizing the effectiveness of the people. This team also had chosen an architecture where specialized talent was hard to come by, limiting the overall effectiveness.
We'll explore what prioritization does for us; how limiting work in progress and slicing stories helps in getting us to done. We'll introduce impediments and make choices whether to work on something else or work to remove them. We'll introduce a specialist and see what the impact of that is.