Resources

In the second of this Use Cases in Practice series of blog articles, author Roly Stimson discusses how a use case model provides a simple, big, visible picture that provides critical value context, which represents a powerful tool that can be used as part of Scrum sprint reviews to ensure that the team and the stakeholders reflect meaningfully on what has been achieved in the context of the overall solution goals and value, and adjust future work objectives, priorities and plans accordingly.

In this first of a new series of blog articles, author Roly Stimson discusses how Use-Case slices are a simple but powerful technique to identify and prioritize small increments of releasable value and how these can be split (if and when needed) into smaller items that you can independently prioritize, schedule, build, test and demonstrate.

In the 6th blog of our series, Brian and Ian present the Contract Bridge game played with the Scrum Essential cards. The game is useful wherever there is a perceived boundary between a Scrum Team and its customers.

The way we develop software struggles to keep pace with changes in technology and business. Even with the rise of agile, people still flip-flop from one branded method to another, throwing away the good with the bad and behaving more like religious cultists than like scientists. This article explains why we need to break out of this repetitive dysfunctional behavior, and it introduces Essence, a new way of thinking that promises to free the practices from their method prisons and thus enable true learning organizations.

In the fifth blog post of this series, Brian Kerr and Ian Spence an experience report of a team learning and applying the Practice Mapping game. The power of this game is to see inside the mind of others and have useful discussions about the results.

As Agile Software Development practices become more and more popular both customers and suppliers are looking to find ways to have more agile contracts. Contracts that reflect and exploit the benefits of an agile way-of-working on both sides of the relationship. This hands-on workshop introduces and applies a number of simple but powerful tools to enable customers and suppliers to establish effective contracts that reflect their level of agility without constraining or compromising that of their partners.

In the fourth blog post of this series, Brian Kerr and Ian Spence provide directions to use the Scrum Essential Cards to play the Practice Mapping game. You can use this game to test the understanding of individuals or small groups, particularly as part of a training event.

In part three of this blog series, Brian Kerr and Ian Spence review how a team played the Practice Patience game. They had been a Scrum team for over 6 months and were used to holding more traditional open ‘brainstorming’ style of retrospectives. The article reviews their experience with the cards guiding them to improve their application of Scrum, including some quotes from their Scrum Master.

Ivar Jacobson International produced the cards in conjunction with Dr. Jeff Sutherland, the co-creator of Scrum - applying the Essence standard to build a helpful reference guide to the essential elements of Scrum. The cards make it easier to communicate with team members, improve team collaboration and provide better overviews.

So what does it mean for a Feature to be “Ready”? And just as importantly when do they need to be “Ready”?** Definition of Ready can be a dangerous thing leading to waterfall behavior and strict hand-overs between Product Owners and their teams. To help resolve these issues, IJI has developed a set of 6 mini-checklist cards that together define the lifecycle of a Feature to use when preparing features for PI Planning.