Player FM - Internet Radio Done Right
Checked 9h ago
Đã thêm cách đây một năm
Nội dung được cung cấp bởi Scott L. Bain. Tất cả nội dung podcast bao gồm các tập, đồ họa và mô tả podcast đều được Scott L. Bain hoặc đối tác nền tảng podcast của họ tải lên và cung cấp trực tiếp. Nếu bạn cho rằng ai đó đang sử dụng tác phẩm có bản quyền của bạn mà không có sự cho phép của bạn, bạn có thể làm theo quy trình được nêu ở đây https://vi.player.fm/legal.
Player FM - Ứng dụng Podcast
Chuyển sang chế độ ngoại tuyến với ứng dụng Player FM !
Chuyển sang chế độ ngoại tuyến với ứng dụng Player FM !
Podcast đáng để nghe
TÀI TRỢ BỞI
M
Mind The Business: Small Business Success Stories


1 Pushing Past Stagnation & Business Plateaus 30:21
30:21
Nghe Sau
Nghe Sau
Danh sách
Thích
Đã thích30:21
Hitting plateaus is a common milestone in business, but there’s a difference between stability and a rut. In the last installment of this season, we’ll dive into the ways small business owners push beyond plateaus and find new ways to achieve revenue growth. Jannese and Austin wrap up their time in Nashville, Tennessee with a wonderful visit to N.B. Goods to speak with owner Camille Alston . Camille details the times where she hit a wall with profits, the strategies she implemented to increase revenue, what worked, what didn’t, and the important lessons she learned in the process. You won’t want to miss this informative final chapter! Learn more about how QuickBooks can help you grow your business: QuickBooks.com See omnystudio.com/listener for privacy information.…
#39-Do I Really Have to Test Everything? Third (and Final) Answer
Manage episode 454640429 series 3564249
Nội dung được cung cấp bởi Scott L. Bain. Tất cả nội dung podcast bao gồm các tập, đồ họa và mô tả podcast đều được Scott L. Bain hoặc đối tác nền tảng podcast của họ tải lên và cung cấp trực tiếp. Nếu bạn cho rằng ai đó đang sử dụng tác phẩm có bản quyền của bạn mà không có sự cho phép của bạn, bạn có thể làm theo quy trình được nêu ở đây https://vi.player.fm/legal.
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.
55 tập
Manage episode 454640429 series 3564249
Nội dung được cung cấp bởi Scott L. Bain. Tất cả nội dung podcast bao gồm các tập, đồ họa và mô tả podcast đều được Scott L. Bain hoặc đối tác nền tảng podcast của họ tải lên và cung cấp trực tiếp. Nếu bạn cho rằng ai đó đang sử dụng tác phẩm có bản quyền của bạn mà không có sự cho phép của bạn, bạn có thể làm theo quy trình được nêu ở đây https://vi.player.fm/legal.
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.
55 tập
Tất cả các tập
×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.

1 #50-Implications of the Agile Manifesto, Conclusions 5:22
5:22
Nghe Sau
Nghe Sau
Danh sách
Thích
Đã thích5: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.

1 #49-Implications of the Agile Manifesto, Part 4 3:05
3:05
Nghe Sau
Nghe Sau
Danh sách
Thích
Đã thích3:05
This week I will tackle the four point of the Agile Manifesto, with an eye toward my conclusion podcast next week.

1 #48-Implications of the Agile Manifesto, Part 3 3:07
3:07
Nghe Sau
Nghe Sau
Danh sách
Thích
Đã thích3: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.

1 #47-Implications of the Agile Manifesto, Part 2 3:31
3:31
Nghe Sau
Nghe Sau
Danh sách
Thích
Đã thích3:31
This week I will investigate part 2 of the Agile Manifesto, as part of my series of four podcasts on the subject.

1 #46-Implications of the Agile Manifesto, Part 1 3:09
3:09
Nghe Sau
Nghe Sau
Danh sách
Thích
Đã thích3:09
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.
A
Agile Tips

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.
A
Agile Tips

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.
Part 3 of my analogy on product quality.
Part 2 of my analogy on product quality.
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.…
A
Agile Tips

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.
A
Agile Tips

1 #17-Acceptance: A Tale of Requirements And Their Meaning 5:56
5:56
Nghe Sau
Nghe Sau
Danh sách
Thích
Đã thích5: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.
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.
A
Agile Tips

1 #15-Agile Comes From a Shift in Systems Criticality 2:48
2:48
Nghe Sau
Nghe Sau
Danh sách
Thích
Đã thích2: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.
A
Agile Tips

1 #14-Share With Colleagues the King Henry School of Argument 3:00
3:00
Nghe Sau
Nghe Sau
Danh sách
Thích
Đã thích3: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.
A
Agile Tips

1 #13-Assess the Business Process Impact of New Projects 3:53
3:53
Nghe Sau
Nghe Sau
Danh sách
Thích
Đã thích3: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.…
A
Agile Tips

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.…
A
Agile Tips

1 #11-TDD Enhances QA But Does Not Replace it 2:50
2:50
Nghe Sau
Nghe Sau
Danh sách
Thích
Đã thích2: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.
A
Agile Tips

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.
A
Agile Tips

1 #39-Do I Really Have to Test Everything? Third (and Final) Answer 4:55
4:55
Nghe Sau
Nghe Sau
Danh sách
Thích
Đã thích4: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.
A
Agile Tips

1 #38-Do I Really Have to Test Everything? Second Answer 3:25
3:25
Nghe Sau
Nghe Sau
Danh sách
Thích
Đã thích3: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.
A
Agile Tips

1 #37-Do I Really Have to Test Everything? First Answer 3:24
3:24
Nghe Sau
Nghe Sau
Danh sách
Thích
Đã thích3:24
This is my first answer to the question posed last week. There will be two more in future weeks.
A
Agile Tips

1 #36-Do I Really Have to Test Everything? Introduction 3:27
3:27
Nghe Sau
Nghe Sau
Danh sách
Thích
Đã thích3: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.
A
Agile Tips

1 #35-The Principle of the Useful Illusion Part 2 3:19
3:19
Nghe Sau
Nghe Sau
Danh sách
Thích
Đã thích3: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.
A
Agile Tips

1 #34-The Principle of the Useful Illusion Part 1 4:37
4:37
Nghe Sau
Nghe Sau
Danh sách
Thích
Đã thích4: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.…
A
Agile Tips

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.
A
Agile Tips

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.
A
Agile Tips

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.…
A
Agile Tips

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.
A
Agile Tips

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.
A
Agile Tips

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.
Chào mừng bạn đến với Player FM!
Player FM đang quét trang web để tìm các podcast chất lượng cao cho bạn thưởng thức ngay bây giờ. Đây là ứng dụng podcast tốt nhất và hoạt động trên Android, iPhone và web. Đăng ký để đồng bộ các theo dõi trên tất cả thiết bị.