The Starfish exercise is based on an evolution of the typical three questions that are used for retrospectives: “What went well?”, “What did not go so well?” and What will be improved?
Category: Digital Product Framework
An Agile Retrospective is a meeting that ́s held at the end of each iteration in Agile Development and it serves for the team to reflect on how to become more effective, so they can tune and adjusts its behavior accordingly.
People spend years trying to understand the importance of good design patterns, buy books about the right practices of the industry but most of the time they forget about the antipatterns, this blog post explains some of the most common mistakes that organizations do about the role of product owners.
Agile teams from around the world use the planning poker technique to estimate their product backlogs. Usually, the planning poker uses story points to estimate the complexity of a story and brings together multiple expert opinions for the estimation.
Agile Product Owner (PO), is responsible for managing the product backlog to achieve the team’s desired outcome. The PO role is a new and critical one.
The SCORECARD is based on our ADAPT Methodology™ – a Digital Product Development Framework, that provides leaders with a proven roadmap for building Digital Product Companies.
Sprint Review meeting is carried out once the Sprint has been done. It is meant to inspect the Increment and adapt the Product Backlog if necessary. When the Sprint Review meeting is taking place, the Scrum team and stakeholders evaluate what has been done during the Sprint. The review serves for sharing information, this is Learn More
The ADAPT Methodology™ is a Digital Product Development Framework, that provides leaders with a proven roadmap for building Digital Product Companies.
Scrum Pillars are essential mindshift that you have to make if you’re really want to successfully adapt the Agile framework.
Are you looking to appoint an external agile transformation firm to help with its agile transformation? This article explains you where to start!
High performing teams are groups of people who share a common vision, goals, and who collaborate and hold each other accountable to achieve great results.
Your Scrum Team should be very much familiar with Epic, User Story and Task. This blog post will explain these terms in Scrum work hierarchy.
This blog post explains several ScrumMaster Antipatterns that many companies face. In this specific blog post, I am tackling ScrumMaster Antipatterns.
Burndown chart is common, a useful tool used in sprint meetings to assess how much work has been completed on an assignment.
The Definition Of Done is the exit criteria that is used to determine whether a product backlog item is complete. The definition of “done” may vary from one Agile Team to another, but it must be consistent within one team.
The most simplified definition of Scrum Product Backlog is: ‘it is a list of all jobs that need to be done within the product’.
Scrum Master role – creating stable and self-organised teams with a clear and engaging direction, and educating the organisation on Agile Methodologies.
Nowadays, external Scrum Master is in high demand as companies finally embrace Agile. Becoming Agile is top of the agenda for many organisations.
Many people struggle to understand why adapting to Agile management style is so hard for executive managers. Check this article that explains this challenge.
This article describes a great exercise how to clarify Scrum Master responsibilities and how to do it within a 2-hour session with your team.