Inspect and Adapt – Détails, épisodes et analyse

Acceptance criteria are the criteria for acceptance, or so the helpful online definitions say. But what does that really mean? And is the common—almost universal—advice to write little functional snippets correct? Join Steve Tockey and Earl Beede as they Inspect & Adapt Acceptance Criteria. They'll take a look from several angles and suggest ways to make acceptance criteria much more useful for your projects. Hosted by Mark Griffin.

Project risk management was a critical part of well-run software development projects late in the last century. With the coming of agile development practices, however, risk management disappeared. Or did it? Steve Tockey and Earl Beede Inspect & Adapt the role of project risk management on modern development projects. They identify when it is still needed, where it is still happening, and how it can improve your project outcomes. Hosted by Mark Griffin. 

Why do software gurus keep talking about the Cynefin Framework? What is it? How is it even pronounced? In this episode of Inspect & Adapt, Construx puts many brains on the topic with Mark Griffin, Jenny Stuart, Steve Tockey, and Earl Beede making the link between Cynefin and doing actual software development work. They cover where Cynefin is best applied and where this sense-making system just doesn't make sense.

Most folks know that the product owner, scrum master, and developers make up the Scrum team, but did you know that these roles are also an accountability triad critical to scaling? In episode #52 of our Inspect & Adapt podcast, Construx’s Earl Beede and Jenny Stuart define the triad and describe its role in scaling agile. Earl and Jenny focus on how each abstraction level in a scaled agile deployment replicates the triad while maintaining the single point of truth (SPOT) rule for that level. They also identify some common pitfalls when the triad is not implemented well and help you see how the triad is a critical tool for your agility.

To be a professional usually means a commitment to ongoing professional development. Doctors, engineers, nurses, accountants, and teachers all require periodic training to maintain their professional status, but what constitutes professional development in software? Can we consider ourselves professional without it? The Construx team will look into the state of professional development in software and give their assessment.

The product owner is often considered the most critical accountability in the triad of <product owner, scrum master, developers>. Why? Because garbage in from the product owner gets garbage out of the developers, so it's crucial to give serious consideration to who is best to staff the product owner role. Listen to Construx experts share best practices, things to watch for, and stories from the field as they Inspect & Adapt the staffing of the product owner.

What do we do when we are faced with "The New"?  When something is new to us, it's harder to estimate, harder to plan, and harder to execute. Some development projects involve much more that is new than others. How do we identify the new and deal with it in a constructive way? In this episode of Inspect & Adapt, Construx's Mark Griffin, Steve Tockey, Earl Beede, and Jenny Stuart dive into ways to have the best development project when dealing with 'The New."

Why can't I know—with high precision—the final cost, scope, and time frame of my work effort? One of the biggest reasons you can't know all three at once is illustrated by Steve McConnell's Cone of Uncertainty. In this episode of Inspect & Adapt, Construx's Mark Griffin, Steve Tockey, and Earl Beede talk about what the Cone is, how it impacts your ability to estimate, and how you can use it to increase your estimate predictability. 

If hindsight is 20/20—and it's good practice to look back to find ways you could do better—then why do retrospectives seem like such a waste of time? Shouldn't they be a goldmine that we're excited about rather than just another obligatory meeting? Inspect & Adapt host Mark Griffin gathers fellow Construx staff, Steve Tockey, Jenny Stuart, and Earl Beede, to discuss how we can make retrospectives something to look forward to.

There is a lot of talk and ideas about how to scale agile up from the one-team, one-product base so that multiple teams can support a product (I am looking at you SAFe). But what about the case where one team must support multiple products? That is reverse agile scaling. Join Construx’s Mark Griffin, Jenny Stuart, and Earl Beede as they share strategies and proven techniques to have one team work with multiple products and multiple product owners.