Backlog Structure | 20-30-50 rule
By Lubos Schramek on October 27, 2020 in the Agile notes
What is the right level of detail for product backlog? 20/30/50 rule by Bob Gales gives you guideline on how to structure product backlog.
Agile is not excuse for POOR quality
the Triple Constraint; success of your product is impacted by cost (budget), time (deadlines) and scope (features).
As product manager you can trade between these three constraints.
VALUE = A value proposition is a promise of value to be delivered. It’s the primary reason a prospect should buy your product.
QUALITY = It describes the degree to which we elegantly meet user needs in terms of completition, usability, efficiency, scalability, adaptability, reliability, etc.
Quality and Value are not-negotiable
the Triple Constraint
CONSTRAINTS = the Triple Constraint; success of your product is impacted by budget, deadlines and features.
As product manager, you can trade between these three constraints.
However, changing the constraints of one means that the other two will suffer to some extent.
- Cost: The financial constraints of a product, also known as the budget
- Scope: The tasks required to fulfill the product’s goals
- Time: The schedule for the project to reach completion
By Lubos Schramek on September 30, 2020 in the Agile notes
Related posts to Agile notes
Agile is not an excuse for a lack of Roadmap
By Lubos Schramek on October 01, 2020 in the Agile notes
Agile teams must absolutely know where they are going... and the goals they want to achieve must be clear.
Agile ≠ Dogma
By Lubos Schramek on September 29, 2020 in the Agile notes
You are not agile if you dogmatically follow process (even specific agile framework) – instead of adapting your activities in order to achieve your goals
Product backlog is not documentation
By Lubos Schramek on September 23, 2020 in the Agile notes
Keep product documentation somewhere else - use Google Docs, Notion, Miro, GIT, Sphinx or any other tool. Don’t use tasks as documentation.