The Professional Scrum with Kanban (PSK)
course has now been out for more than 6 months at Scrum.org. As one of
the first few trainers who wanted to teach this course when it came
out, I find that it is a great way to combine the Scrum framework with
Kanban as a strategy to deliver value to your customer.
of the many topics that we talk about in this class, I’ve found that
the use of throughput instead of velocity/capacity to be a positive
change. I’ve taught the regular Professional Scrum Master (PSM) course
for about 6 years now and when I get to the Sprint Planning slides, we
usually extend the conversation around velocity and capacity. I pull up
my complementary slide deck around relative estimation, poker planning,
charts to track velocity and we spend an additional hour on this topic. I
answer questions around the meaning of story points, how they should be
understood, tracked and used in multi-team Agile project.
the PSK class, this conversation is completely different. When I get to
the Sprint Planning slides, I point out that the throughput history is
used as an input to the Sprint Planning. With a few examples, I show how
easy it can be to get from your electronic Agile tracking system (Ex:
Jira) or on your physical Kanban board.
then get a new set of questions from students which I find a lot more
interesting. The conversation goes quickly around the variation in the
size of the Product Backlog Items (PBIs) that are taken by the team at
Sprint Planning. I can also tie it back to Little’s Law where limiting
work in progress will increase throughput, thus helping students see
throughput linked to limiting work in progress. There are very few
questions around understanding throughput. Students find it is a metric
that makes sense to the business compared to story points.
While our industry has talked about poker planning
and story points since almost the beginning of agility in 2001, I think
it is more than time that the conversation at Sprint Planning shifts to
historical throughput instead of using velocity. Maybe one day in the
software engineering museum, we can see a deck of poker planning cards
next to a set of punch cards.
Practicing Hypothesis-Driven Developmentis thinking about the development of new ideas, products and services – even organizational change – as a series of experiments to determine whether an expected outcome will be achieved. The process is iterated upon until a desirable outcome is obtained or the idea is determined to be not viable.
But what is the Scrum methodology, and how does it work? This introduction to Scrum PPT will explore just that. Whether you’re a manager, programmer, tester, product owner, or just want to improve product delivery, check out these Scrum presentations by Certified Scrum Trainer and author Mike Cohn of Mountain Goat Software. Source: https://www.mountaingoatsoftware.com/presentations/an-introduction-to-scrum