

Discover more from Agile Notes
91 subscribers. :) Let me know what you think about a giveaway and how we should do it in the comments.
This week, we continue with Collaboration Explained by Jean Tabaka. This week, we move on to Chapter 5: Defining Project Collaboration Events.
Lots of really good and really detailed guidance on how to run the various types of meetings needed to run a project and/or Scrum teams. Tabaka looks at Status meetings like a daily Scrum , Planning meetings like a project kickoff/chartering or Sprint planning meetings, Release planning, Project Working Sessions like Design and Requirements gathering meetings.
The section on Sprint Demos/Reviews Meeting caught my attention. I like the structure to it and I will add these questions to my Sprints. These questions formalize the Review. In the past, I have found it easy to just do a demo, get a thumbs up from the Product Owner and then roll right into the Sprint Review and then Sprint Planning. These questions from Tabaka force you to tie everything together in a more formal way. Has scope changed? Have priorities in the backlog changed? How about our estimates for the next Sprint (probably a sprint planning question but I get it.)
What commitments were made? What were our goals? Which ties to the Demo - or it SHOULD - if it doesn’t then we are in trouble. After the Demo - we ask about what did NOT get completed.
I like all of this. Everything in context to the Sprint and the Backlog.
Do you have anything to add to these questions? Let me know in the comments. Thanks for reading! Please like, share, subscribe. Don’t forget to comment on a potential 100 Subscriber Giveaway!
Agile Notes (No. 46)
Hey Mike, this one deserves a podcast for sure. I think we could expound on how demos/review should be run and what we stand to learn from them, using your post here as a guideline.