!!!STOP PRESS!!! SPECIAL PRICE FOR A LIMITED TIME !!!STOP PRESS!!!
Scrum is a simple framework that allows us to complete projects, continuously improve and get an early return on investment.
AUTHOR NOTE "I write this text as a certified scrum master with experience in international blue chip companies dating back to 1999. That experience includes leading projects for the BBC, General Electric, Oracle, BSkyB, HiT Entertainment (responsible for Angelina Ballerina, Bob the builder and other titles that you love watching with your kids or siblings but won’t admit to) and Razorfish. These roles have all involved leadership on a wealth of mobile, internet TV and web software projects."
“Life is not perfect and the greatest lessons of all are learned by making mistakes and improving.”
Although I have always endorsed The Scrum Guide as the authority on Scrum and the official rulebook, some things can only be learned from experience. This is because although The Scrum Guide does teach you the scrum rules, nothing can completely prepare you for what to do when things do not go according to plan.
In my years as a Software Engineer, Scrum Master and Agile Portfolio Manager, it has been a combination of my experiences and implementing continuous improvement, which have by far provided me with the most learning. The experiences have been both good and bad. They have involved mistakes by my colleagues but more importantly, mistakes by me. I have found that our own mistakes are often the biggest wake up calls of all. However, I have also learned that as long as we truly inspect and adapt, we always grow hugely from our mistakes.
I wrote this book because I have found that my experiences and mistakes are also valuable to others. This is because it allows them to foresee some situations before they occur and benefit from my experience.
This book is in the form of short stories, because they are stories of my life. In addition, because this format should help entertain you while enlightening you.
Once you have read this book you will have gained:
-insight into real life, common, difficult situations that have occurred in real corporate organisations
-confessions, revealing mistakes I have made on the job and how I have dealt with them
-lessons learned from an industry expert. These are lessons that can be applied to any project, in any organisation
These are my confessions.
Table of Contents
Introduction
Scrum Introduction and Recap
The Characters
Confession 1: Tools vs People
Confession 2: Release Planning Peril
Confession 3: Intro to Scrum Gone Bad
Confession 4: Stand-up vs Sprint Review
Confession 5: Taking the Team to Task
Confession 6: Retrospective Regret
Confession 7: The Bloated Bug Backlog
Paul VII
Scrum is a simple framework that allows us to complete projects, continuously improve and get an early return on investment.
AUTHOR NOTE "I write this text as a certified scrum master with experience in international blue chip companies dating back to 1999. That experience includes leading projects for the BBC, General Electric, Oracle, BSkyB, HiT Entertainment (responsible for Angelina Ballerina, Bob the builder and other titles that you love watching with your kids or siblings but won’t admit to) and Razorfish. These roles have all involved leadership on a wealth of mobile, internet TV and web software projects."
“Life is not perfect and the greatest lessons of all are learned by making mistakes and improving.”
Although I have always endorsed The Scrum Guide as the authority on Scrum and the official rulebook, some things can only be learned from experience. This is because although The Scrum Guide does teach you the scrum rules, nothing can completely prepare you for what to do when things do not go according to plan.
In my years as a Software Engineer, Scrum Master and Agile Portfolio Manager, it has been a combination of my experiences and implementing continuous improvement, which have by far provided me with the most learning. The experiences have been both good and bad. They have involved mistakes by my colleagues but more importantly, mistakes by me. I have found that our own mistakes are often the biggest wake up calls of all. However, I have also learned that as long as we truly inspect and adapt, we always grow hugely from our mistakes.
I wrote this book because I have found that my experiences and mistakes are also valuable to others. This is because it allows them to foresee some situations before they occur and benefit from my experience.
This book is in the form of short stories, because they are stories of my life. In addition, because this format should help entertain you while enlightening you.
Once you have read this book you will have gained:
-insight into real life, common, difficult situations that have occurred in real corporate organisations
-confessions, revealing mistakes I have made on the job and how I have dealt with them
-lessons learned from an industry expert. These are lessons that can be applied to any project, in any organisation
These are my confessions.
Table of Contents
Introduction
Scrum Introduction and Recap
The Characters
Confession 1: Tools vs People
Confession 2: Release Planning Peril
Confession 3: Intro to Scrum Gone Bad
Confession 4: Stand-up vs Sprint Review
Confession 5: Taking the Team to Task
Confession 6: Retrospective Regret
Confession 7: The Bloated Bug Backlog
Paul VII
