Iterative vs. Incremental – What’s the Difference and Why Should You Care?

Agile is an incremental and iterative approach to delivering value to our customers. But too often we assume it’s really all about ways to slice work into smaller batch sizes and that both approaches are fundamentally equivalent. However, there is a crucial difference and this lack of awareness is a major contributor to projects and teams that are AINO (Agile In Name Only)!

In this session, we will discuss how to differentiate between incremental and iterative approaches, their strengths and weaknesses, and why you really need both. We will explore the many ways in which iteration shapes the core of Agile practices, how it supports and enables the benefits of agility, and how understanding its awesome power is a key step in moving from “doing” Agile to truly being agile. In addition, we will take a close look at the practical implications of when to use each approach by discussing real world scenarios, highlighting common Agile anti-patterns and (re)examining familiar story slicing patterns.

You will walk away with both a better understanding of one of the most important underlying principles of agility and immediately applicable insights for your daily work!

 
2 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/Structure of the Talk

Stage 1: Incremental, the Waterfall way

Why predictive approaches no longer work

Stage 2: Incremental, the Agile way

Signs you’re only halfway there

Iterations, learning, and testing riskiest assumptions

Stage 3: Iterative & Incremental

Agile as a way to manage uncertainty

Learning Outcome

- Appreciate the important differences between iterative and incremental aspects of Agile

- Understand how iteration is at the core of mastering agility

- Learn practical ways to take advantage of the strengths of each approach

Target Audience

Beginning and intermediate agilists who are interested in Agile's underlying principles and how to take their Agile implementation to the next level.

Prerequisites for Attendees

Some experience with Agile frameworks and mindset.

schedule Submitted 1 year ago

Public Feedback

