Agile Bites

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 di...

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 vis...

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...

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...

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 y...

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...

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 antiquit...

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...

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...

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" an...

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 questi...

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...

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 Phi...

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 i...

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.

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—pigeonholin...

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...

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...

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,...

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. ...

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...

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...

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...

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....

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...