Player FM - Internet Radio Done Right
Checked 2d ago
اضافه شده در one سال پیش
محتوای ارائه شده توسط Scott L. Bain. تمام محتوای پادکست شامل قسمتها، گرافیکها و توضیحات پادکست مستقیماً توسط Scott L. Bain یا شریک پلتفرم پادکست آنها آپلود و ارائه میشوند. اگر فکر میکنید شخصی بدون اجازه شما از اثر دارای حق نسخهبرداری شما استفاده میکند، میتوانید روندی که در اینجا شرح داده شده است را دنبال کنید.https://fa.player.fm/legal
Player FM - برنامه پادکست
با برنامه Player FM !
با برنامه Player FM !
#48-Implications of the Agile Manifesto, Part 3
Manage episode 469410131 series 3564249
محتوای ارائه شده توسط Scott L. Bain. تمام محتوای پادکست شامل قسمتها، گرافیکها و توضیحات پادکست مستقیماً توسط Scott L. Bain یا شریک پلتفرم پادکست آنها آپلود و ارائه میشوند. اگر فکر میکنید شخصی بدون اجازه شما از اثر دارای حق نسخهبرداری شما استفاده میکند، میتوانید روندی که در اینجا شرح داده شده است را دنبال کنید.https://fa.player.fm/legal
This week I will cover part three of four in the Agile Manifesto, as preparation for my final entry in this series that will suggest how to address these implications in your organization.
72 قسمت
Manage episode 469410131 series 3564249
محتوای ارائه شده توسط Scott L. Bain. تمام محتوای پادکست شامل قسمتها، گرافیکها و توضیحات پادکست مستقیماً توسط Scott L. Bain یا شریک پلتفرم پادکست آنها آپلود و ارائه میشوند. اگر فکر میکنید شخصی بدون اجازه شما از اثر دارای حق نسخهبرداری شما استفاده میکند، میتوانید روندی که در اینجا شرح داده شده است را دنبال کنید.https://fa.player.fm/legal
This week I will cover part three of four in the Agile Manifesto, as preparation for my final entry in this series that will suggest how to address these implications in your organization.
72 قسمت
همه قسمت ها
×A
Agile Tips

People fear being replaced by AI. Should they? This episode will examine why this concern may not be as founded as people think, at least when it comes to industries I am familiar with.
This episode will use software development as an example of how AI can be used to make the product development process more efficient, and less wasteful. This is an example which I believe could apply to any kind of product.
This podcast will kick off a series of episodes on AI, and my personal view of it.
A
Agile Tips

This week I will wrap up the notion of Shift Left, and introduce the next topic for this podcast.
The final "shift left" I will examine is the detection of defects during the planning process, specifically requirements analysis. It represents one of the most important and also most difficult challenges that face us when developing products.
In our continuing effort to shift the detection of defects and other mistakes to earlier and earlier phases in our development process, this week I'll discuss the role that design can play.
This week we will examine how defects can be detected and sometimes even prevented during the implementation of the product as analyzed and designed in the previous phases.
We're shifting left again, to the integration phase that precedes traditional testing. What defects can and should ideally be detected at this point, and how can we accomplish this? That's what this episode with examine.
We're shifting left, and the next shift involves uncovering bad or missing behavior during the traditional testing phase. Such testing is important and necessary, but is it enough? We'll see.
In this episode, I will investigate the first step in shifting left, which is to detect product defects at the time they are sold and deployed but before they are in use by the customer, and therefore cannot impact them.
The next series of podcasts will examine the concept of shift left, which deals with the way we determine and remediate defects in our product. This week I will start with the notions of detecting these defects when the product is being used.
This episode will introduce the concept of the "Shift Left" initiative in product development, and will set the stage for a series of podcasts that examine key aspects and implications of it.
This episode is about the creation of acceptance tests, who should write them and how they should be structured, to get the maximum value from them.
This episode will tell you a story about a time when missing a critical stakeholder caused a company to make a potentially disastrous mistake in their business automation.
This episode will examine the difference between Requirements and the Expectations that drive them, and suggest ways that we can better serve our organization by focusing on the latter.
به Player FM خوش آمدید!
Player FM در سراسر وب را برای یافتن پادکست های با کیفیت اسکن می کند تا همین الان لذت ببرید. این بهترین برنامه ی پادکست است که در اندروید، آیفون و وب کار می کند. ثبت نام کنید تا اشتراک های شما در بین دستگاه های مختلف همگام سازی شود.