A Scrum team cannot deliver value without a good Product Owner. This is for me the most important role and it is not easy to keep an Agile balance between a long term business vision that could lead the team to success and the ability to adapt to change after receiving customer feedback. In this article, Zuzi Šochová shares a list of the most common mistakes made by Product Owners.
Articles, Blog Posts, Books and Quotes on Agile Project Management
It all starts with doing the right thing. Agile has not changed the old computer wisdom of “garbage in, garbage out”. This is why Allan Kelly last book is dedicated to the art of Agile product ownership. As he wrote: “If a Scrum Master performs badly, the team simply fails to perform well. If the Product Owner performs badly, the whole product is in jeopardy”.
We all know that there are three roles in Scrum teams : product owner, scrum master, and the development team. Modern software development can sometimes require some specializations that could be beyond the capabilities of the Scrum team members. UX and Web design, database administration, performance testing are some examples of activities that requires specific expertise only for a limited amount of time. How do you deal with it?
The Kenneth Rubin’s “Essential Scrum” book starts with a foreword by Mike Cohn who writes “there must be billions of possible ways to implement Scrum. And while there is no single right way, there are better and worse ways to implement Scrum.” Mike Cohn writes also “what works in one company or project will fail in another”. The presence of Mike Cohn in this book is not a surprise as Kenneth Rubin hired him in 2000 to work on the implementation of Scrum at Genomica.
T-shaped skills is a metaphor used to describe people with deep vertical skills in a specialized area as well as broader but not necessarily deep skills in other areas. This is a base for cross-functional Scrum teams, but people can resist this. Learn why and what you can do to change this.
The ScrumMaster role is certainly the most original addition of Scrum to the concept of software development teams. How and how much the ScrumMaster should be involved with the teams is a topic for debates in the Agile community. Isn’t the Scrum team supposed to be self-organized in the first place? In this article, Zuzi Šochová, author of The Great ScrumMaster, shares her opinion on some of the common mistakes made by ScrumMasters.
Sometimes, organizations adopting an Agile approach are mostly following Scrum practices like rituals. They might do daily stand-up meetings but do not perceive that the real goal is to deliver quickly value to the customer. In an article, Vinod Santhanam explains how the Value-Oriented Incremental Delivery (Void) approach can help Agile teams to achieve this goal.