Final Thoughts

  • Tim Brizard

Abstract

One of the primary reasons for writing this book was to share my experiences from over six years on Agile projects and, ideally, to help other development teams learn from others’ mistakes. I’m a big believer in learning from others’ experience and not repeating the mistakes and going through the same pain. On several Agile projects, I’ve see new teams refuse to ask more seasoned teams for advice. Perhaps they just wanted to learn on their own and not be influenced by others’ experiences. Maybe they thought they had all the knowledge and tools they needed to be successful. But, inevitably, I would hear them go through all the same pain that other teams had gone through and long since learned from. That’s why I wanted to share these stories. Not every team is the same and not every scenario is covered here; that could never be the case. There is no right answer and the thoughts about each story are just my opinions and based on what I have personally experienced.

Keywords

Open Communication Unit Test User Story Agile Software Development Defect Count 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Copyright information

© Tim Brizard 2015

Authors and Affiliations

  • Tim Brizard
    • 1
  1. 1.FloridaUS

Personalised recommendations