#41-Agile Architecture-SOA AND SAAS

Agile Tips

Player FM - Internet Radio Done Right

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

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

Our Skin: A Personal Discovery Podcast

1
You Are Your Longest Relationship: Artist DaQuane Cherry on Psoriasis, Art, and Self-Care 32:12

26 روز پیش32:12

پخش در آینده

لیست ها

پسندیدن

دوست داشته شد

32:12

DaQuane Cherry was once the kid who wore a hoodie to hide skin flare-ups in school. Now he’s an artist and advocate helping others feel seen. He reflects on his psoriasis journey, the power of small joys, and why loving yourself first isn’t a cliché—it’s essential. Plus, a deep dive into the history of La Roche-Posay’s legendary spring. See omnystudio.com/listener for privacy information.…

حدود یک سال پیش 2:55

MP3•خانه قسمت

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.

69 قسمت

#Tech #Scott Bain

#41-Agile Architecture-SOA AND SAAS

Agile Tips

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

اشتراک گذاری

MP3•خانه قسمت

69 قسمت

#Tech #Scott Bain

همه قسمت ها

1
#68-Shift left - Conclusions 4:04

21 hours پیش4:04

4:04

This week I will wrap up the notion of Shift Left, and introduce the next topic for this podcast.

1
#67-Shift left - Detecting Defects During Analysis 3:47

۸ روز پیش3:47

3:47

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.

1
#66-Shift left - Detecting Defects During Design 3:28

15 روز پیش3:28

3:28

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.

1
#65-Shift left - Detecting Defects During Implementation 3:57

22 روز پیش3:57

3:57

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.

1
#64-Shift left - Detecting Defects During Integration 3:30

29 روز پیش3:30

3:30

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.

1
#63-Shift left - Detecting Defects During Testing 3:51

۵ weeks پیش3:51

3:51

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.

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

۶ weeks پیش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.

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

۷ weeks پیش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.

1
#60-Shift Left - Introduction 3:25

۸ weeks پیش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.

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

۹ weeks پیش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.

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

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

1
#57-Requirements vs. Expectations 3:41

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

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

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

1
#55 - Measureing Agile Progress Effectively 4:36

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

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

14 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

15 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

16 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

17 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

18 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

19 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

20 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
#48-Implications of the Agile Manifesto, Part 3 3:07

21 weeks پیش3:07

3:07

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.

Agile Tips

1
#47-Implications of the Agile Manifesto, Part 2 3:31

22 weeks پیش3:31

3:31

This week I will investigate part 2 of the Agile Manifesto, as part of my series of four podcasts on the subject.

Agile Tips

1
#46-Implications of the Agile Manifesto, Part 1 3:09

23 weeks پیش3:09

3:09

This week I'll examine the first point in the Agile Manifesto, as part of a series of four podcasts.

Agile Tips

1
#45-Implications of the Agile Manifesto 3:00

24 weeks پیش3:00

3:00

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.

Agile Tips

1
#44-Maintain an Organizational Glossary 2:51

25 weeks پیش2:51

2:51

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.

Agile Tips

1
#43-The Four Quadrants of Requirements 4:41

26 weeks پیش4:41

4:41

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.

Agile Tips

1
#42-The Agile Use of Inheritance 3:45

27 weeks پیش3:45

3:45

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.

Agile Tips

1
#41-Agile Architecture-SOA AND SAAS 2:55

28 weeks پیش2:55

2:55

Agile Tips

1
#40-Writing Specifications as Tests 3:35

29 weeks پیش3:35

3:35

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.

Agile Tips

1
#39-Do I Really Have to Test Everything? Third (and Final) Answer 4:55

33 weeks پیش4:55

4:55

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.

Agile Tips

1
#38-Do I Really Have to Test Everything? Second Answer 3:25

34 weeks پیش3:25

3:25

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.

Agile Tips

1
#37-Do I Really Have to Test Everything? First Answer 3:24

35 weeks پیش3:24

3:24

This is my first answer to the question posed last week. There will be two more in future weeks.

Agile Tips

1
#36-Do I Really Have to Test Everything? Introduction 3:27

36 weeks پیش3:27

3:27

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.

Agile Tips

1
#35-The Principle of the Useful Illusion Part 2 3:19

37 weeks پیش3:19

3:19

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.

Agile Tips

1
#34-The Principle of the Useful Illusion Part 1 4:37

38 weeks پیش4:37

4:37

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

Agile Tips

1
#33-Product Confusion Reveals Coupling 3:17

39 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

40 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

41 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

42 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

43 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

44 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

45 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

46 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

47 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
#09-TDD Improves Product Design Quality 3:02

1 year پیش3:02

3:02

TDD is a process that produces multiple values for the organization. One of them is a fundamental improvement in the quality of the products they produce. This is not just because of the testing per se, but also because of the effect of writing them up front. This episode explains why.

Agile Tips

1
#08-TDD Captures Institutional Knowledge Permanently 2:16

1 year پیش2:16

2:16

