#45-Implications of the Agile Manifesto

Agile Tips

Player FM - Internet Radio Done Right

اضافه شده در one سال پیش

محتوای ارائه شده توسط Scott L. Bain. تمام محتوای پادکست شامل قسمت‌ها، گرافیک‌ها و توضیحات پادکست مستقیماً توسط Scott L. Bain یا شریک پلتفرم پادکست آن‌ها آپلود و ارائه می‌شوند. اگر فکر می‌کنید شخصی بدون اجازه شما از اثر دارای حق نسخه‌برداری شما استفاده می‌کند، می‌توانید روندی که در اینجا شرح داده شده است را دنبال کنید.https://fa.player.fm/legal

Netflix Is A Daily Joke

1
Jerry Seinfeld:A Joke About The Phrase "It Is What It Is' 1:54

۶ روز پیش1:54

پخش در آینده

لیست ها

پسندیدن

دوست داشته شد

1:54

Jerry Seinfeld jokes about the phrase "it is what it is' in his Netflix special, "23 Hours To Kill".

حدود یک سال پیش 3:00

MP3•خانه قسمت

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.

63 قسمت

#Tech #Scott Bain

Agile Tips

#45-Implications of the Agile Manifesto

Agile Tips

published حدود یک سال پیش

اشتراک گذاری

MP3•خانه قسمت

63 قسمت

#Tech #Scott Bain

همه قسمت ها

Agile Tips

1
#62-Shift Left – Detecting Defects During Deployment 3:27

۲ روز پیش3:27

3:27

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.

Agile Tips

1
#61-Shift Left – Detecting Defects During Product Usage 3:23

۹ روز پیش3:23

3:23

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.

Agile Tips

1
#60-Shift Left - Introduction 3:25

16 روز پیش3:25

3:25

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.

Agile Tips

1
#59-The Structure of an Acceptance Test 4:05

23 روز پیش4:05

4:05

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.

Agile Tips

1
#58-The Risk of The Missing Stakeholder 3:16

۴ weeks پیش3:16

3:16

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.

Agile Tips

1
#57-Requirements vs. Expectations 3:41

۵ weeks پیش3:41

3:41

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.

Agile Tips

1
#56-Utilize the Power of Information Radiators 4:05

۶ weeks پیش4:05

4:05

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.

Agile Tips

1
#55 - Measureing Agile Progress Effectively 4:36

۷ weeks پیش4:36

4:36

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.

Agile Tips

1
#54-Changing Change, Part 4 4:46

۸ weeks پیش4:46

4:46

This week I will relate the notion of "changing change" to the test-driven development process, in two different senses.

Agile Tips

1
#53-Changing Change, Part 3 3:47

۹ weeks پیش3:47

3:47

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.

Agile Tips

1
#53-Changing Change, Part 2 3:02

10 weeks پیش3:02

3:02

This episode will explore another aspect of the agile design process, from a non-technical point of view.

Agile Tips

1
#52-Changing Change, Part 1 4:46

11 weeks پیش4:46

4:46

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.

Agile Tips

1
#51-Responding to Change 4:51

12 weeks پیش4:51

4:51

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.

Agile Tips

1
#50-Implications of the Agile Manifesto, Conclusions 5:22

13 weeks پیش5:22

5:22

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.

Agile Tips

1
#49-Implications of the Agile Manifesto, Part 4 3:05

14 weeks پیش3:05

3:05

This week I will tackle the four point of the Agile Manifesto, with an eye toward my conclusion podcast next week.

Agile Tips

1
#33-Product Confusion Reveals Coupling 3:17

33 weeks پیش3:17

3:17

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.

Agile Tips

1
#32-Legacy Code and Magic Buttons Part 2 3:02

34 weeks پیش3:02

3:02

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.

Agile Tips

1
#31-Legacy Code and Magic Buttons Part 1 3:22

35 weeks پیش3:22

3:22

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

Agile Tips

1
#30-Follow The Open-Closed Principle 3:50

36 weeks پیش3:50

3:50

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

Agile Tips

1
#29-Refactoring is Lean Pt. 2 3:44

37 weeks پیش3:44

3:44

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.

Agile Tips

1
#28-Refactoring is Lean Pt. 1 2:47

38 weeks پیش2:47

2:47

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.

Agile Tips

1
#27-Why Design Patterns are Agile 3:04

39 weeks پیش3:04

3:04

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.

Agile Tips

1
#26-Being Persuasive in Context 2:45

40 weeks پیش2:45

2:45

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.

Agile Tips

1
#25-Enumerate Your Stakeholders 2:55

41 weeks پیش2:55

2:55

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.

Agile Tips

1
#24-The Power of Lists Part 2 2:54

42 weeks پیش2:54

2:54

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.

Agile Tips

1
#23-The Power Of Lists Part 1 2:45

43 weeks پیش2:45

2:45

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.

Agile Tips

1
#22-Know What it Means to be Done 3:26

44 weeks پیش3:26

3:26

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.

Agile Tips

1
#21-Build Quality in Part 3 2:38

45 weeks پیش2:38

2:38

Part 3 of my analogy on product quality.

Agile Tips

1
#20-Build Quality In Part 2 2:06

46 weeks پیش2:06

2:06

Part 2 of my analogy on product quality.

Agile Tips

1
#19-Build Quality In Part 1 2:48

47 weeks پیش2:48

2:48

Part of the Agile approach, as well as the tenets of Lean, say to "build quality in." This seems wise, but what specifically is meant by "quality"? Also, how can we know if we have imbued our product with enough of the required qualities to make it releasable? The next three episodes will examine the notion of quality using a hopefully familiar analogy.…

به Player FM خوش آمدید!

Player FM در سراسر وب را برای یافتن پادکست های با کیفیت اسکن می کند تا همین الان لذت ببرید. این بهترین برنامه ی پادکست است که در اندروید، آیفون و وب کار می کند. ثبت نام کنید تا اشتراک های شما در بین دستگاه های مختلف همگام سازی شود.