In this 2-part series, I'll be covering an issue I've seen several Agile teams face firsthand: how to stay Agile when developing mandated, compliance-based features. In Part 1  I'll look at ways to approach this type of work, including reducing risks, sustaining user value, and why reverting to a waterfall approach isn't the best answer. Part 2  looks at changes to the Product Manager's playbook. Part 1: When Outcomes Aren’t Incremental Story Time Early in my career, I had an

You wouldn’t tell someone they got a full night’s rest by taking eight one-hour naps at random times throughout the day. So why do we do something similar to our developers?

Earlier in my career, I worked with a team that, on paper, looked great. They had two-week sprints, predictable velocity, solid flow...

Processes that help your product, not become your product.

Letting users suffer to make customers happy.

Take me home, country road(map)s.