A lot of Agile practitioners are familiar with Team-level Scrum Retrospective, an event where the Team inspects its own progress over the past Sprint, acknowledges what it did well, comes up with a list of items they'd like to improve, and produces some actions that will hopefully be fulfilled by the time next Sprint Retrospective is held.
As simple as this classic Retrospective concept is, I've seen one too many times when Retrospectives are undervalued and not happening at all, or are done as a "tickbox activity", meaning not much to the participants who just do it because they have to.
There are good reasons why that apathy happens.
Some of those are in the lack of understanding of what a good, well-run Retrospective can do to your Team's development and Agile maturity over time. Others are simply in the poor form and execution, that need to be demonstrated and corrected by a professional.
Program-level (or Program-wide) Retrospectives are similar as a concept, but very different in how they are executed.
As the name suggests, those are not for the Development or Delivery Team level, but for much wider and higher circle of stakeholders that are supposed to be "leading the charge" and supporting the Teams with their Vision and Governance, from above.
Professionally facilitated Retrospective of this level helps Development Teams be seen as real people with real feedback, cutting through the borders of formal reporting lines and middle-management trying to look good (in some cases).
It helps parts of Business that felt excluded, misunderstood, or simply not welcome to the party to finally be heard. It drives Continuous Improvement at a Program Level, could help realign Product Vision, perceived Roadmap of Features in the Delivery, and have other positive side-effects.
Finally, having it done by an external professional who specializes in delivering sessions like these helps take egos on higher level management out of equation, helping streamline communication and hold people positively accountable going forward.
Mostly described by the introduction text above, actual content of the session may vary, based on the needs of your organisation and upon your request.
There is always core element to the Retrospective involved, where everyone writes on Post-It notes and discusses observations. But that is usually expanded into Product Vision discussion or other key challenges that I aim to address in a fluid facilitation manner.
It is usually a half-day exercise, sometimes expanded to a longer time-frame based on the organisational needs and custom Agenda.
We mostly train teams in Sydney, but will consider other locations in Australia, pending discussion with the Requestor.
Base conditions of the course are 10-30 participants, venue organised by the Requestor, with some additional requirements that are discussed once you've contacted us.
Pricing is competitive with similar services offered by the other freelance Lean-Agile training providers and agencies in Australia, and available along with other details upon request.