Ideas and resources to make better decisions
Content to think better about AI, product, and technology.
Designed for professionals already working in the field.
Event: Sprint Planning
The Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint
Team: Product Owner
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team
Event: Sprint Review
The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations
Event: Sprint Retrospective
The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness
What is Scrum?
Scrum is a lightweight framework by which people, teams, and organizations create value through adaptive solutions to complex problems. - Scrum Guide
Team: Developers
The developers are the people on the Scrum Team who are committed to creating any aspect of a usable Increment in each Sprint
Event: Daily Scrum
The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work
Team
The fundamental unit of Scrum is a small team of people, a Scrum Team. The Scrum Team consists of a Scrum Master, a Product Owner, and the Developers
Team: Scrum Master
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization
Internal or external Product Owner?
Most of the information available on blogs, podcasts, and books on Product Management and Product Ownership focuses on commercial products aimed at end-users such as the cases of Airbnb, Uber, Rappi, Mercado Libre, etc.
The story of a product that was not selling
This year marks the 20th anniversary of the signing of the Agile Manifesto. It was a milestone that became a turning point for an entire industry. Today, twenty years later, I would like to comment on some things about it, but not about the agility and the manifesto (I think that much has already been saying about that) but about a divergent path that Product Management provides. For that, I am going to go back to my first major challenge in Product Management. It began in mid-2003 and lasted until the end of 2006. Yes, a long time ago (it is not worth taking accounts!).
Scrum Pillars
You don't learn by thinking. You learn by doing and observing. Knowledge is information; learning is action.