Player FM - Internet Radio Done Right
Checked 1d ago
اضافه شده در one سال پیش
محتوای ارائه شده توسط Scott L. Bain. تمام محتوای پادکست شامل قسمتها، گرافیکها و توضیحات پادکست مستقیماً توسط Scott L. Bain یا شریک پلتفرم پادکست آنها آپلود و ارائه میشوند. اگر فکر میکنید شخصی بدون اجازه شما از اثر دارای حق نسخهبرداری شما استفاده میکند، میتوانید روندی که در اینجا شرح داده شده است را دنبال کنید.https://fa.player.fm/legal
Player FM - برنامه پادکست
با برنامه Player FM !
با برنامه Player FM !
پادکست هایی که ارزش شنیدن دارند
حمایت شده
B
B2B Agility with Greg Kihlström™: MarTech, E-Commerce, & Customer Success


1 #52: Navigating the effect of AI on marketing jobs and the job market with Sue Keith, Landrum Talent Solutions 19:09
This episode is brought to you by Landrum Talent Solutions, a national recruiting firm specializing in marketing and HR positions. Our guest today has been keeping us up to date with the current state of hiring for marketers on a quarterly basis, which has taken us on quite a roller coaster ride. Today we’re going to look at how marketing and communication execs are responding to the latest developments in the world while still needing to get their work done. To take a look at the latest here, I’d like to welcome back to the show Sue Keith, Corporate Vice President at Landrum Talent Solutions. About Sue Keith Sue Keith is Corporate Vice President at Landrum Talent Solutions. With deep expertise in navigating complex labor markets, Sue has a front-row seat to the evolving dynamics of marketing roles, hiring trends, and the broader implications of AI and economic uncertainty. RESOURCES Landrum Talent Solutions: https://www.landrumtalentsolutions.com Catch the future of e-commerce at eTail Boston, August 11-14, 2025. Register now: https://bit.ly/etailboston and use code PARTNER20 for 20% off for retailers and brands Online Scrum Master Summit is happening June 17-19. This 3-day virtual event is open for registration. Visit www.osms25.com and get a 25% discount off Premium All-Access Passes with the code osms25agilebrand Don't Miss MAICON 2025, October 14-16 in Cleveland - the event bringing together the brights minds and leading voices in AI. Use Code AGILE150 for $150 off registration. Go here to register: https://bit.ly/agile150 Connect with Greg on LinkedIn: https://www.linkedin.com/in/gregkihlstrom Don't miss a thing: get the latest episodes, sign up for our newsletter and more: https://www.theagilebrand.show Check out The Agile Brand Guide website with articles, insights, and Martechipedia, the wiki for marketing technology: https://www.agilebrandguide.com…
#08-TDD Captures Institutional Knowledge Permanently
Manage episode 416826314 series 3564249
محتوای ارائه شده توسط Scott L. Bain. تمام محتوای پادکست شامل قسمتها، گرافیکها و توضیحات پادکست مستقیماً توسط Scott L. Bain یا شریک پلتفرم پادکست آنها آپلود و ارائه میشوند. اگر فکر میکنید شخصی بدون اجازه شما از اثر دارای حق نسخهبرداری شما استفاده میکند، میتوانید روندی که در اینجا شرح داده شده است را دنبال کنید.https://fa.player.fm/legal
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.
68 قسمت
Manage episode 416826314 series 3564249
محتوای ارائه شده توسط Scott L. Bain. تمام محتوای پادکست شامل قسمتها، گرافیکها و توضیحات پادکست مستقیماً توسط Scott L. Bain یا شریک پلتفرم پادکست آنها آپلود و ارائه میشوند. اگر فکر میکنید شخصی بدون اجازه شما از اثر دارای حق نسخهبرداری شما استفاده میکند، میتوانید روندی که در اینجا شرح داده شده است را دنبال کنید.https://fa.player.fm/legal
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.
68 قسمت
همه قسمت ها
×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.
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.
A
Agile Tips

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

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

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

Most of us do not ask "why" enough. Let's look at the effects of this problem, and what to do about it.
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.
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.
به Player FM خوش آمدید!
Player FM در سراسر وب را برای یافتن پادکست های با کیفیت اسکن می کند تا همین الان لذت ببرید. این بهترین برنامه ی پادکست است که در اندروید، آیفون و وب کار می کند. ثبت نام کنید تا اشتراک های شما در بین دستگاه های مختلف همگام سازی شود.