comment Suggest improvements to the Speaker

  • Liked Ellen Grove
    keyboard_arrow_down

    Ellen Grove - Making our Mark: Drawing Together to Enhance Collaboration

    90 Mins
    Workshop
    Beginner

    Co-creating drawings helps teams enhance their systems thinking abilities by really seeing the big picture. A group of people talking around a whiteboard is an effective way to share ideas across a team. Imagine how much richer the conversation is when everyone on the team has a marker in their hand and is actively contributing! Graphic visualization is an important tool for talking about new ideas, generating insights and developing shared understanding. In a team context, drawing is a thinking tool rather than an artistic endeavour. When everyone participates in creating drawings, all team members can see how things fit together and what mental models are at play in defining the situation. And, by drawing together, the team is collaboratively creating meaningful records that are being validated and updated.

    Come along on a visual adventure into how teams can collaboratively visualize ideas and make sure that everyone at the table has a voice. In this workshop, we will warm up with some basic doodling skills practice. No drawing experience is required to take part in this session: if you can hold a marker, we can teach you the skills needed to put your ideas on paper. Together we'll consider the ways that collaborative drawing can be used to enhance group work, and we will share practical activities that you can take back to use with your team for setting the stage, gathering information, and sharing stories.

  • 90 Mins
    Workshop
    Advanced

    Abstract (280 chars)

    What if you could organize and motivate people to double their highest-expected productivity goals? Lessons from a large, distributed, volunteer group of online video gamers offer practical 21st-century guidance for your workplace. Even if you aren't a gamer. Or a space pirate.

    Abstract (full)

    What if you could gather and motivate people to double even their highest-expected productivity goal? What if you had no authority over those people -- if they were all volunteers?

    The future of leadership is emerging to guide 21st-century organizations beyond the small, cross-functional, green-field software development teams of the 1990s. Agile enterprises must respond to emerging markets, provide unity of purpose to workers with conflicting motivations, and foster order when change is the only constant. Agile leadership must cope with distributed teams, "gig economy," diverse skill-sets, and the impact to morale of unexpected changes. But the measure of success is still delivery to the market: volume, quality, reliability.

    Early in 2017, a group of several hundred independent players of the online futuristic video game Elite:Dangerous faced all the above organizational challenges yet still managed unprecedented delivery to their market. And they did it despite the "me first" culture of online games.We'll explore the structural, social, and cognitive factors which enabled this large distributed team of casual volunteers to deliver twice as much as their nearest competition. And we'll uncover how to amplify those factors in your own workplace.

    You'll learn the powerful effects of making individual contributions visible, expanding the scope of your regular team synchronizations, having a loose leadership hierarchy, and encouraging diffusion of innovation. And you'll see how community engagement is an essential quality of a servant leadership culture. This is a compelling story about leadership that's relatable to anyone regardless of their interest in or experience with Agile, online gaming, or space pirates.

  • 60 Mins
    Talk
    Intermediate

    Are you - or worse, your bosses - starting to doubt this Agile thing? Are your software teams proficiently delivering every two weeks and yet it just doesn't seem to make much of a difference to the bottom line?

    Most organizations begin their foray into Agile with software development and that makes sense - after all, the Agile Manifesto focuses on “working software.” Unfortunately, though, this is often also where the Agile journey comes to a grinding halt. Management confines Agile to a small box labeled “Delivery,” puts a lid on it, and everything else continues as usual. Development teams in such an environment may produce more software, faster and with better quality, but the expected impact on the organization often fails to materialize because the business value of the produced software doesn’t increase correspondingly.

    In this session, we’ll take a closer look at why Agile shouldn’t end with “working software.” The most commonly used Agile frameworks don’t provide much guidance on how to manage risk and ensure the creation of organizational value, so we will draw on insights, tools and techniques from other domains to identify crucial high risk assumptions, test our hypotheses, and measure outcomes. We’ll explore how we can get past the “feature factory” focus and apply the Agile mindset beyond delivery to produce better business outcomes and organizational impact.

  • Liked Martin Aziz
    keyboard_arrow_down

    Martin Aziz - "When do you need it by?" Business-Agility Metrics in an Agile World

    60 Mins
    Talk
    Intermediate

    “When will it be done?” is a question asked in just about every business I’ve encountered, Agile or otherwise. In this metrics-focused session we will explore why that question is so hard to answer and whether it is even the right question to ask.

    We will explore current thinking about measurement in knowledge work fields. How every business needs to identify their own appropriate metrics to measure for their own business challenges and goals. While metrics are always unique for each individual business context, we will identify 4 metric categories identified from the Fit for Purpose framework.

    To connect these concepts to your Agile organization we explore going past looking at measurement as a team phenomena and connect this to the level of services or value streams.

    Digging further we continue to examine questions around measuring and predicting delivery times. We contrast prediction approaches using deterministic methods vs probabilistic methods. And consider multiple sources of variability that make predictions challenging and often impossible.

    We conclude by considering more appropriate questions to replace “When will it be done?” Rather asking “When do we need it” followed by “and so, when should start?”

  • Liked Fernando Cuenca
    keyboard_arrow_down

    Fernando Cuenca - Visualizing Work: If you Can't See It, you Can't Manage It

    60 Mins
    Talk
    Intermediate

    Unlike a factory, where we can see work literally moving around, piling up waiting, being worked on, or even deteriorating with time, knowledge workers have to deal with abstract constructs that are largely invisible. Suddenly, answering questions like "what are we working on?" or "how does work get done here" can become tricky.

    The basic premise that the first step towards effectively managing knowledge work is to make it visible will not come as a surprise for anyone with some familiarity with Agile. That said, there's more to effective work visualization than a 3-column board showing "To Do | In Progress | Done" columns, and visualizing work items is only the first step.

    This session will explore approaches for visualizing otherwise invisible aspects of work, such as commitments, process, rules and, of course, work items, and using them to enable more effective management and collaboration.

  • Liked Dave Dame
    keyboard_arrow_down

    Dave Dame / Aaron Sampson, PMI-ACP, ITILv3, SMC - Your Proxy is Killing Your Product...One Delay at a Time

    90 Mins
    Workshop
    Beginner

    A supported Product Owner has the power to prioritize. An empowered Product Owner has the power to say 'No'!

    The Product Owner is the most underutilized and unsupported role in large organizations that are trying to increase their speed to market. Product Owners are only business people playing a 'weekend dad' to the team or they are merely only writing requirements for the team.

    Companies that are successful in delivering products to market empower the Product Owner. The Product Owner has one leg in Product Management and the other leg with the Scrum Team. The empowered Product Owner engages the business, customers, engineering, design, sales groups as stakeholders. They are empowered to optimize value by creating vision and context to enable teams to deliver products people want to buy and are technically sound to maintain and scale.

    In this workshop, we will help you unleash this opportunity and guide you in understanding the role of an empowered Product Owner.

  • Liked thomasjeffrey
    keyboard_arrow_down

    thomasjeffrey / Adeeb Dhanani - Creating Shared Understanding At High Complexity through Story Mapping, Spec By Example and Domain Driven Design

    90 Mins
    Workshop
    Advanced

    Shared understanding is a pre-requisite to success for any agile teams. Many Agile teams rely on User Stories to help them get consensus on what to deliver, and what done looks like. Stories are a great practice for agile teams, but as the complexity of the problem or solution they are building increases, they often need more. Agile teams can face serious churn in the story writing process as complexity increase. Different team members can have completely different understandings of the meaning of key business and solution concepts. Often the same concepts end up being discussed over and over again, significantly slowing down story exploration. Even worse, different stakeholders end up having ambiguous and even conflicting understanding of the solution.

    During this session, we will discuss how we have integrated story exploration practices such as Story Mapping, Story Grooming, and Spec by Example, with the Domain Driven Design method, with the goal to promote the creation of a ubiquitous language and share understanding of both the solution and business domain. We will show how various teams have leveraged light weight, informal tools to enable both technical and non technical stakeholders to execute in a highly aligned way, and dramatically decrease churn and rework as a result.

    A key part of this session will be taking the audience through an integrated example that show cases how one can elaborate on an idea through progressive refinement of Stories and CRC Card based domain driven models in parallel. We will showcase how Story Maps can be refined through creation of an initial Domain Driven Model expressed through Class Responsibility Cards. We will illustrate how to connect story grooming and refinement of domain models in order to create a precise business and solution language. We will illustrate how domain model walkthroughs can be used to battle test your stories against your domain model, validating key assumptions before coding starts. We will also showcase how both story grooming and domain driven design can be done directly in code, and how this approach dovetails perfectly into test driven development.

  • Liked Gil Broza
    keyboard_arrow_down

    Gil Broza - How to Make Real Collaboration Possible

    60 Mins
    Talk
    Intermediate

    Collaboration is generally considered a net positive, and everyone knows it’s a key principle of Agile. Yet most Agile teams -- even those that seem to work well together -- don’t collaborate nearly enough, and thus don’t reach their full potential. It takes attention and work to make collaboration possible, let alone appealing and practical! In this interactive talk, the author of “The Human Side of Agile” explains the not-so-short list of not-so-simple factors that get in the way of real collaboration, and provides a process for determining actions that will make collaboration possible.

  • Liked Gillian Lee
    keyboard_arrow_down

    Gillian Lee / Varun Vachhar - Agile Development with JavaScript

    60 Mins
    Talk
    Beginner

    How can we deliver value continuously when building modern JavaScript web applications? In the past 5-6 years, the popularity of JavaScript has exploded. There’s a good chance that you’re working at an organization where you’re using JavaScript.

    Learn about component-based architecture and approaches to state management that help us respond to changing requirements or even pivot in a new direction as a product evolves.

    What architecture choices and patterns enable meaningful independence and which ones hinder them?

    For all you non-developers out there, this is a fabulous opportunity to deepen your understanding of what choices your software development team may be making. Developers, here’s your chance to learn more about what Agile-friendly modern JavaScript development can look like.

    While some concepts are indeed language agnostic, this session will focus on the JavaScript ecosystem. We will cover the tools and techniques specific to component-based frameworks such as React, Vue, and Angular.

  • Liked Jochy Reyes
    keyboard_arrow_down

    Jochy Reyes - Cognitive Biases in Agile Teams

    Jochy Reyes
    Jochy Reyes
    Agile Coach
    ANZ
    schedule 1 year ago
    Sold Out!
    40 Mins
    Talk
    Beginner
    Cognitive biases often results to poor decisions that could affect your teams. This talk provides an introduction to cognitive biases and how they impact team performance and effectivity.
    I'll cover 3 aspects of teams that could be impacted by these cognitive biases - team dynamics, communication and productivity.
    I'll discuss the symptoms of these biases and show you how to proactively control and reduce its effects for more effective teams.
  • Liked Fernando Cuenca
    keyboard_arrow_down

    Fernando Cuenca - Agile beyond the Team: Creating a Context where Agile Teams can Thrive

    60 Mins
    Talk
    Intermediate

    Agile has now gone mainstream. Starting new and more Agile teams is relatively easy, but organizations then run into the challenge to orchestrate the work of multiple agile teams. Some have even observed that even though they manage to obtain better results from individual teams, if they step back and look at the larger picture, work still takes a long time to be delivered, quality expectations are not met, and teams experience considerable "friction" when they interact with their environment.

    This session is directed to those managers that operate above the team (middle-management, director level, etc.) and explores the concerns that need to be considered to create a context in which those Agile teams can thrive and realize the promise of high-performance.