Skip to content

Users Stories

Jump to bottom
Kern edited this page Apr 4, 2016 · 4 revisions

Create an User Story

When you want to add a new feature, you can create a new Trello card in the column "US à spécifier".

The naming convention of this card is very strict :

  • It must be in french
  • The name must be a precise sentence
  • The first part is "En tant que {user-type}," where user-type is refering to the targeted user categories of the application
  • The second part is "Je veux {performed-action}" where performed-action is a quick description of the wanted action, describing the feature
  • The name is prefixed with a backlog ID
  • The backlog ID is composed of three informations : the lot ID, the epic ID, and the US ID
  • The US ID is a letter whereas the other IDs are numbers
  • A backlog ID must be unique
  • An epic is a thematic group of US
  • Each information is separated with a dot, and the backlog ID is surrounded by bracklets

A good example of that is : "[1.2.D] En tant responsable des communautés métier, je veux créer une communauté métier".

The second step is to write the acceptance tests. It is a checklist named "Tests d'acceptation", with several functional test items defining your feature.

Each item is a sentence.

The functional tests must be as exhaustive as possible, because these are the specifications the developement team will have to make your feature.

When you wrote all your tests, you can move the card to the "Spécifications à valider" column.

The product owner will check this column, and when a card is defined enough for an useful feature, he will move it to the "US à valoriser" column.

Valorize an US

The product owner have to declare the value for each US.

The value is between 0 and 100 and is associated to the importance the feature carries for the specified user.

This value will help to have project monitoring and give priorities as a value/complexity ratio for each US.

To define the value, put it at the end of the Trello US name like this : {US-name} | V{value}.

One the value is defined, the product owner will move the card to the "US prêtes" column.

The product owner will create an associated issue, with an Epic milestone if this is the first US of its Epic.

Develop an User Story

To develop an user story, first consult the issues list and the Trello board.

If a Trello card is in the column "US prêtes", with an associated issue created on the Git repository with the "US" label and still unassigned, you can assign yourself to it.

Assign yourself on the Trello card also and move it to the "US en cours" column.

Then, go with Git to your develop branch, update it and create a new branch following the name convention.

git checkout develop
git pull origin develop
git checkout -b feature/{issue-number}/{your-name}-branch-name
  • {issue-number} is the issue ID. It will help you to know on which issue you are working.
  • {your-name} is your own name (that was pretty hard to guess, I know). It helps the others to know who is working on the feature.

Now you are on your feature branch, you can code, commit, push, whatever you like during the feature developement.

Once the feature is finished, push your work to your remote feature branch :

git push origin HEAD

After performing your last code commit, update the CHANGELOG.md file with new items in the [unreleased] field.

To know exactly the best practices for a changelog file, please read keepachangelog.com.

Now you will perform a special commit. This commit will close your feature's issue.

To do this, create the following commit and push :

git add CHANGELOG.md
git commit -m "Close #{issue-number}: {work resume}"
git push origin HEAD

Do not close manually the feature issue !! It will be done manually when your code will be merged in master ! It gives global project visibility with the milestones roadmap and must be preserved this way. Any manually closed issue will be reopen.

Then create a merge request based on the develop branch. Any merge request based on master will be rejected.

Do not validate your own work ! Someone else will review your code, test the developed feature, and then merge it.

Once the branch is merge, remove it, and move the associated Trello card in the "US à valider" column.

Validate an User Story

When an User Story is in the Trello "To Validate" column, the project's product owner will test if the developed feature is conform.

To do it, a checklist of acceptance tests are available on the Trello card.

The tester has to check each item and confirm that the given code respect every condition.

Once all items are checked, the tester can move the Trello card to the "US à déployer" column.

When the code will be deployed to the final environment, the card can be moved to the "US terminées" column

Clone this wiki locally