Archive for the ‘Agile’ Category

Estimating Placeholder Stories is a Bad Practice

0 comments

Placeholder stories, in general, are a bad idea. Estimating placeholder stories to reserve capacity or to get credit is a very bad idea. Define “Placeholder Stories” Of course, all stories are “placeholders for a conversation”, but that’s not what I’m talking about here. I am also not talking about things like “Refactor the such-n-such class as we start work on […]

read more

Story Splitting: Where Do I Start?

0 comments

I don’t always follow the same story splitting approach when I need to split a story. It has become intuitive for me so I might not be able to write about everything I do or what goes through my mind or how I know. But I can put here what comes to mind at the […]

read more

Agile Teams in the Enterprise

0 comments

Once you have clarified why you are transforming your organization to become agile, it’s time to set up your agile teams. With the growth of agile over the last decade, most people are familiar with the delivery team structure of 6-8 cross-functional professionals with the all tools and skills needed to deliver value on the […]

read more

How Many Stories Per Sprint? Rules of Thumb

0 comments

I’m often asked how many user stories you should have in a sprint and how big is too big for a story. People are looking for guidance. Stories per Sprint I’ve heard some coaches recommend “3-6 stories per iteration per developer”. That’s a bad rule of thumb. For a team of 7 developers you would […]

read more

Use Metrics to Tell a Story

0 comments

Agile delivery practices use metrics as a foundation to quantify the unpredictable nature of understanding what someone has in mind. Stories are a set of words that convey an idea and translate one person’s imagination into an imaginary format called software. Given that we can debate what the definition of “is” is, estimating when some […]

read more
1 2 38