Scrum Backlog: Epic, User Story, Acceptance Criteria

by Avienaash Shiralige

Often, I get to hear questions about level of details that need to go in the product backlog stories.  How detailed should be the acceptance criteria? or how small the story should be? We all know stories matures with time. I really like this post on user story life-cycle. Please take time to read this. Let’s consider an example now.

User story evolution

User Story example: As a Project Owner(PO), I should be able to transfer complete project ownership to my connection, with my role remaining to be just a project creator(author) after transfer.

Note: At the first sight, it is tough to say whether this is a story or an epic. When this story comes up in backlog grooming meeting, teams might completely miss the magnitude of such stories.  Hence, as the product becomes bigger it is wise to start detailing stories by adding acceptance criteria earlier in grooming meetings itself. Impact of every new story gets wider as product becomes bigger which often gets missed by the team.

Now, let’s see the description of this story below:

Description of the story: Currently, authenticated users do not have the ability to be able to transfer the project ownership to their connection. While I may be listed as the Project Owner by default when I create a project, but I should be able to transfer the ownership to any of my Connections by assigning them as the Project Owner. This project should then drop-off my projects dashboard and be available for the new Project Owner.

The Original Project Creator will still be tracked in the Project. If the Project Owner is again revised, access and edit permissions will be transferred to the new Project Owner. This field will be listed under “Assignment Information” in the Project edit view.

Acceptance Criteria for the story will be:

1. Author should have permission

  • To upload content files
  • Download contents, turns and transcripts
  • To view assignment, case information and project information block.
  • To discuss and collaborate.

2. Author should NOT have permission

  • To upload transcripts
  • To edit project
  • To delete any of the files(content,transcript)
  • To create/edit turns.
  • To search on those projects if he does not have any other role on the project.

Workflow Status Change:

  • There is no change in status of the project when ownership gets transferred. Earlier workflow remains intact.

System Notifications:

  • System Notification will be displayed for new project owner after assignment in his notification window.
  • Email Notification will be sent for new project owner.
  • No notifications to authors for any changes in project after transfer

Discussion:

  • Project author should be able to discuss on the project And notification is going to all assigned users.
  • If any of the assignee add something to discuss, notification is going to assigned users except Author.

Collaborate:

  • Project author should be able to Collaborate on the project And notification is going to all assigned users.
  • If any of the assignee add something to collaborate, notification is going to assigned users except Author.

Project Search:

  • New PO should be able to search the project after he is been made owner by the project author.
  • Unassigned PO  — If a PO (say name abc) transfer her ownership to one of her connections, then, abc should not be able to search the project.

TimeZone:

  • Create Date/Time of the project should get changed as per the timezone of the new PO
  • Due By Date/Time of the project should get changed as per the timezone of the new PO

Dashboard:

  • Author should not see this project under her Project Listing
  • PO should see this project under her project Listing.

Reports:

  • Any impact on existing reports?
  • Creating new report story: Should we create reports to assess how many levels of ownership change has happened?(This can be treated as a separate story). I should be able to track all the ownership changes, how many levels, from whom to whom in the reports.

As you see here, complete  details of the story doneness must go in the acceptance criteria. This lists out all the impacts across the system. But this list looks quite long. Hence this is an Epic and might take more than a quarter of a sprint(this is the thumb rule I follow to pick a story in a sprint). This epic now can we divided into multiple stories like handling dashboard, search and reports. That will bring the size of the above story manageable to implement within the quarter of the sprint. Build basic functionality and then add features incrementally to make them rich.

Spread the love
  •  
  •  
  •  
  •  
  •  
  •  
Shyama Joshi June 8, 2015 at 11:11 pm

Hey Avi, I have a peculiar problem with the project that I am managing using Agile. I have a user story very well defined with very well-articulated acceptance criteria. During the sizing of user story and detailing out the tasks as part o f backlog grooming exercise, SCRUM team realized that the user story cannot be termed as “DONE” due to the effort involved and indicated that the tasks surrounding the user story needs to spill over into next sprint. Is this accepted in so called “AGILE” world? In case it is not what would be your best suggestion to overcome this situation?

Avienaash Shiralige June 11, 2015 at 12:02 am

Shyama, if you realize this at the end of sprint, then you will not mark it as DONE and you will not take credit for that story in your velocity calculations for that sprint. You will push it back to product backlog and get it prioritized to pick in upcoming sprints.

But if you know this in backlog grooming meeting, then you should break such story(vertical slicing) into smaller stories and add later story for coming sprints. This is incremental approach. Does that answer?

Avie

Shyama Joshi June 16, 2015 at 6:55 am

Thanks Avie. It does answer my query.

Comments on this entry are closed.

Previous post:

Next post: