The Real Value of Agile is Not in Delivery
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.
Outline/Structure of the Talk
- Introduction: Complicated vs. complex problems
- How waterfall mindsets constrain Agile
- Managing uncertainty
- Value-driven prioritization and the problem with identifying value
- Surfacing critical assumptions
- Hypothesis-Driven Development vs. the Feature Factory
- Closing the value loop
- Key points
- Explore how Lean Discovery and experimentation can expand the scope of Agile’s “inspect and adapt” learning loops beyond software delivery
- Identify and examine the riskiest assumptions with tools like Assumption Mapping and Impact Mapping
- Understand how to use the power of iteration and feedback to validate critical assumptions with testable hypotheses
Agilists, managers and other leaders who want to expand Agile beyond a narrow technical focus.
Prerequisites for Attendees
Some experience with Agile development/delivery and the interface with the rest of the organization.
schedule Submitted 1 year ago
People who liked this proposal, also liked:
Mathias Eifert - Iterative vs. Incremental – What’s the Difference and Why Should You Care?Mathias EifertAgile Pragmatist and Managing ConsultantExcella
schedule 2 years agoSold Out!
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!
Nicole Spence-Goon - Welcome to the Jungle: Where to begin in assessing Scrum TeamsNicole Spence-GoonAgile CoachExcella
schedule 1 year agoSold Out!
Picture it: you've been dropped like a paratrooper in the middle of a project jungle where the scrum teams are already full speed ahead in working their sprints, but it's more like the sprints are working them... to a slow death march. The never-ending barrage of user story questions is like a thick brush blocking the teams from reaching their goals. Plus, you've been given a "helpful" tip from an insider that some teams are "in need of discipline". How do you dig in and evaluate what's going on without creating more chaos?
In this session, we will discuss who and what to evaluate when making assessments of an Agile team's maturity.
Nicole Spence-Goon - Finding the OM in O & M: Prioritizing the dirty work of Operations & MaintenanceNicole Spence-GoonAgile CoachExcella
schedule 1 year agoSold Out!
Operations and Maintenance work is often seen as an unsexy, thankless job - but it has to be done. Since it's not hot, new development work, it ends up being placed on the back burner or thrown into a dark cave and not always considered as an area of work to apply agility. Sooner or later though, once the new software development work is done, everyone has to face these questions:
1) How do you manage the grunt work of keeping these systems operational and subsequent enhancements
2) How do you deal with system owners who all think their requests are the most important and
3) Is there a better way to handle all of this dirty work?
This session will show you how you can prioritize your O&M work – without the turf battles - when supporting multiple systems.