Africa-focused technology, digital and innovation ecosystem insight and commentary.
…
continue reading
Player FM - Internet Radio Done Right
Checked 11M ago
Added two years ago
Content provided by Integrity Inspired Solutions. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Integrity Inspired Solutions or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.
Similar to Agile Bites
Show notes are at https://stevelitchfield.com/sshow/chat.html
…
continue reading
The director’s commentary track for Daring Fireball. Long digressions on Apple, technology, design, movies, and more.
…
continue reading
The power of Data is undeniable. And unharnessed - it’s nothing but chaos. Making data your ally. Using it to lead with confidence and clarity. Host Jess Carter is solving problems in real-time to reveal what’s possible. Helping communities and people thrive. This is Data Driven Leadership, a show brought to you by Resultant.
…
continue reading
Download This Show is your weekly guide to the world of media, culture, and technology. From social media to gadgets, streaming services to privacy issues. Each week Rae Johnston and guests take a fun, deep dive into how technology is reshaping our lives.
…
continue reading
Android Backstage, a podcast by and for Android developers. Hosted by developers from the Android engineering team, this show covers topics of interest to Android programmers, with in-depth discussions and interviews with engineers on the Android team at Google. Subscribe to Android Developers YouTube → https://goo.gle/AndroidDevs
…
continue reading
We help founders make something people want.
…
continue reading
This is the audio podcast version of Troy Hunt's weekly update video published here: https://www.troyhunt.com/tag/weekly-update/
…
continue reading
Redefining AI is the 2024 New York Digital Award winning tech podcast! Discover a whole new take on Artificial Intelligence in joining host Lauren Hawker Zafer, a top voice in Artificial Intelligence on LinkedIn, for insightful chats that unravel the fascinating world of tech innovation, use case exploration and AI knowledge. Dive into candid discussions with accomplished industry experts and established academics. With each episode, you'll expand your grasp of cutting-edge technologies and ...
…
continue reading
A podcast about web design and development.
…
continue reading
Player FM - Podcast App
Go offline with the Player FM app!
Go offline with the Player FM app!
))
Daily Deals
Podcasts Worth a Listen
SPONSORED
<
<div class="span index">1</div> <span><a class="" data-remote="true" data-type="html" href="/series/tickets-to-travel">Tickets to Travel</a></span>
What exactly is a travel experience? A travel experience is more than just a destination. From the pulsating beats of a major music festival, to the adrenaline -fueled excitement of professional sports, to the legendary tours of music icons, these events are more than just spectacles. They are game changers affecting airfares, hotel room rates, restaurants, and growing local economies. Welcome to Tickets to Travel, the podcast that unlocks the stories, businesses, careers, and personalities within the realm of unforgettable travel experiences. I'm Mario B, and I have over 20 years of experience in online travel and entertainment ticketing distribution. Join me as we delve into the vibrant tapestry of these industries, uncovering hidden gems and insider secrets along the way. Tickets to travel spotlights the trailblazing businesses shaping the future of travel experiences. These startups and innovative companies are driving forces that redefine how we explore the world. Whether you're a seasoned jet center, an aspiring entrepreneur, or simply curious about the transformative power of travel, join me on Tickets to travel as I embark on this exhilarating journey through the world of travel experiences. Follow us where you get your podcasts.
A Little Help - Compare Apples to Apples
Manage episode 392966485 series 3495087
Content provided by Integrity Inspired Solutions. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Integrity Inspired Solutions or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.
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.
93 episodes
Share
Manage episode 392966485 series 3495087
Content provided by Integrity Inspired Solutions. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Integrity Inspired Solutions or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.
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.
93 episodes
All episodes
×
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.…
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.…
1 Agile Team Management and Visualization (It's Not What You Think) 17:42
17:42 
Play Later 
Play Later 
Lists 
Like 
Liked17:42
Play Later Play Later Lists Like LikedA 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.…
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.…
1 How To Manage Software Teams - Fundamentals 20:34
20:34 Play Later Play Later Lists Like Liked20:34
Play Later Play Later Lists Like LikedMany 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.…
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.…
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.…
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.…
1 Slicing Stories Vertically vs. Horizontally 18:23
18:23 Play Later Play Later Lists Like Liked18:23
Play Later Play Later Lists Like LikedShould 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…
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.…
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.…
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.…
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.…
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.…
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.…
A
Agile Bites
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.…
A
Agile Bites
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.…
A
Agile Bites
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.…
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.…
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.…
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.…
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.…
A
Agile Bites
1 MVPs - The User Journey (Don't Stop Believin') 19:58
19:58 Play Later Play Later Lists Like Liked19:58
Play Later Play Later Lists Like LikedForget 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.…
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.…
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.…
A
Agile Bites
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.…
A
Agile Bites
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.…
A
Agile Bites
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.…
A
Agile Bites
1 A Little Help - Don't Overwork, Don't Underwork 16:41
16:41 Play Later Play Later Lists Like Liked16:41
Play Later Play Later Lists Like LikedWe'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.…
A
Agile Bites
When a card gets pulled to work on, that should mean that the team is committing to not only starting it but also (and more importantly) finishing it. Now, we all know that it's not always that simple. Blockers happen, new priorities come down the management pipeline, and, unfortunately, cards in progress are forgotten or pushed backward into the backlog. But at the end of the day, your team is judged on the work they finish—not the work they start. And that's why the commitment to finishing should be the highest priority rather than the commitment to start something. In this episode, Host Phil Ledgerwood talks about why cards get started but not finished and how to avoid ending up in this situation in the first place.…
A
Agile Bites
1 Breaking Barriers by Elevating Your Constraint 20:36
20:36 Play Later Play Later Lists Like Liked20:36
Play Later Play Later Lists Like LikedSo you've identified the constraint. You've optimized your constraint. You've learned to subordinate to your constraint. Assuming you haven't skipped any of these important steps (if you have, go back and listen to those episodes!), now it's time to elevate your constraint. In this episode, host Phil Ledgerwood discusses ways to get the most efficiency out of your constraint and increase its capacity to keep work moving forward. ➡️ Connect with Agile Bites Host Phil Ledgerwood on LinkedIn ➡️ Visit our website…
When you're starting to build an application, at what point should the database be designed? (To our non-developer listeners, hang in there—this is relevant to you!) There are a lot of opinions on this topic in the software community, and many say the database should come first. But if you're building an application in an agile manner, why would you start with a piece of the project that the user can't interact with and give feedback on? In this episode, host Phil Ledgerwood discusses why he thinks starting with the database can not only hold back your team's agility but also negatively affect the quality of the application in the long run. And he'll be giving some suggestions for better places to start that will help you create a more useful app for your users. ➡️ Connect with Agile Bites Host Phil Ledgerwood on LinkedIn ➡️ Visit our website…
We all know that having lots of work in process causes problems when it comes to your delivery rate. If you're on a Scrum team, this can look like items getting carried over from sprint to sprint, nothing being ready until the very end of the sprint, no capacity to respond to emergency fixes, or every new user story taking longer and longer to complete. These can all be indicators that your Scrum team has too much WIP. But before you start thinking you need to incorporate other techniques and frameworks that focus on limiting WIP—did you know that Scrum already had a WIP limiting mechanism built into the framework? In this episode, learn to take advantage of the ways Scrum can guide your team to limit the amount of work they have in progress and deliver at a more consistent rate. Connect with Agile Bites Host Phil Ledgerwood on LinkedIn Visit our website…
A
Agile Bites
Can you be a good scrum master or agile coach without experience in the domain you work on? There are several schools of thought when it comes to this controversial question. Some say yes, some say no, and some say that technical knowledge can actually make you worse at your job. What should actually be the standard? Who's to say? But in this episode, we're going over the different perspectives we've come across and sharing our viewpoint on the matter. Connect with Agile Bites Host Phil Ledgerwood on LinkedIn Visit our website…
A
Agile Bites
The title of this episode may sound counterintuitive, but it's actually the key to optimizing your team's agility. When we say “working less,” we're not talking about slacking off—we're talking about balancing your workflow by subordinating your work stages to your constraint. Having every team member produce the most amount of work at all times seems like the fastest way complete projects, but it's not. And it'll actually work against you. In this episode, learn how you can start thinking about your team as a stream of value rather than individual units cranking out as much work as possible. And in learning that, we hope you more clearly see the path to delivering value in the most efficient way possible. Connect with Agile Bites Host Phil Ledgerwood on LinkedIn Visit our website…
A
Agile Bites
Every Scrum master's nightmare is their team wanting to switch to Kanban. It's easy to look at a shiny new framework and think that it's going to solve all your problems. And while we do think that Scrum is not the best fit for most software teams, there are both good and bad reasons to consider before jumping into another framework. In this episode, get ready to think about some hard truths (like, is the problem your framework, or is it something going on in your team?). And also hear about some good reasons to make the switch to Kanban.…
A
Agile Bites
True or false: For Kanban, Monte Carlo, and Little's Law to work, your work items have to be a similar size. When we think about forecasting work, it's easy to think that the best way is to add up the total amount of time it takes to complete something and use that to predict the future. But that's actually not the case. In this episode, learn how you can let go of worrying about making all your cards the same size in order to get accurate forecasting.…
Regardless of what Agile strategy or framework a team is using, at the end of the day, one of the biggest questions teams are trying to answer is, “What can we get done in a certain timeframe?” And some choose to address this by using velocity: adding up the number of story points delivered in a sprint and using that to determine how much can get done in a future sprint. But does that really make sense with how story points work? And more importantly, is it even accurate at predicting future work? In this episode, find out why we think velocity is actually meaningless and learn about better alternatives you can use to predict your team's output.…
A
Agile Bites
So you've found your constraint—what now? (or maybe you haven't found your constraint yet. In that case, scroll back a few episodes and listen to “Finding the Constraint” first!) Your constraint is basically what's controlling the pace of your whole system. So now that you've found it, you need to optimize it so it's working continuously and effectively (notice that we didn't say to get rid of the constraint!) In this episode, we're giving you practical tips to optimize your constraint so that you're putting your efforts to improve your team's flow in the right place.…
Just because the “Q” in “QA” stands for “Quality” doesn't mean that this role should be the only one who's responsible for making sure features are up to standards. Unfortunately, too many QAs spend their limited time just making sure that features WORK, let alone finding edge cases and addressing actual bugs. And then they have to pull the developer back in to fix the feature after the developer has already moved on to the next one. Talk about a bottleneck! Quality can't only be QA's job—it needs to be everyone's job. Spending the time building in quality up front will prevent overhead involved in re-work, keeping your system flowing and allowing QA to do what they're best at. In this episode, you'll learn three actionable steps to start making quality a team sport for your software development team.…
A
Agile Bites
When Daniel was learning Karate in The Karate Kid, Mr. Miyagi had him start by doing tasks over and over without explanation so he could master the basics before actually using the martial art on his own. And this method of mastering a skill is something we see across many disciplines outside martial arts—sometimes it's even applied to learning agility. But is following and mastering “the rules” before venturing off and making your own improvements the best way to start to increase your agility? We say no, because getting good at executing a framework is missing the point of being Agile. In this episode, we hope to encourage you to look at your team's unique goals and desired outcomes and feel free to step outside of “the rules” so you can focus on what's working and leave behind what's not.…
A
Agile Bites
1 Row Together! Synchronize Your Team With Drum-Buffer-Rope 19:01
19:01 Play Later Play Later Lists Like Liked19:01
Play Later Play Later Lists Like LikedHopefully, you know by now that limiting your work in progress is the solution to a lot of delivery problems. Both Scrum and Kanban have their own ways of limiting WIP, but there's another way you might not have heard of: Drum-Buffer-Rope scheduling. In this episode, learn what Drum-Buffer-Rope scheduling is and how it can align the activities of your team and reduce bottlenecks in your flow.…
A
Agile Bites
One of the benefits we can get out of Agile and Lean processes is the ability to forecast work based on a team’s metrics. But if you’ve just started tracking your cycle time and running Monte Carlo simulations, and your results are all over the map, this podcast is for you. We’re sharing with you what things need to be in place so that when you do run forecasts or look at your cycle time scatterplots, you’ll see results that are meaningful, useful, and actionable.…
Every system, no matter how optimized, has a constraint—the point in the system that has the lowest throughput. But do you know where yours is? And what are you doing about it? Knowing your constraint means knowing where you can make meaningful improvements to your system. Because if you make improvements to the wrong part of the system, you could actually make your flow worse (*cough, cough* hiring more developers when they're not the actual source of the bottleneck). In this episode, learn why you should know where your system's constraint is, how you can find it, and what options you have with what to do with it.…
The whole concept behind using the word “flow” in “workflow” is that work keeps moving forward. Sounds nice, right? But we all know it's a little ambiguous in practice. What about those times when cards seem to need to move backward on the board? Like when QA finds a bug—should the card move back to Dev? To answer that question, we first have to remember why the columns on the Kanban board exist in the first place: to be stages of transformation—not roles or specific activities, per se. And with that teaser, you can probably guess what our answer is. If not (or even if you have), listen to this episode to find out!…
Welcome to Player FM!
Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.
Daily Deals
Similar to Agile Bites
Africa-focused technology, digital and innovation ecosystem insight and commentary.
…
continue reading
Show notes are at https://stevelitchfield.com/sshow/chat.html
…
continue reading
The director’s commentary track for Daring Fireball. Long digressions on Apple, technology, design, movies, and more.
…
continue reading
The power of Data is undeniable. And unharnessed - it’s nothing but chaos. Making data your ally. Using it to lead with confidence and clarity. Host Jess Carter is solving problems in real-time to reveal what’s possible. Helping communities and people thrive. This is Data Driven Leadership, a show brought to you by Resultant.
…
continue reading
Download This Show is your weekly guide to the world of media, culture, and technology. From social media to gadgets, streaming services to privacy issues. Each week Rae Johnston and guests take a fun, deep dive into how technology is reshaping our lives.
…
continue reading
Android Backstage, a podcast by and for Android developers. Hosted by developers from the Android engineering team, this show covers topics of interest to Android programmers, with in-depth discussions and interviews with engineers on the Android team at Google. Subscribe to Android Developers YouTube → https://goo.gle/AndroidDevs
…
continue reading
We help founders make something people want.
…
continue reading
This is the audio podcast version of Troy Hunt's weekly update video published here: https://www.troyhunt.com/tag/weekly-update/
…
continue reading
Redefining AI is the 2024 New York Digital Award winning tech podcast! Discover a whole new take on Artificial Intelligence in joining host Lauren Hawker Zafer, a top voice in Artificial Intelligence on LinkedIn, for insightful chats that unravel the fascinating world of tech innovation, use case exploration and AI knowledge. Dive into candid discussions with accomplished industry experts and established academics. With each episode, you'll expand your grasp of cutting-edge technologies and ...
…
continue reading
A podcast about web design and development.
…
continue reading
Player FM - Podcast App
Go offline with the Player FM app!
Go offline with the Player FM app!
