Really interesting report
I begin with questions to understand more teams context and to get to know other aspects that are interesting to me.<p>1) How often teams released in each of the 4 years<p>2) What is the state of the code-base (i.e. how many parts of the code devs would prefer not to work with, how many bugs are discovered only in production, what is the CC, what is the size of the longest method/class, how many conditionals and static members are in the code, how much time it take for a new team member to do it's first check-in)<p>3) What about collective code ownership ?<p>4) How many time you discovered/learned things only after releasing a feature and how are you dealing with that now<p>5) How much unknowns, uncertainties, unexpected-unpredictable events and changes there are in your domain and business and how you deal with them<p>6) What about devops and support and operation of the system in production?<p>7) what about the features released, how much they are the right features for the users and for the stakeholders ? how much early the team spot the wrong feature?
This is a great article Michael. I admire such openness and transparency. A very inspiring and thought provoking read. Many thanks for making this available.