Hacker News new | ask | show | jobs
by ryanthedev 2546 days ago
Features and stories should be completable in the span of an iteration.

Epics and Features are prioritized by the business and product. They can be expected to slide from iteration to iteration.

Any User Story or task should be expected to be completed an a single iteration.

If you keep having open stories stop bringing in a complete story. Just assign tasks.

Features and Epics are pointed.

Business looks at points earned per year or quarter. Look for trend.

IT leadership looks at amount of open stories and tasks that were moved from iteration back to the backlog. Over the span of all iterations.

This will ensure teams are breaking down work into actionable goals.

2 comments

Good lord! Buzzword Bingo and Obfuscation at its finest!

Nothing personal, but you have just confirmed to me why i loathe the Agile/Scrum/[fad] processes so much. Take easily understood commonsense ideas/terms and invent fancy names for them, convert heuristics to axioms and sell a business around it.

So said the 2 day scrum master