Partner with firstname.lastname@example.org
Work with email@example.com
Creitive Singapore Pte Ltd
71 Robinson Road, 14-145
Creitive Digital Agency FZ-LLC
Dubai Media City, Building 10
Creitive FonSoft d.o.o.
Generala Anrija 13
What is Agile?
What is Scrum?
What are User story in Agile (Scrum)?
What is Epic?
What is Product Backlog?
What is Sprint in Scrum?
(Traditionally there was no collaboration and communication within a team).
Every good user story should have these elements, known as the three C’s principle:
The three C’s principle is a very common practice in modern agile project management.
Anyone in an Agile team can and should write user stories, however, the Product Owner is responsible for making sure that the User Stories are written and that the product backlog is managed.
The Product Owner will usually communicate with the team regularly to make sure this happens. The team will usually collaborate with the Product Owner and often write cards that the Product Owner prioritizes in the backlog.
Product owners should be focused on the business value each story provides to the user, they are usually considered as "business" or "client" advocates.
User Stories are written on 3 by 5 inch cards. The description goes on the front, Acceptance Criteria on the back.
There is a plugin/functionality in Jira Software for a more scrum-like look and feel. Read more in JIRA's documentation.
"3 Rs" concept How to write a User Story using the "3 Rs" concept:
As a role I want requirement so that reason/ROI
Its purpose is to articulate precisely when the User Story is "Done" from the Product Owner's perspective. They should translate into "acceptance tests" that a QA tester can use to verify the quality of the feature. The tester can be involved in writing them but it is a Product Owner's responsibility to produce them.
A user should see/be able to:
- Acceptance Criteria 1
- Acceptance Criteria 2
- Acceptance Criteria 3
Edge cases (other scenarios)
- Edge Case 1
- Edge Case 2
- Edge Case 3
As an F1 game player I want to see a circuit map so that I know where I am on the circuit
An F1 game player should se a track that:
- as closely as possible resembles the shape of the F1 track in the game
- consists of a graphical circuit line that fits within a 3 by 5 proportioned box
- has a small dot that represents the game player's car
- the dot should move in relation to and in proportion to the game player's position on the track
- If the car blows up, the dot should turn red for 1 second then disappear
As an F1 game player I want (to see) an Options Screen so that I can choose the driver I want to use
- User Story 1: As an F1 game player I want (to see) an Options Menu so that I can choose the driver I want to use
- User Story 2: As an F1 game player I want (to see) the Image Holder for a driver so that I can see the driver I want to use
As a sports fan I want a group of Sports pages so that I can see the top 10 news stories for each sport
- Sports homepage: As a Soccer Fan I want a Football Home Page so that I can see the top 10 football news stories
- Sports homepage: As a Baseball Fan I want a Baseball Home Page so that I can see the top 10 baseball news stories
You can use the above examples as a User Story template for jIRA or similar platforms.
Teams really need Stories to be in manageable size in order to estimate them well.
Acceptance criteria: The user should be able to load the page in less than 30 milliseconds
Acceptance criteria: If there is an unknown error loading the page, the user should see the standard error message "Unknown Error: Currently unable to load this page. Please refresh the page and try again."
Acceptance criteria: The user should see an advertisement for the sports channel below each news story, measuring 5 by 2 inches.
Story points are a unit of measure for expressing an estimate of the overall effort that will be required to fully implement a product backlog item or any other piece of work.
In Agile development, the Product Owner is tasked with prioritizing the backlog - the ordered list of work that contains short descriptions of all desired features and fixes for a product.
Story points estimate the relative effort of work by using a simplified Fibonacci sequence: 1, 2, 3, 5, 8, 13.
The Fibonacci sequence is a series of numbers where each number is equal to the sum of the two numbers that come before it, and usually starts with 0 and 1: 0 + 1 = 1, 1 + 1 = 2, 1 + 2 = 3, 2 + 3 = 5, etc.
Some teams use other measurement scales for story points, but this is a common one.
When we estimate with story points, we assign a point value to each item. The raw values we assign are unimportant. What matters are the relative values. A story that is assigned a 2 should be more complex than a story that is assigned a 1. It should also be less complex than a story that is estimated as 3 story points, and so on.
Because story points represent the effort to develop a story, a team's estimate must include everything that can affect the effort. That could include:
We are Creitive, digital product agency. If you want to learn more, check out our Agile Product Development Services