Agile product development works--if you do it right. Despite its simple principles, executing them presents challenges to new and experiences agile practitioners alike. Many organizations start a move to agile with high hopes and enthusiasm, only to end up discouraged, frustrated, and ready to give up. Do these problems sound familiar? - Lack of planning and predictability in your agile projects - Teams that continually over or under commit - Product Owners that are ineffective or not engaged - Poorly written requirements - Inability to meet project deadlines If you have struggled with issues like these, 30 Days to Better Agile can help. In it, you will learn specific and targeted techniques for working through common problems every organization faces when moving to an agile model. This book is an indispensable resource for anyone looking to get the most value possible out of agile practices.
This was an incredibly helpful book. It was well structured which allows you to jump to certain points that you need to reference. One of the highlights of the book was that it not only gave you a scenario and fix, but it also explains why it happens in the first place.
Three stars because this book told me that a Sprint Review is for the PO to sign off on the “Done” work. However the actual goal of a Sprint Review is to show the stakeholders the new features from a user’s perspective so that 1) their feedback tells us if what we’re delivering is what they want and we can adapt quickly if not, and 2) we can adjust the backlog together if they decide, given this new work, they want other things that hadn’t been thought of previously.
I led my team in the wrong direction on Sprint Reviews for months until it was brought up in Retrospective that we seemed to just be reporting during these meetings. Then I went to Scrum.org and found out the mistake.
- Provides you with the basic terminology about Agile / Scrum - I absolutely loved the portion of the book devoted to undesired (Product Owner, SCRUM master, stakeholder, manager, SCRUM team) behaviors . Makes theory more tangible and understandable. - Examples, examples and more examples of red flags.
What I didn't like. - Nothing really - I wish there was a sequel!
Who can use this book. - Anyone starting off on their Agile / SCRUM path. - People who attended Angela's workshops - it's a must read.