What Was Rally Thinking?

Agile Bites

#Tech #Integrity Inspired Solutions

24:35

It’s the very first episode of The Big Pitch with Jimmy Carr and our first guest is Phil Wang! And Phil’s subgenre is…This Place is Evil. We’re talking psychological torture, we’re talking gory death scenes, we’re talking Lorraine Kelly?! The Big Pitch with Jimmy Carr is a brand new comedy podcast where each week a different celebrity guest pitches an idea for a film based on one of the SUPER niche sub-genres on Netflix. From ‘Steamy Crime Movies from the 1970s’ to ‘Australian Dysfunctional Family Comedies Starring A Strong Female Lead’, our celebrity guests will pitch their wacky plot, their dream cast, the marketing stunts, and everything in between. By the end of every episode, Jimmy Carr, Comedian by night / “Netflix Executive” by day, will decide whether the pitch is greenlit or condemned to development hell! Listen on all podcast platforms and watch on the Netflix Is A Joke YouTube Channel . The Big Pitch is a co-production by Netflix and BBC Studios Audio. Jimmy Carr is an award-winning stand-up comedian and writer, touring his brand-new show JIMMY CARR: LAUGHS FUNNY throughout the USA from May to November this year, as well as across the UK and Europe, before hitting Australia and New Zealand in early 2026. All info and tickets for the tour are available at JIMMYCARR.COM Production Coordinator: Becky Carewe-Jeffries Production Manager: Mabel Finnegan-Wright Editor: Stuart Reid Producer: Pete Strauss Executive Producer: Richard Morris Executive Producers for Netflix: Kathryn Huyghue, Erica Brady, and David Markowitz Set Design: Helen Coyston Studios: Tower Bridge Studios Make Up: Samantha Coughlan Cameras: Daniel Spencer Sound: Charlie Emery Branding: Tim Lane Photography: James Hole…

about a year ago 22:20

MP3•Episode home

If we had a dollar for every piece of “authoritative Agile advice” out there, let's just say that we'd have a lot of money.

Sharing the successes, failures, and lessons learned is so valuable to all of us on an Agile journey. But it's important to keep your filter up for not only false information, but also true information that doesn't fit your situation.

In this episode, Host Phil Ledgerwood dissects some “authoritative” facts and figures about so-called “full Scrum” vs. “lightweight Scrum” to demonstrate how easy it can be to fall into the trap of misleading Agile guidance.

The lesson here? Don’t blindly accept what anyone says, no matter the source (even this podcast!). Always investigate, weigh it carefully, and experiment for yourself.

93 episodes

Agile Bites

What Was Rally Thinking?

Agile Bites

published about a year ago

MP3•Episode home

If we had a dollar for every piece of “authoritative Agile advice” out there, let's just say that we'd have a lot of money.

The lesson here? Don’t blindly accept what anyone says, no matter the source (even this podcast!). Always investigate, weigh it carefully, and experiment for yourself.

93 episodes

#Tech #Integrity Inspired Solutions

All episodes

Agile Bites

1
Limiting Your WIP 25:57

49 weeks ago25:57

25:57

In our previous episode, we talked about the importance of visualizing your current work-in-progress to uncover bottlenecks, enhance decision-making, and provide clarity on your team's workload. Now, let's tackle what often comes next: realizing you have too much work in progress. Why does this happen so often to development teams, and what can we do about it? In this episode, we're diving into strategies to manage and prevent this overload. We’ll cover setting WIP limits, staying responsive, and juggling organizational demands effectively. Tune in to hear how to avoid overcommitting, the perks of prioritizing and finishing tasks before jumping into new ones, and how to use Lean principles to keep your workflow sustainable.…

Agile Bites

1
Visualizing Your WIP 23:32

50 weeks ago23:32

23:32

When the kind of work we do is invisible (like software development), it can be a challenge to keep track of what work is going on at any given time. That's where visualization can be a great tool for understanding your team's work in progress. Building on last episode's discussion on creating workflow visualizations, in this episode, host Phil Ledgerwood explores the importance of visualizing work in progress to uncover current projects in flight and find hidden bottlenecks and inefficiencies. I discuss the pros and cons of common WIP visualizations (lists, Kanban boards, etc.) so that you can decide on a visualization that fits your unique workflow, even if it means thinking outside the box.…

