Introduction
A recent Twitter dialogue with @agileklzkittens sparked a crucial critique of Scrum, particularly focusing on its tendency to prioritize delivering 'visible value' in each sprint, a theme often reinforced in Sprint Reviews. @agileklzkittens pointed out, “Some kinds of work is just too big to fit into a two-week period and too atomic to be split up much less deliver visible 'value' at the end of a sprint.”
This observation highlights a trend that can inadvertently lead teams to prioritize user-facing features, potentially at the expense of crucial but less noticeable tasks, such as technical infrastructure enhancements. This skewed focus can result in compromised quality and usability.
In this article, I aim to address how to avoid this pitfall and clarify that Scrum is not solely about delivering what is immediately and visibly valuable to the user in a Sprint. My interpretation is that 'visible value' does not exclusively mean features that users directly perceive as valuable but encompasses a broader spectrum of product development.
Understanding Product Increments in Scrum In Scrum, product increments are essential steps toward the Product Goal. Each increment contributes to the product's development, whether it’s a visible user feature or an underlying technical improvement. A product increment must be usable and valuable.
A Spectrum of Valuable Increments in Scrum
Scrum has a spectrum of product increments, each holding its unique value and usability. Recognizing this variety is key to effective Scrum implementation. We can categorize these increments into at least three main types: Customer/Business Need Increments, Functional Increments, and Build to Learn Increments. It's important to note that all three categories involve building something tangible, allowing teams to empirically validate whether they are building the right thing and building it correctly. Let's delve into each of these types to understand their distinct roles and contributions.
Exploring the Three Main Types of Product Increments
1. Customer/Business Need Increments: Directly impactful features or enhancements for users, customers or business objectives.
Example: A feature in a job application system that allows users to track their application status.
2. Functional and Usable Increments: Components supporting overall product functionality, setting the stage for future developments.
Example: Implementing a CRUD (Create, Read, Update, Delete) split in the job application system, such as developing the 'Create' and 'Read' functionalities. While these may not provide full user value individually, they are vital for building a complete and functional system.
3. Build to Learn Increments: These increments are focused on exploration and learning and on actively building something for empirical validation. They include prototypes, mockups, and other experimental tools that are not intended for production use but are essential for validating ideas, concepts, or hypotheses in a tangible way. This approach goes beyond theoretical research by providing concrete evidence of the functionality, design, or user interaction.
Example: A prototype for the job application system’s user interface to test user interactions.
Introducing Learning Increments
Related yet slightly tangential, I propose that Scrum should evolve to include a new type of increment: the Learning Increment. A valid Sprint outcome could be solely focused on learning, such as conducting customer discovery interviews or observations. While Scrum generally emphasizes building towards 'done', this can sometimes lead to premature convergence on solutions. Learning Increments would validate the significance of exploration and understanding in product development, challenging the traditional focus on tangible product increments. For a deeper exploration of this concept and its potential impact on Scrum, read more in my article, ‘Escaping Scrum's Build Trap: Integrating Learning Increments’.
Conclusion: Crafting a Healthier Path in Scrum Development
Embracing a broader understanding of product increments in Scrum paves the way for a more nuanced and comprehensive approach to development. Recognizing the diverse contributions of various types of increments aligns Scrum teams more closely with the Agile principle of continuous learning and adaptation. This expanded perspective fosters a robust and holistic approach to product development and addresses critical challenges such as premature convergence on fragile features. It shifts the focus from the relentless pressure to deliver new, flashy features every sprint to a more balanced approach, emphasizing building a sustainable product and maintaining a healthy team dynamic. By valuing both the visible and foundational aspects of development, we can avoid sacrificing essential elements that ensure the product's and team's long-term success and resilience, leading to Bright Scrum and avoiding Dark Scrum.