Teams that have mastered Scrum know that the key to success lies in a just-in-time, increasingly refined, breakdown of work on the Product Backlog. They prefer Sprint Backlogs with many small (functional) items instead of just a few large ones. Smaller items improve flow and reduce the risk of failing the sprint. In this article, I will explain why the breakdown of work is important, and why it should be done across functional — instead of technical — boundaries. Christiaan Verwijs offers 10 useful strategies that experienced Scrum Teams use to break down work in this article: https://medium.com/the-liberators/10-powerful-strategies-for-breaking-down-user-stories-in-scrum-with-cheatsheet-2cd9aae7d0eb
Just a site where I archive interesting reads I've encountered online