Agile is a now mainstream method used in IT project management. Yes, Agile and Scrum are now considered as a method and no longer as a philosophy. Everyone wants to “do” Agile and thus want to “be” Agile as well, but what are the common mistakes in applying Agile?
There’s a debate raging in the Agile world around the #NoEstimate concept: should we estimate, or not? Lost in the noise are more important questions: When should we estimate, and why? When should we not estimate, and why not?
The product owner is a very important component in a Scrum team, as it is the force driving the team towards the satisfaction of the end-user needs. This is a different situation if you are in a small startup or responsible for a large, established product line. In this blog post, Roman Pichler discusses the differences between small and big product owners.
One of the most important, and often overlook, sentence in the principles of the Agile Manifesto is “continuous delivery of valuable software”. Delivering value is an important principle for Agile and prioritization is the tool that allows to deliver value quickly. This is the topic discussed by Daniel Zacarias in his article “20 Product Prioritization Techniques: A Map and Guided Tour”.