How can we keep track of the behavior of systems as they change over time? We must do this, or critical enterprise knowledge can be lost, at potentially great cost going forward. This episode is about how TDD solves this problem.

Agile Tips

1
#07-TDD Will Increase Development Velocity 3:16

1 year پیش3:16

3:16

This tip is one of four that elucidate the benefits of TDD, so that those whose approval is needed for adopting this way of working will understand why it should be done. This week, the issue is increasing team velocity.

Agile Tips

1
#06-Know the Benefits of Test-Driven Development 2:39

1 year پیش2:39

2:39

Adopting TDD initially can involved overcoming the objections of others in your organization. In this episode, and the next few that follow, we will examine these concerns and how to address them

Agile Tips

1
#05-A Thought Framework for Risk Assessment 4:50

1 year پیش4:50

4:50

Good design and process seeks to reduce or eliminate risks, but we all know that it is impossible to act completely risk-free. Because of this, we need a way to assess those risks we cannot prevent, in order to determine what, if anything, to do about them. This podcast will offer an effective way to do that, collaboratively…

Agile Tips

1
#04-Martin Fowler Says Ignore Your Mother 3:16

1 year پیش3:16

3:16

Somethings are known before we begin a project, but many things are not. We need to balance our process between decisions that cannot or should not be deferred, and those that it is better to wait on. This episode all about that balance.

Agile Tips

1
#03-Always Ask Why 3:39

1 year پیش3:39

3:39

Most of us do not ask "why" enough. Let's look at the effects of this problem, and what to do about it.

Agile Tips

1
#02-Don't Choose ATDD Automation Tools Up Front 3:01

1 year پیش3:01

3:01

Acceptance test can be made executable by an automation framework. But you should not choose one at the beginning of your adoption of ATDD. Here's why.

Agile Tips

1
#01-Don't Trust Code Coverage Measurements 2:20

1 year پیش2:20

2:20

Many tech leaders and project managers are mandating a minimum level of code coverage by developers. They believer this ensures a level of quality and reliability in the product but this is a fallacy. Hear why.

Agile Tips

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

48 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

49 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

50 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

51 weeks پیش2:38

2:38

Part 3 of my analogy on product quality.

Agile Tips

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

1 year پیش2:06

2:06

Part 2 of my analogy on product quality.

Agile Tips

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

1 year پیش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.…

Agile Tips

1
#18-Understand What A Good Test Is 3:50

1 year پیش3:50

3:50

TDD can help you to improve your product design for many reasons. One of them is that it is difficult, if not impossible to write a good test for a bad design. But what is a good test? How would we know if it's good in the right sense? That's what this episode will explain.

Agile Tips

1
#17-Acceptance: A Tale of Requirements And Their Meaning 5:56

1 year پیش5:56

5:56

This episode relates a story that an ex-student and current colleague of mine related to me over lunch. I felt it was an extremely revealing and useful example of how requirements are misunderstood, the disasters than can result, and what to do about this.

Agile Tips

1
#16-Keep Scenarios Small 3:22

1 year پیش3:22

3:22

Scenarios, like requirements, can often be too large to work with effectively. In this episode we'll examine why this is a problem, and some example of how we can deal with it.

Agile Tips

1
#15-Agile Comes From a Shift in Systems Criticality 2:48

1 year پیش2:48

2:48

The world has changed, and so has the technology we use to automate it. But a lot of the traditions that guide our efforts to control automation projects are based on the realities that existed in the past. Agile is a response to this, and this episode is all about why, and how this is so.

Agile Tips

1
#14-Share With Colleagues the King Henry School of Argument 3:00

1 year پیش3:00

3:00

When collaborating with others, sometimes you will encounter reticence to ask or answer important questions. There are a number of reasons for this, but in this episode I will outline an approach I take to counter this, one which has served me well in multiple occasions.

Agile Tips

1
#13-Assess the Business Process Impact of New Projects 3:53

1 year پیش3:53

3:53

When creating something new of value, one must always consider the context within which it will operate. Part of this is determining what, if anything, in the existing business processes will be effected by the new work. Failing to take this into account can have serious consequences, as this episode will demonstrate.…

Agile Tips

1
#12-Sharpen Your Analysis Skills with CVA 2:56

1 year پیش2:56

2:56

Analysis is a fundamental part of system's development. It is also one of the most difficult things to do right, and since everything that follows is based on it we need multiple skills to do it correctly. Commonality-Variability Analysis, as suggested in the work of James O. Coplien, is a remarkably powerful approach to conducting requirements analysis.…

Agile Tips

1
#11-TDD Enhances QA But Does Not Replace it 2:50

1 year پیش2:50

2:50

Test-Driven Development (TDD) is not really a testing activity per-se, but an analysis process that drives product design. That said, although it does not eliminate the need for after-development testing (QA/QC), it does contribute to that process. This episode will show why this is.

Agile Tips

1
#10-TDD Improves Collaboration 2:30

1 year پیش2:30

2:30

One of the benefits of Test-Driven Development is the way is enhances our ability to collaborate effectively. This is especially true if you include Acceptance Testing as part of the way of working. This episode is all about this.

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

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