You may hear the following terms batted about at meetups, hackathons, and tech talks: “Product Owner”, “SCRUM master”, “Project Manager / Technical Project Manager”, “Senior Developer”, “Stakeholders” and so on.
What do all these terms, roles, and names mean?
While interpretation varies a little bit from team to team, it’s still a good idea to have a basic understanding of the kind of work these roles describe.
To give you a general overview, we recommend this video by Henrik Kniberg, professional agile coach at Spotify and Lego. It’s entertaining to watch and contains clear expectations around teams.
In your time at Epicodus, what roles and responsibilities have you seen emerge from the workflow in teams and pairs? In what ways can the principles in this video enrich those experiences?