What are the Agile Engineering Skills, Scrum Developer Practices, or Software Craftsmanship practices?

I was co-training an Agile for Teams workshop with Rob Myers last week. This group had been trying to do Scrum, with some success. Our job was to help them solidify their Scrum practice. I love workshops like these. There’s enough knowledge and experience in the room that if willing to learn, can create a

As I train and coach Scrum across the country, I’m often struck with the power how certain words can create a sense of fear in people. In my experience, no word creates as much fear as ‘commitment’. Yet commitment is one of the five Scrum Values per the Scrum Guide! IMHO, that’s a problem.

I’m a pragmatist. I need things to make sense. So, when something like principles are introduced to me, I start to ponder questions like… What is a principle? Where did these principles come from? Are all these really principles? How do these principles relate to each other? Why should I care? Etc. Yep, I can

My Scrum team has been working on a particular service for over a year. It’s been 20+ Sprints. I’m concerned about the deliverables and the rate at which we deliver. I have just put together some material for my stakeholders. I am pasting those slides here for your review. Do you mind reviewing

A key part of the ScrumMaster’s or Product Owner’s job is making information visible.* Whether that’s a product backlog, taskboard, cumulative flow diagram, or a one-off visual for a specific need, good visuals lead to better decisions. Here are four principles for doing it

Workflows are a very common element of software. But they can be hard to split well when you’re trying to work in small, vertical slices because the most obvious split turns out to be wrong. In this video from my 80/20 Product Ownership online course, I explain why the obvious approach is wrong and