This talk is a study of a case in which three Scrum teams converged into a single large team Kanban system design. Working in separate teams resulted in issues with responsibility, hand-overs, resource utilization and a culture of blaming others. In a large, highly self-organized team the members could share responsibility for the whole, work on the right things and focus on flow.
Using Story points is a technique used by Scrum team to evaluate the relative size of user stories. If this technique works fine for single teams, it might be more problematic when multiple teams are involved. In this article, Paul Raymond explains why user story normalization is needed in contexts where multiple Scrum teams cooperate on the same user stories.
One of the important concept around Agile and Scrum is that it is more important to build the right product than to build the product right. Impact Management is a framework that helps managers to focus on impact of an idea and a product. In her article “Impact-Driven Scrum Delivery”, Ingrid Domingues explains how to brings together Scrum and Impact Management in software development projects where design is important.
Most agile software development team grapple with user stories as a technique for understanding what needs to be developed iteratively. This talk presents some techniques for uncovering useful user stories and how to slice them in a way to deliver value in small increments.
The ScrumMaster is a key element of the Scrum teams that need such a role for facilitating their work. In his book “Scrum Shortcuts without Cutting Corners”, Ilan Goldstein discusses the question if a ScrumMaster can be member of multiple Scrum teams.
Integrating UX into an Agile process is not always an easy challenge. In this article, Mike Bulajewski reminds the why the differences between the two vision exist in the first place and proposes some solutions on how they could be solved. This article provides a very interesting point of view of the Agile-UX relationship from the UX side.
We’ve all been there. You release a new feature, product or service, only to find it isn’t quite what your customers want or need. But by the time you release, it’s too late to make significant changes. Traditionally user experience design has involved a significant amount of upfront user research and design, to ensure we build products that meet customer needs. But this approach doesn’t always work so well within an Agile development environment.
Scrum Expert Copyright © 2009-2024 Martinig & Associates