Agile Bites

1
Agile Team Management and Visualization (It's Not What You Think) 17:42

51 weeks ago17:42

17:42

A lot of what we do in software development is invisible. If someone is typing furiously on their keyboard, you don't know if they're about to finish that new feature or if they're complaining to their state representative. One of the things that tends to be invisible is the actual process of getting something from “request” to “deliverable.” Everybody kind of knows what that process is, but they typically only know their piece of it, and they probably haven't thought critically about it in years. Creating a visualization of this process can: Spotlight potential weak points Improve communication Reveal the complexities of your team's workflow Uncover hidden opportunities for optimization In this episode I'm sharing practical tips for mapping out your processes, understanding team dynamics, and setting the stage for continuous improvement.…

Agile Bites

1
Day One of Managing Agile Teams 25:36

52 weeks ago25:36

25:36

When managing a new team, it's tempting to come in guns blazing with new ideas and changes. Not only can this cause resistance, however, but you might be heading the wrong direction to begin with. Start with Fact-Finding and Reason-Finding before Recommendation-Making. In other words, one of your first moves should be to ask a lot of questions—"why" being one of the most prominent of them. This sets you up for success with your team because: You may discover there are good reasons for their current practices that are not immediately apparent to you It lays the foundation for future discussions, focusing on the reasons behind the practices rather than the practices themselves—making the conversation ego-agnostic. In this episode, learn how to create a safe environment to gear up your operations for change and set you and your team up for future success.…

Agile Bites

1
How To Manage Software Teams - Fundamentals 20:34

1 year ago20:34

20:34

Many of us who were thrown into management positions over development teams had to learn on the job. And when that happens, it can be easy to fall into the role of what you THINK a manager should do—be the rule enforcer and hold the team accountable. But as a dev team manager, your primary role should be to enable your team to deliver value effectively and efficiently. In other words, get out of your team's way and empower them to do their best work. How does this actually play out, though? In this episode, I'm sharing the lessons I've learned and things I wish I had understood when I first started managing dev teams. Whether you're a new manager or a seasoned veteran, this episode provides practical tips for keeping you and your team on the same side working towards a common goal.…

Agile Bites

1
Secret Management Hacks to Faster Delivery 25:04

1 year ago25:04

25:04

If you're a CTO, manager, or team lead looking to develop software faster, this episode is for you! If someone has told you that you shouldn't -want- to shorten time to delivery, this episode is also for you. Because they're wrong. Wanting speed isn't a bad thing—assuming you are building the right thing (which is the main problem Agile addresses). As teams do grow in their agility, they do tend to become faster for all kinds of reasons—but it's not directly because of Agile. Speed isn't the goal of Agile. Making sure the right software comes out the door is. But there are definitely process improvements you can make that can also increase your speed of delivery, and you should want that. In our most click-baity titled episode yet, I talk about the actual things that are influencing your rate of delivery and how to deal with them.…

Agile Bites

1
Why Are You Doing This? 20:40

1 year ago20:40

20:40

Have you stopped and asked yourself and your organization, “Why are we doing this?” You may or may not be surprised to find out that a lot of organizations make decisions, choose frameworks, and prioritize projects simply because of inertia and not because there's a real reason behind it. Why would you put time and resources into maintaining structures whose reasons have been lost to antiquity or never existed in the first place? It seems like common sense to individuals, but that often doesn't translate on the organizational level. This episode delves into the importance of understanding the reasons behind technical decisions and the pitfalls of following practices or working on projects without understanding their original purpose or questioning their current relevance. Defining the ‘why’ helps ensure that actions are not only based on historical momentum but are relevant, justified, and beneficial in their current context.…

Agile Bites

1
Hey Managers - Is Agile a Scam? 22:26

1 year ago22:26

22:26

Hey managers, let's talk straight: Is Agile a scam? In your context, it just might be. Agile has become the default for teams, but do you truly understand WHY you're using it or if you even need it? In this episode, we're stripping away the Agile buzzwords, getting back to basics, and exploring the essence of Agile from a manager's perspective. Forget sprints and user stories—Agile is all about responsiveness to change. By starting with this fundamental principle, you can avoid getting tangled in specific practices or frameworks that don't fit your organization.…

Agile Bites

1
Slicing Stories Vertically vs. Horizontally 18:23

1 year ago18:23

18:23

Should we be slicing stories vertically or horizontally? Does it even matter? Should we organize the requirements in our user stories by architectural layers or by small units of functionality? Both approaches divide the work up into smaller batches, but what good are pieces of software if they're not actually usable? That's what happens when we slice stories horizontally (e.g. a user story to build a non-functional screen). Horizontal slicing brings on risks to the organization, like: Prematurely prescribing an implementation Lengthening the feedback loop Delaying value delivery Misaligning user story delivery metrics Vertical slicing, however, allows our teams to be agile by ensuring the delivery of functional, valuable capabilities driven by user needs and feedback…

Agile Bites

1
Scaling Agile - Is Less More? 20:20

1 year ago20:20

20:20

Wondering what scaled Agile framework is right for your organization? If this is your question, this episode is not going to answer it for you because we don't think that's going to bring you the most value. Instead, we're going to challenge you to take a step back and ask why you need to scale and why you're Agile in the first place. Just because your organization is “big" and your current framework is causing friction, that does not mean finding the right scaled Agile framework is the answer (in fact, it's usually not). And implementing a scaled framework might actually cause more pain than not. In this episode, we explore the underlying reasons and common misconceptions behind scaling, from the classic scenario of numerous teams to the allure of frameworks like SAFe. Discover how you can navigate dependencies, optimize team structures, rethink release cadences, and look at your team's framework from a different perspective to get to the Agility you're looking for.…

Agile Bites

1
Business Analysts in an Agile World 25:35

1 year ago25:35

25:35

Traditionally confined to creating hefty upfront requirements documents, BAs find themselves at a crossroads in the Agile world. However, we believe BAs hold the key to promoting agility and delivering maximum value to organizations. In this episode, we challenge the notion that BAs are mere translators of requirements into user stories. Instead, we highlight the rich business knowledge and questioning skills that BAs possess. By delving deep into business processes and understanding the "why" behind them, BAs can unearth genuine value in user stories. BAs also have the unique opportunity to uncover hidden needs and facilitate cross-functional dialogues that drive process improvements. By fostering collaboration and aligning business objectives with software development, BAs can contribute to the creation of software that not only meets user needs but also enhances overall organizational efficiency.…

Agile Bites

1
What's Next For Agile Bites? 18:34

1 year ago18:34

18:34

In the year and a half that the Agile Bites podcast has been around, we've covered a lot of topics—from story points to stand-ups to MVPs and a whole lot more. And we hope it's been a helpful resource in our listeners' Agile journeys. Now, we're taking a look at the future and asking ourselves, "What's next?" Listen to this episode to hear from Host Phil Ledgerwood about the new direction of Agile Bites, and we'd love for you to be a part of it by leaving your feedback! Leave a comment on this platform or email Phil at phil@integrityinspired.com.…

Agile Bites

1
What Was Rally Thinking? 22:20

1 year ago22:20

22:20

If we had a dollar for every piece of “authoritative Agile advice” out there, let's just say that we'd have a lot of money. Sharing the successes, failures, and lessons learned is so valuable to all of us on an Agile journey. But it's important to keep your filter up for not only false information, but also true information that doesn't fit your situation. In this episode, Host Phil Ledgerwood dissects some “authoritative” facts and figures about so-called “full Scrum” vs. “lightweight Scrum” to demonstrate how easy it can be to fall into the trap of misleading Agile guidance. The lesson here? Don’t blindly accept what anyone says, no matter the source (even this podcast!). Always investigate, weigh it carefully, and experiment for yourself.…

Agile Bites

1
QA in an Agile World 22:58

1 year ago22:58

22:58

Traditionally, QA has been synonymous with manual testing and has been established as its own post-development phase. But in an agile landscape, that setup can lead to bottlenecks and silos. That's why we advocate for making QA a strategic player throughout the entire development journey—not just at the end of development. Tune in to gain insights on reshaping QA practices and maximizing its impact on the entire value stream of software development.…

Agile Bites

1
Can User Stories Be Too Small? 20:06

1 year ago20:06

20:06

We all know we should get user stories as small as they can be, but can we go too far? Yes, user stories should be as small as we can get them, but they also need to be a valuable delivery (e.g. a user story should not just be a technical task). Tune into this episode for actionable tips on what to do (and what not to do) to keep your user stories both small and valuable.…

Agile Bites

1
User Stories Are Not Requirements 21:50

1 year ago21:50

21:50

Have you or someone you know ever been stuck with pages of requirements notes having to turn those into user story format (As a [persona], I [want to], [so that])? If so, first of all, we're sorry. Secondly, we want to help you know that there are other—and better—ways to dealing with this situation, and that's what this episode is all about. User stories should be user STORIES—pigeonholing them into a one-size-fits-all format takes away from the value they were meant to provide. Tune into this episode to hear a brief history of user stories and get back to the WHY behind them so that your user stories function the way they're supposed to.…

Agile Bites

1
Should We All Go Back to the Office? 21:54

1 year ago21:54

21:54

You might be wondering what this controversial subject has to do with agility, but people in the agile community are already trying to figure out how this topic works in an agile environment. How do we reconcile with the work-from-home debate when one of the principles of the Agile Manifesto is that “the most efficient and effective method of conveying information to and within a development team is face-to-face conversation?” Ultimately, just like anything else, this is something that is heavily dependent on context and is a decision each organization needs to make. But this episode lays out the realities of both dispersed and co-located teams and presents ways to approach this topic from an agile perspective.…

Agile Bites

1
The Biggest Lie Your Developers Tell 23:27

1 year ago23:27

23:27

When you ask how long a project is going to take, do you ever feel like your developer team is telling you what you want to hear rather than reality? Unfortunately, this problem is all too common in software development when it comes to estimating deadlines and giving progress updates. We're not claiming it's anything nefarious—humans are just bad at predicting how long things are going to take (especially when building a huge project for the first time) and they probably just want to keep you happy. In this episode, learn what signs to look for if you're being lied to, why teams feel like they need to lie, and how to prevent a culture that incentivizes it.…

Agile Bites

1
MVPs - How Will You Measure 23:00

1 year ago23:00

23:00

So you've defined success for your MVP. But have you thought about how you're going to measure whether it's successful or not? It sounds simple, but it's often not. Some measurements are black-and-white and easier to extract information from. But others (like sentiment) have a lot more gray areas and can be tricky to make decisions based on. In this last episode of our MVP series, learn about different types of measurements (financial, technical, operational, and psychological) and how to extract valuable data from even the trickiest of factors so you can make smart decisions about your product.…

Agile Bites

1
MVPs - Defining Success 18:09

1 year ago18:09

18:09

Next in line on MVP series, we're talking about defining success for your MVP. The point of an MVP is not to create a small version of the product—it's to get meaningful information that will inform your decisions about the product going forward.Because of this, how you define success plays a vital role in whether your MVP reveals valuable information about your product's viability. What things, if they turned out to be true or false, would cause you to rethink this product or would convince you that you’re on the right track? In this episode, learn about the different success indicators that can be considered and how to define those best so you can measure the valuable information to make informed decisions about your product's future.…

Agile Bites

1
MVPs - Schedule and Cost 21:54

1 year ago21:54

21:54

Next up in our MVP series, we're talking about schedule and cost—two related elements that can trigger essential pivots in your project. In this episode, host Phil Ledgerwood shares practical insights on estimating timelines, development costs, and additional considerations such as infrastructure and promotional expenses. Learn how these factors play a pivotal role in making informed decisions about your MVP.…

Agile Bites

1
MVPs - Feature Selection 19:45

1 year ago19:45

19:45

How do you decide which features should make it into your MVP? When people first think about MVPs, usually this is the point they jump to (side note: if you haven't listened to our previous episodes in our MVP series yet, go back and listen to those first!) With countless feature options and probably many strong opinions, it can be challenging to narrow down what features you should invest in for your first MVP. In this episode, Host Phil Ledgerwood shares the framework and exercises he uses to help define MVP features with that will be valuable for future decisions about your product.…

Agile Bites

1
MVPs - The User Journey (Don't Stop Believin') 19:58

1 year ago19:58

19:58

Forget about software for a second and think about what your user actually wants to accomplish. Why would they want your software in the first place? What are you helping them to get done more easily than they could without your software? Those questions are what you should be thinking about when it comes to user journey—not screens or features. Because your users don't inherently care about those things. They just want to accomplish whatever they need to get done in a way that makes sense to them. In this episode, Host Phil Ledgerwood explains the importance of user journeys and what you need to think about as you go about understanding how your users will best interact with your product.…

Agile Bites

1
MVPs - The "Who": Personas 22:47

1 year ago22:47

22:47

Next up in our series about MVPs, we're talking about personas. To know if people are going to use your product, you first have to understand the people you would be building the product for—because no product can be built for “everyone.” In this episode, Host Phil Ledgerwood breaks down MVP personas into three parts: identifying potential users, understanding them, and empathizing with them. When you truly understand your potential users, that knowledge helps you build a product that serves your users better—and that should be your ultimate goal.…

Agile Bites

1
MVPs - The "How": The Vision 16:32

1 year ago16:32

16:32

In the next episode in our series about MVPs, we're talking about the vision: the thing that guides, outlines the scope, and captures the value of the MVP. Everything we do in the MVP needs to be geared towards the vision—not towards your idea of the final product. If it’s extraneous to the vision, it’s extraneous to the MVP. Sticking to the vision will keep you from wasting time and money on features that aren't necessary to validate the core of your product.…

Agile Bites

1
MVPs - The “What” and the “Why” 19:38

1 year ago19:38

19:38

After 67 episodes, it's about time we talk about the MVP—Minimum Viable Product. There are a whole lot of conversations online about what an MVP is and what it isn't. We're not setting out to define it once and for all. Instead, we're taking you through the same process we go through with our clients in this special series about MVPs. And this first episode is all about the “what” and the “why” behind this framework that can help you validate a product idea before putting a full investment into it.…

Agile Bites

1
A Little Help - Compare Apples to Apples 16:45

1 year ago16:45

16:45

We're covering the last assumption of Little's Law in this series, and this time we're looking at why consistent units must be used for all measures This one seems obvious and trivial, but that doesn't always translate on a practical level when we're thinking about how we want our work items and the planning around them to look. This assumption comes down to deciding what unit of measurement is valuable for planning and communicating, and then only using those units—not transferring them to other ways of measuring. In this episode, dive into this thought-provoking assumption with us and learn how consistency of your measurements can make your forecasts more meaningful, stable, and reliable.…

Agile Bites

1
A Little Help - Aging Gracefully 18:23

1 year ago18:23

18:23

It's time to unpack another assumption of Little's Law, and this time we're looking at how and why the average age of WIP must not be meaningfully changing. This is probably one of the most misunderstood assumptions because people think everything must be the same size. But the key to remember here is the word "average." Little’s Law needs the average age to stay level— not each individual age to stay level. In this episode, Host Phil Ledgerwood talks through this assumption and its upsides/downsides.…

Agile Bites

1
A Little Help - Don't Overwork, Don't Underwork 16:41

1 year ago16:41

16:41

We've been working our way through a series on the assumptions of Little's Law, and this episode is about the importance of keeping your WIP constant in your system as a whole. Little’s Law doesn’t tell you the right amount of WIP—it just wants it to be stable so that you're pulling work at the same rate that work is completed. This way, your system stays flowing and is neither underworked nor overworked. In this episode, Host Phil Ledgerwood illustrates how this assumption of Little's Law works, and how you can implement it in your team.…

Agile Bites

1
A Little Help - Finishing What You Start 22:12

1 year ago22:12