SIGS DATACOM Fachinformationen für IT-Professionals

The Conference for Software Architecture
Munich, 03 - 07 February 2020


Talk: Do 3.2
Date: Thu, 06.02.2020
Time: 11:00 - 11:45

Retrospectives To The Next Level: Organizational Agility

Time: 11:00 - 11:45
Talk: Do 3.2


Agile Retrospectives can be used to deal with problems in teams, at a project or product level, or those related to the collaboration between the team and stakeholders. But you need a different approach compared to team level retrospectives to do organizational-wide improvement.
This session shows how to use agile retrospectives to reveal and solve systemic organizational problems and to increase the company's agility It explores different approaches, formats, and techniques for agile retrospectives that are done beyond the development team.

Target Audience: Managers, Teams, Scrum Masters, Agile Coaches, Tech Leads
Prerequisites: At least some experience with team/organizational improvement
Level: Practicing

Extended Abstract
Nowadays many agile teams are doing retrospectives regularly. They are investing their time to reflect, learn, and take action to improve their way of working and deal with problems that they are facing in a structural way.
Organizations are seeing the benefits from this: teams that are becoming empowered, being able to deliver more value to customers and stakeholders, happy employees, and fewer people leaving the organization.It's time to take retrospectives to a higher level, and use them to reveal and solve systemic organizational problems. Agile Retrospectives can be used to do that, but you need a different approach.
In this session, I will show how we can use retrospectives to improve the agility of organizations.
Note: Some might call the above approach scaling retrospectives. If that goes towards imposing how teams do retrospectives with some kind of framework, then I believe it doesn't work. Increasing agility with retrospectives is about creating an environment where teams not only focus on their own improvement needs but also on the company as a whole, and get support from management when improvements go over their team borders or outside their autonomy.