Agile and documentation are not two words that are often associated in articles or blog posts. Scrum teams have however to find alternate ways to spread the knowledge among their member. In this article, Viktor Cessan explains how he uses an exercise named History Lines to share knowledge in Agile teams.
Articles, Blog Posts, Books and Quotes on Agile Project Management
Fifty Quick Ideas to Improve your User Stories is another book from Gojko Adzic, a consultant and author that already produced some very good books on Agile requirements like Impact Mapping and Specification by Example. It goal is to help people involved with Agile requirements to improve their discussion with the stakeholders and the planning activities associated with user stories. This is clearly not a book for beginners on how to write user stories.
How can you achieve a modern Agile organization? Starting from the description of the version 1.0 and 2.0 of organizations, Zuzi Šochová explains how to transition to a new Agile work organization that relies team and communication more than on individuals.
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.
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.