Step#2 User Stories

The step#1 was about defining the EPICS. As a recap, the EPICS of Go2Scrum were;

  1. Content for mastering Scrum
  2. Content for mastering Jira
  3. Mentoring for individual users
  4. Customer specific mentoring
  5. Monitoring & Controlling customer’s projects using Jira
  6. Agile outsourcing support

Can we estimate the effort involved in developing them?. It is not possible as the information available is not detailed enough. We need to elaborate them further. That is where ‘User stories’ fits in.

Structure of the User Story

User story contains three sections – header, detail and the acceptance criteria. One EPIC is elaborated by single or multiple User Stories, based on the complexity of the EPIC.

  • Header – Creating Content for mastering Scrum
  • Detail – As a content creator, I should be able to create reader friendly content for product backlog, sprint backlog, sprint planning meeting, sprinting, daily scrum, sprint review, sprint retrospective, roles & responsibilities, burn down charts.
  • Acceptance criteria – It must cover scrum, as defined by the founders of scrum Ken Schwaber and Jeff Sutherland. It must be easy and simple to understand.

Let us define this user story in Jira

As an after thought I created user stories for creating content for;

  • Product backlog
  • Sprint backlog
  • Sprint planning meeting
  • Sprinting
  • Daily scrum
  • Sprint review
  • Sprint retrospective
  • Roles and responsibilities
  • Burn down charts
  • Estimation
  • Velocity calculations

If the stories are smaller, I will be able to show progress on a daily basis.

Here is the screenshot