Publisher: Pragmatic Bookshelf, 2006, 155 pages
Project retrospectives help your teams examine what went right — and what went wrong — on a project. Traditionally, though, retrospectives (also known as postmortems) are held only at the end of the project, too late to help. You need agile retrospectives that are iterative and incremental. You need to accurately find and fix problems to help the team — today.
This book will help you uncover and solve hidden — and not-so-hidden — problems with your technologies, your methodology, and those difficult "people issues" on your team. You'll see how to mine the experience of your software development team continually throughout the life of the project.
You'll be able to fix the problems you and your team face every day.
You'll discover how to construct retrospectives in general, how to design them specifically for your team and organization, how to make them run effectively, how to make any necessary changes, and how to scale these techniques. You'll learn how to deal with problems, and implement solutions effectively throughout the project — not just at the end.
This book will help you:
Funny thing, this is more a book that can be seen as a handbook on how to conduct Workshops, but I expect that it can re-used to do retrospectives for the Agile community.
Truth to be told, this is a common theme in this community, they believe that no-one will detect that they are using old stuff or re-inventing the stuff, as long as they re-brand it.
That said, for a Workshop guide, it is OK.
There are currently no comments