معلومات عن هذه الحلقة
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.
الإنجليزية
الولايات المتحدة
النص 🔗
Are you the producer of this podcast?
Add a podcast transcript
Need Audio-to-Text?
Transcribe with Listen411 in Just 60 Seconds
البحث في الحلقات الماضية
البحث في الحلقات السابقة من Agile Bites.
حلقات أخرى في هذا البودكاست
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 an…
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,…
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 trans…
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…
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…
إخلاء المسؤولية: البودكاست والأعمال الفنية المضمنة في هذه الصفحة مأخوذة من Integrity Inspired Solutions، وهي مملوكة لمالكها وليست تابعة لشركة Listen Notes, Inc أو معتمدة منها.
تعديل
شكراً على مساعدتنا في الحفاظ على قاعدة بيانات البودكاست مُحدَّثة.
