Articles and videos on creating and managing cross-functional Scrum teams: scrum master, product owner and development team.
Technical debt is a well-known concept in Agile software development. Technical Debt is defined as the eventual consequences of poor or evolving software architecture and software development within a codebase. In this blog post, Steve Blank discusses the concept of organizational debt.
Making decisions in groups like Scrum teams is our daily bread. Together we ponder over the right architecture, we select tools and set rules that we should follow as a software development team. In case of errors we discuss and decide how to get rid of them once and for all. We discuss, exchange point of views, bring arguments… or even yell at each other.
Agile is a now mainstream method used in IT project management. Yes, Agile and Scrum are now considered as a method and no longer as a philosophy. Everyone wants to “do” Agile and thus want to “be” Agile as well, but what are the common mistakes in applying Agile?
The basic rules of Agile project management frameworks like Scrum are deceptively simple. Drawing from his experience as an Agile coach, Jeff Campbell offers in his book “Actionable Agile Tools” some lightweight practices and tools that could help you to implement successfully an Agile approach.
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.
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.
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.
Scrum Expert Copyright © 2009-2025 Martinig & Associates