Working on improving our sprint reports jira plugin, am already interviewing TPMs but thought taking some unfiltered advice here would be a good idea too.<p>The key question is: What is one piece of info in your sprint reports that will save you from taking another headache pill every weeK? (or save your fridays from preparing reports manually)
The only non-negotiable is information clearly stating what the goal of your team is, how it directly affects the mission of the company, and how much progress your team made towards the goal during the sprint.<p>I recommend “An Elegant Puzzle” by Will Larson if you are asking this sort of question. It’s as close as we have to a bible on being a technical PM. It totally changed my perspective on getting things done as a team of software engineers, and also led me down a treasured path of systems thinking and psychology. It’s simply an excellent book for someone like you to read.