User Stories are not requirements

User Stories are not requirements

I always struggle with the word “requirements”. This is how specifications and functionalities are normally called when working on a project. Requirements create a blanket of necessity and limit the empowerment of product managers to be effective at solving problems. The word requirement, and its verb counterpart to require, in their essence define something that is “required”, “needed”, “expected”. The

Quick guide to Kanban

We wanted to provide a quick guide to Kanban including a list of resources to learn about what Kanban is and how to get started with Kanban. What is Kanban? (David Peterson) What is Kanban? (Atlassian) How to Create a Kanban Board for Any Project How To Create An Efficient Kanban Board/Process 32 Practical Kanban Board Examples Kanban Tools The

The Scrum Master’s reading list

Books This is a short list of great books on Agile, Scrum, and practices to become an effective Scrum Master. Scrum and Agile foundations “Essential Scrum: A Practical Guide to the Most Popular Agile Process“, by Kenneth Rubin “Your Scrum Playbook”, Fabian Schwarts, CST Scrum Master stories “Scrum Mastery: From Good to Great Servant-Leadership”, Geoff Watts, CST “Scrum: The Art

The Product Manager’s reading list

We have compiled a list of books and articles on Agile, Product, Design Thinking, and Innovation. These books and articles offer perspectives, frameworks, and real stories for the successful application of product management practices to the ideation and development of new products. If you are a Product Owner, a Product Manager, or a Product Leader, these books and articles are

Engineering practices

Building quality-in and keeping technical debt in check are two of the most important goals to support long-term sustainable product development. Adopting the right engineering practices allows teams to focus on innovation and value delivery, rather than wasting time on fixing problems or avoiding quality issues. BookingBug faced a near-death situation when it had accumulated too much technical debt due

Technical debt is a silent enemy of every product team

Technical debt is the silent enemy of every product team. Product development activities are hectic, as teams try to jam as many features as possible into a single release, and as the business pushes for higher productivity. At times, development teams make shortcuts as they push for a deadline; make architectural choices to fit into the current environment and delay