We were half-way in Sprint Planning and suddenly it hit me. Like a light bulb turning on. I had been listening to the discussion between the Developers and the Product Owner and all seemed normal… until this very moment. I just realized that the team was planning their sprint with absolute no idea of velocity or capacity. How did I
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
The main goal of the Scrum Master is to create a highly productive team that is self-organizing and continuously improving. They do this by acting as a servant leader, coaching the team when needed, and creating the space for team members to own their work, their decisions, and the opportunities for self-improvement. Many Scrum Masters act in the dark side.
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
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
The Scrum Master role in Scrum is one of the most important and often misunderstood. The creators of Scrum, Jeff Sutherland and Ken Schwaber, recognized that change is hard and in order for teams to be able to effectively transition to a new way of working (adopting Scrum) help was required in terms of coaching and support. So the Scrum
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 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
Scrum is an Agile framework for developing new products and extending existing ones with rapid cycles of incremental development and customer feedback
Solid Product management and discovery practices are at the foundation of any product development effort. I often find that when Agile fails, it’s not because “Agile” doesn’t work. It’s because the organization has not taken the rights steps to foster a product development mindset. Here I share a few tips on how to support Product and Agile transformations.