DevOps User Story WS

As an Agile Coach, I made an assertion that the whole DevOps team can and should get involved in all types of work. This might mean we lose the pretty colour-coding of our favourite story-management tool, but in turn we gain a way to acknowledge all the work we are doing—whether traditional feature stories, defect fixes, tech tasks or DevOps tasks—as valuable to the business. To do this successfully you have to restructure your mindset about these “technical” stories right from the start and keep that mindset strong throughout the development lifecycle.

We made our second day of training a working workshop to create a healthy backlog and created user stories throughout the day. In the photos, you can see everyone was writing user stories during the workshop, which was an enriching experience to see all the team contributing. We collaborated, interacted with each other and Anil our Architect was able to attend, which was important to have his view and insight on how the DevOps team were creating their roadmap for the rest of the year and early on through next year with high level features! Michael Frantz, who is their manager was very attentive and was helpful with my user story training and the team’s involvement for successfully getting this team kick started!