A survey says that 64% of the functionalities included in software products are never or almost never used! In this blog post, Emiliano Soldi shares some ideas on how to avoid this and prioritize user stories.
Agile Scrum backlog grooming and management
This post presents a structured and hierarchical product backlog board that considers non-functional requirements and display high priority items that are ready to code.
Some people want to take the stance that no work should be done in advance of the sprint. That is clearly untenable. To see why, let’s take that view to its extreme: If we did nothing in advance to understand what we’re building, we’d show up at the planning meeting and say, “Hey, what should we build this sprint? We were working on an eCommerce site yesterday, but I think maybe we should switch to writing a word processor…” The team would literally have nothing written down—no product backlog / user stories / prioritized feature list at all.
Dave Prior explains the concept of a product backlog.
The article “Managing the Pipeline” by Mary Poppendieck discuss the project planning and usage of resources. Exhorting workers to estimate more carefully and project mangers to be more diligent in meeting deadlines is not going to remove variation from projects. We need to change the rules of the game!