Tag archive: user stories

Process Scale Invariance: UML Diagramming

I wrote a book on how to organize all the information about your product, from random user notes to testable code. By putting everything in terms of information management, it turns out a bunch of other things come into focus… continue reading »

Top Five Reasons You’re Wrong About Needing a Large Backlog

Most of these happen because people are confused about what, exactly, a backlog should be in an Agile environment. But we have a lot of work to do! – You are confusing activity with value. Backlogs measure value, not activity.… continue reading »

Technical Story Slicing 3 of 3

Too many times user stories and backlogs are taught at such a high level of abstraction that folks can’t get value from them. So let’s take a real project, developed on AWS using Microservices, and walk though how the backlog… continue reading »

Technical Story Slicing 2 of 3

Too many times user stories and backlogs are taught at such a high level of abstraction that folks can’t get value from them. So let’s take a real project, developed on AWS using Microservices, and walk though how the backlog… continue reading »

Technical Story Slicing 1 of 3

Too many times user stories and backlogs are taught at such a high level of abstraction that folks can’t get value from them. So let’s take a real project, developed on AWS using Microservices, and walk though how the backlog… continue reading »

Destroy The Agile Clubhouse!

I’ve seen a lot of team environments, and I don’t have the perfect answer for what’s right for your team. There. Got that out of the way. But I do believe that if you want to maximize creativity and the… continue reading »

Agile Value Dark Horse: What’s Your Backlog Pattern?

When teaching Agile, you usually throw up a chart that looks something like this overview of Agile Value: You talk about how each project, the Agile/iterative one and the Waterfall one, may deliver the same value at the end, but… continue reading »

Agile Backlogs. Sigh.

What a mess Frederick Taylor created. We can’t blame him completely, of course. He was just an engineer born in the mid 1800s who asked a simple question: “Why don’t we break up industrial processes into smaller and smaller pieces… continue reading »