# Defining a Role with a Retrospective Activity

DevFeed: [Defining a Role with a Retrospective Activity](<https://devfeed.tech/articles/defining-a-role-with-a-retrospective-activity-2022.md>)

Original publisher: [Read original article](<https://developers.soundcloud.com/blog//defining-a-role-with-a-retrospective-activity>)

Published: 2018-06-22T00:00:00Z

Content type: article

Language: en

Sources: [SoundCloud Backstage Blog](<https://devfeed.tech/sources/soundcloud-backstage-blog.md>)

Topics: [Agile](<https://devfeed.tech/topics/agile.md>), [Tech Lead](<https://devfeed.tech/topics/tech-lead.md>), [iOS](<https://devfeed.tech/topics/ios.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [ios](<https://devfeed.tech/tags/ios.md>), [leadership](<https://devfeed.tech/tags/leadership.md>), [retrospective](<https://devfeed.tech/tags/retrospective.md>), [tech-lead](<https://devfeed.tech/tags/tech-lead.md>)

## AI overview

The article explains how a modified KALM retrospective activity was used with SoundCloud's iOS Collective to redefine the responsibilities and expectations of an iOS Tech Lead role. It emphasizes creating a safe, collaborative setting for gathering opinions, discussing changes, and identifying what the team needs from the role.

## Source excerpt

Agile retrospectives are a widely used practice within engineering teams. They provide teams with a way to reflect on how they work and become better at what they do. One of the main benefits of retrospectives is that they empower teams to define and make changes by analyzing what happened in an iteration and by determining what can be improved moving forward. Here at SoundCloud, we hold retrospectives at the end of every iteration (every two weeks), and we often do them at the end of projects as well.