One of the pillars of the ADAPT Methodology™ is the Agility part, that`s why talking about Agile Transformation Mistakes is very important! In this blog post, we make you aware of 14 common Agile Transformation Mistakes that you must avoid at any cost! If you are an executive leader looking to ADAPT your company Learn More
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.
When starting an Agile Implementation good agile consulting firms are mandatory, this article explains to you what you should look for when hiring one, so that you do not run into troubles.
Learn how a single release workflow known as the Continuous Delivery Pipeline enables digital product companies to deliver new features to users fast and efficiently.
During this decade, several companies embrace the need for an Agile Transformation but most of the leaders do not know where to start. In this article, you can find a suggestion where to start and what kind of activities you should take into consideration to run a successful Agile Transformation.
The Sailboat exercise helps teams to define a vision of where they want to go; it helps them to identify risks during their path and allows them to identify what slows them down and what helps them to achieve their objectives.
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?
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 sprint review is an informal meeting where the team gives a demo of the product and will determine what is finished and what isn’t, in other words, is a meeting to demonstrate and determine the usability of a piece of software.
Scrum Pillars are essential mindshift that you have to make if you’re really want to successfully adapt the Agile framework.
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.
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 term “definition of done” (also known as “DoD”) refers to the criteria that must be met in order for a task or feature to be considered complete in an agile development product.
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.