As an architect, what is my place in Scrum?

Scrum and the stakeholders, episode 3

Willem-Jan Ageling
Serious Scrum

--

The ‘Scrum and the stakeholders’ series discusses the place of several stakeholders in Scrum. All its articles have this theme and can be read on their own.

Rough architectural design of a building with coloured makers lying on top.
By stux-12364 at Pixabay

Introduction

Scrum knows 3 roles: Product Owner, Development Team and Scrum Master. People outside the Scrum Team are addressed as ‘stakeholders’. On top of that the Scrum Guide mentions ‘committee’, ‘employees’ and ‘organization’, but the umbrella term in Scrum is ‘stakeholder’.

Often stakeholders have no insight in what kind of role they can play. The series ‘Scrum and the stakeholders’ aims to clarify the place of the different stakeholders within Scrum.

Every Scrum environment is different, so there is no clear-cut answer that applies to all situations. Therefore we will discuss the different options to help you decide what is the best solution for you.

This article will discuss the architect who architects solutions and services for organizations. Often the architect is acting outside of the Scrum Team, but this doesn’t have to be like this.

The purpose of a Sprint

“The heart of Scrum is a Sprint, a time-box of one month or less during which a…

--

--

Willem-Jan Ageling
Serious Scrum

https://ageling.substack.com Writer, editor, founder of Serious Scrum. I love writing about maximizing value.