Confessions of a serial product owner is a short guide to a business person aiming for becoming an excellent product owner in Agile and Scrum projects. It was written in 2009 and is based on the personal experience of Anna Forss.
Articles, Blog Posts, Books and Quotes on Agile Project Management
Shifting responsibilities from a “command and control” organization towards self-organized teams is not easy. In her article “Managing Product Teams for Success”, Teresa Torres discusses the challenges that you face when you try manage product teams by outcomes.
When an approach or a technology reach the hype level, then every IT solutions provider include it in the description of what it offers. This is today the case for Agile and Scrum in software development. This is why the Defense Innovation Board (DIB) has worked on a document to help US Department of Defense (DoD) agencies to detect Agile bullshit.
One of the trends associated with the Agile approach is the shift from “building the software right” to “building the right software”. This translates in putting more emphasis on collaborative product definition activities and quicker feedback. The Minimum Viable Product (MVP) is an approach that tries to elicit quick customer feedback while providing him with a working product. In his book Lean Inception, Paulo Caroli proposes a workshop-based recipe to build the MVP canvas.
The Product Owner is a key component of Scrum teams as the role a major influence on software development projects. It is however not always possible for the Agile team to get access to a full-time qualified Product Owner. This is why Marcelo Leonetti discusses in this article some situations where a Product Owner proxy could help Scrum teams solve some problems.
Projects have been the main working mode of software development activities since the beginning of computers. According to Allan Kelly, it is however not the best mode to develop software. He fosters the #noproject movement to fight project myopia that he defines as the “belief that the project model is the only way of managing business change and development.”
As the Agile Manifesto stated that it prefers “working software over comprehensive documentation”, some early Agile adopters jumped to the conclusion that documentation was useless. Thus Scrum software developers should only concentrate in creating working software with code that was the most easier to understand.