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.
Product backlog is not documentation
Keep product documentation somewhere else - use Google Docs, Notion, Miro, GIT, Sphinx or any other tool. Don’t use tasks as documentation.
Please, keep product documentation somewhere else – use Google Docs, Notion, Miro, GIT, Sphinx or any other tool.
BUT don’t use tasks as documentation. Even if you write a great specification, once task is closed -> no one will open it again.
Imagine to search something after a few months, with all the change requests. No way.
By Lubos Schramek on September 23, 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 is not excuse for POOR quality
By Lubos Schramek on September 30, 2020 in the Agile notes
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.
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