Africa-focused technology, digital and innovation ecosystem insight and commentary.
…
continue reading
Player FM - Internet Radio Done Right
Checked 7h ago
اضافه شده در one سال پیش
محتوای ارائه شده توسط Scott L. Bain. تمام محتوای پادکست شامل قسمت‌ها، گرافیک‌ها و توضیحات پادکست مستقیماً توسط Scott L. Bain یا شریک پلتفرم پادکست آن‌ها آپلود و ارائه می‌شوند. اگر فکر می‌کنید شخصی بدون اجازه شما از اثر دارای حق نسخه‌برداری شما استفاده می‌کند، می‌توانید روندی که در اینجا شرح داده شده است را دنبال کنید.https://fa.player.fm/legal
مشابه Agile Tips
Show notes are at https://stevelitchfield.com/sshow/chat.html
…
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
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
Flash Forward is a show about possible (and not so possible) future scenarios. What would the warranty on a sex robot look like? How would diplomacy work if we couldn’t lie? Could there ever be a fecal transplant black market? (Complicated, it wouldn’t, and yes, respectively, in case you’re curious.) Hosted and produced by award winning science journalist Rose Eveleth, each episode combines audio drama and journalism to go deep on potential tomorrows, and uncovers what those futures might re ...
…
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
This is the audio podcast version of Troy Hunt's weekly update video published here: https://www.troyhunt.com/tag/weekly-update/
…
continue reading
The director’s commentary track for Daring Fireball. Long digressions on Apple, technology, design, movies, and more.
…
continue reading
Three nerds discussing tech, Apple, programming, and loosely related matters.
…
continue reading
We help founders make something people want.
…
continue reading
Player FM - برنامه پادکست
با برنامه Player FM !
با برنامه Player FM !
))
پادکست هایی که ارزش شنیدن دارند
حمایت شده
In 1910, Dorothy Arnold—a wealthy, educated socialite from New York City—left her home for a shopping trip and never returned.
#30-Follow The Open-Closed Principle
Manage episode 444000577 series 3564249
محتوای ارائه شده توسط Scott L. Bain. تمام محتوای پادکست شامل قسمت‌ها، گرافیک‌ها و توضیحات پادکست مستقیماً توسط Scott L. Bain یا شریک پلتفرم پادکست آن‌ها آپلود و ارائه می‌شوند. اگر فکر می‌کنید شخصی بدون اجازه شما از اثر دارای حق نسخه‌برداری شما استفاده می‌کند، می‌توانید روندی که در اینجا شرح داده شده است را دنبال کنید.https://fa.player.fm/legal
In order to embrace change, as agile says we must, we must make sure that changes to the system going forward do not create excessive waste and/or delays. Part of how we can do this is to follow good principles, such as the Open-Closed Principle. This episode will explain this principle, and what it means.
64 قسمت
اشتراک گذاریManage episode 444000577 series 3564249
محتوای ارائه شده توسط Scott L. Bain. تمام محتوای پادکست شامل قسمت‌ها، گرافیک‌ها و توضیحات پادکست مستقیماً توسط Scott L. Bain یا شریک پلتفرم پادکست آن‌ها آپلود و ارائه می‌شوند. اگر فکر می‌کنید شخصی بدون اجازه شما از اثر دارای حق نسخه‌برداری شما استفاده می‌کند، می‌توانید روندی که در اینجا شرح داده شده است را دنبال کنید.https://fa.player.fm/legal
In order to embrace change, as agile says we must, we must make sure that changes to the system going forward do not create excessive waste and/or delays. Part of how we can do this is to follow good principles, such as the Open-Closed Principle. This episode will explain this principle, and what it means.
64 قسمت
همه قسمت ها
×
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.
Information radiators are extremely useful to an agile organization. But often there are such radiators that have been missed. This episode will investigate this problem.
How you measure the progress of an agile team will fundamentally effect how much value that team will produce, since that measurement will reflect that value. What should that measurement consist of? That's the topic for this week.
This week I will relate the notion of "changing change" to the test-driven development process, in two different senses.
Part three of this series on changing our relationship to change deals with the concept of encapsulating variation in business automation. This is expressed in non-technical language and should be useful to those that lead product development initiatives.
This episode will explore another aspect of the agile design process, from a non-technical point of view.
If we are to be successfully agile, we must embrace unpredictable change. But to do that, we have to fundamentally alter our relationship to change itself. This is part one of a series about how I recommend teams accomplish this.
The fourth point of the Agile Manifesto, that we value responding to change over following a plan, has massive implications for the way agile teams are managed. This podcast will introduce the issues that result, and will lead to the next series.
This week I will answer the questions raised over the last four Agile Tips, each a different aspect of the Agile Manifesto. I'll also set the stage for what to expect next from this series.
This week I will tackle the four point of the Agile Manifesto, with an eye toward my conclusion podcast next week.
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.
This week I will investigate part 2 of the Agile Manifesto, as part of my series of four podcasts on the subject.
This week I'll examine the first point in the Agile Manifesto, as part of a series of four podcasts.
In this episode we will examine the roots of the Agile Movement, and delineate the Agile Manifesto that came from those roots. This will begin a series of five podcasts that point out the implications of each item in this manifesto.
No matter what kinds of products and services an organization offers, there are terms that are specific to them. These terms must be carefully defined and consistently updated as things change. This podcast is all about creating such a set of definitions.
This episode will introduce a useful framework for organizing requirements as the are identified. Such organization can be very helpful in collaboration and validation throughout an agile process.
Various technologies provide us with the concept of "inheritance". What should this used for, ideally, in an agile development environment? This episode addresses this question in a way that should be interesting to non-technical people as well as developers and testers.
The way we create business automation in the modern environment has been influenced by the strength of various innovations that have preceded us. This week I'll introduce this idea, and then over the next few episodes will examine some of the implications and opportunities.
Last week I pointed out that Test-Driven Development, even though it is named as it is, is not a testing activity but rather the creation of an executable specification. So how does this change how they are written? That's the subject of this episode.
This week I wrap up my answer to the question of three weeks ago and is so going point out, perhaps, the most important aspect of TDD, and how to make sure it delivers all the value it is capable of.
Part two of my answer to the question posted two weeks ago. There is one more to come, next week. It may be the most crucial of these answers.
This is my first answer to the question posed last week. There will be two more in future weeks.
Teaching Test-Driven Development, either in the unit testing form for developers or the acceptance testing that anyone can learn and do, this questions almost always arises at some point. It's actually an excellent question and can yield a lot of value in answering it. This episode will explain why.
How does this principle apply to the notion of an agile process? I think it fundamentally changes the way we create automation, and the value that automation ultimately provides. This week I explain why.
This is kind of a fun one. I start by pointing out that, regardless of appearances, computers are not really doing any of the things we think they are doing. Examining this fact, and it is a fact, leads to some interesting and I think useful insights. Next week, I'll drive this idea into practicality.…
Products that are difficult to use or illogical in their design can seriously impede their value. This episode will examine an example of such a problem, from the author's own personal experience with a new car.
Last week I teased the notion that it's possible to bring your legacy code under better control by using a magic button. While such buttons obviously do not exist, this week I'll outline how to get the value of such a resource anyway, at a manageable cost.
What is the best way to deal with the fact that most organizations have a high degree of vulnerability to the quality (or lack thereof) of the legacy systems they depend upon? This week I'll discuss a thought experiment that helps us to understand this conundrum, and next week I'll show you what to do about it.…
In order to embrace change, as agile says we must, we must make sure that changes to the system going forward do not create excessive waste and/or delays. Part of how we can do this is to follow good principles, such as the Open-Closed Principle. This episode will explain this principle, and what it means.…
Last week I discussed the notion of refactoring, and why business people often fail to see the value in it. This week I explore what that value is, and how best to express it honestly.
Should a Project Manager allow a development team to spend time and resources on Refactoring? What is refactoring, and why do they want to do it? It seems to have no business value whatsoever. This episode, and the next, will explore this question and offer a way to resolve it.
If you are familiar with the concept of a "Design Pattern" you may well feel that they reflect an older view of development. Indeed, the patterns were first identified before the popularity of agile approaches. That said, they are entirely agile, and this episode is about why that is.
Collaborating effectively includes, among many necessary skills, the ability to be persuasive. This episode will outline an approach to persuasiveness that I have found to be highly effective in my experience as a consultant and mentor.
Over the last two weeks I discussed the power of list-making in an agile project. This week, I dig into the details of one very important list, which is a list of the stakeholders to a given product, project, or feature.
Last week I introduced the notion of a team to-do list, and how important this artifact is during the development of a feature. That list should be curated once the work is done. How that curation is accomplished the the subject of this episode.
One of the most powerful tools available to the team when conducting Acceptance Test-Driven Development, or any kind of requirements analysis, is also one of the simplest ones. This episode is all about that tool.
In agile processes, we need discrete definitions of every important aspect of our work, so that we can work efficiently and effectively together, and to know when organizational goals have been achieved. Part of this is knowing when the work is "done", and that's what this episode is all about.
A
Agile Tips
Part 3 of my analogy on product quality.
A
Agile Tips
Part 2 of my analogy on product quality.
به Player FM خوش آمدید!
Player FM در سراسر وب را برای یافتن پادکست های با کیفیت اسکن می کند تا همین الان لذت ببرید. این بهترین برنامه ی پادکست است که در اندروید، آیفون و وب کار می کند. ثبت نام کنید تا اشتراک های شما در بین دستگاه های مختلف همگام سازی شود.
Daily Deals
مشابه Agile Tips
Africa-focused technology, digital and innovation ecosystem insight and commentary.
…
continue reading
Show notes are at https://stevelitchfield.com/sshow/chat.html
…
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
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
Flash Forward is a show about possible (and not so possible) future scenarios. What would the warranty on a sex robot look like? How would diplomacy work if we couldn’t lie? Could there ever be a fecal transplant black market? (Complicated, it wouldn’t, and yes, respectively, in case you’re curious.) Hosted and produced by award winning science journalist Rose Eveleth, each episode combines audio drama and journalism to go deep on potential tomorrows, and uncovers what those futures might re ...
…
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
This is the audio podcast version of Troy Hunt's weekly update video published here: https://www.troyhunt.com/tag/weekly-update/
…
continue reading
The director’s commentary track for Daring Fireball. Long digressions on Apple, technology, design, movies, and more.
…
continue reading
Three nerds discussing tech, Apple, programming, and loosely related matters.
…
continue reading
We help founders make something people want.
…
continue reading
Player FM - برنامه پادکست
با برنامه Player FM !
با برنامه Player FM !
))
