67. If they haven’t already, they determine their capacity and, based on the priorities, commit to a set of work.
68. This means that a team may have capacity to do work, but may not get to it in a release if that work pushes the operation team beyond its capacity.
69.
70. We attempt to manage this through classes of service. We borrow a concept from Kanban that says similar projects are grouped into classes and each class is assigned an allocation.
96. So, over time, an estimate of completion time for items of a given size should become more accurate.
97. We have eliminated planning poker. Work items are just sized as smalls or mediums and the average cycle times for those sizes from the last release become the estimate for the upcoming release.
98.
99.
100. More importantly, testing used to take 6 weeks. Now it takes 1 week. Testing used to be 50% of the release cycle, but now is just 20%.
101. We have a better picture of our release at any given moment