<ol>
<li>Make sure that your stories are not centered on Operations.  Remember that DevOps is a culture not a role.  Is an "Operations Engineer" really the stakeholder for the story?</li>
<li>Think of the features and business value they provide.  As a <strong>stakeholder</strong> I want <strong>feature</strong> so that <strong>business value</strong>. If you are struggling to identify the business value why are you doing it?</li>
<li>Stories are supposed to be "vertical slices" as opposed to "horizontal slices".  This means that stories should focus on an entire feature, not a layer.  This fits very well in a DevOps culture as your stories can cut across the traditional Development and Operations layers.</li>
</ol>

<p>You already have some interesting features such as the quality standards. Now you just need to identify who the end stakeholder is, what the business value of this would be, and ensure that you write the story in such a way that people with development, operations, and possibly QA skill sets can work on it.</p>

CC BY-SA 4.0
2019-10-28T14:17:10.823Z
2019-10-28T14:34:17.380Z
2019-10-28T14:34:17.380Z
Wesley Rolnick
<p>What type of user stories should Operations write down while being asked to be a stakeholder in a scrum project?</p>

<p>Following this template:</p>

<p>"As Operations engineer, I want to.. in order to.."?!</p>

<p>My first idea is for example to come up with for example expectations to quality standards i.e. <em>acceptance criteria</em> to deliverables, like "as an operations engineer, I want to get deliverables accompanied with installation and validation automation scripts in order to enable fast and transparent deployments", but is there more to it?</p>

CC BY-SA 4.0
2019-11-05T22:29:11.103Z
What do you need that benefits you? Why do you need it? You can make it so generic that the story will never complete, or so specific that it need no further breakdown. For example, as an operations engineer I need feature_x implemented in script_y so that i can something_z.
Birb
<architecture><operations><agile>
What are DevOps & Ops user stories, or elements in scrum context?
Ta Mu
# What are DevOps & Ops user stories, or elements in scrum context?

(Asked by: username_0 on 2019-10-28)

What type of user stories should Operations write down while being asked to be a stakeholder in a scrum project?

Following this template:

"As Operations engineer, I want to.. in order to.."?!

My first idea is for example to come up with for example expectations to quality standards i.e. *acceptance criteria* to deliverables, like "as an operations engineer, I want to get deliverables accompanied with installation and validation automation scripts in order to enable fast and transparent deployments", but is there more to it?

**Tags:** architecture, operations, agile

> **Comments:**
> **username_1**: What do you need that benefits you? Why do you need it? You can make it so generic that the story will never complete, or so specific that it need no further breakdown. For example, as an operations engineer I need feature_x implemented in script_y so that i can something_z.  

---

## 1 answers

### Answer by username_2 on 2019-10-28. Score: 7

1. Make sure that your stories are not centered on Operations. Remember that DevOps is a culture not a role. Is an "Operations Engineer" really the stakeholder for the story?
2. Think of the features and business value they provide. As a **stakeholder** I want **feature** so that **business value**. If you are struggling to identify the business value why are you doing it?
3. Stories are supposed to be "vertical slices" as opposed to "horizontal slices". This means that stories should focus on an entire feature, not a layer. This fits very well in a DevOps culture as your stories can cut across the traditional Development and Operations layers.

You already have some interesting features such as the quality standards. Now you just need to identify who the end stakeholder is, what the business value of this would be, and ensure that you write the story in such a way that people with development, operations, and possibly QA skill sets can work on it.


---

