Main Menu

Project Life Cycle


SCRUM introduction

A good introduction to SCRUM methodology is available at in many languages.

A good knowledge base about using JIRA in SCRUM is available on Atlassian web page,

Helpful resources:

Basic rules

  1. Sprint is 4 weeks long (see fixed schedule for sprints).
  2. Sprints musn't be extended (prolonged).
  3. Stories and epics come only from a client side, not from the development team.
  4. Each developer takes care of a single user story by implementing all needed stuff (database, business logic, GUI).
  5. If a developer gets stuck in something difficult the developer asks for help a Subject Matter Expert (another developer).
  6. Big changes in the software need to be consulted with the whole team.
  7. If a bug is to be fixed the author of the broken functionality takes care of it.
  8. Real time spent on particular issue should be logged into JIRA.

Using JIRA

  1. Use the GreenHopper plug-in's interface (see the "Agile" option in the top menu).
  2. Using the basic JIRA forms is not allowed. It may cause errors and hamper the work of developers as GreenHopper introduces a new way ticket management.

Working with tickets

  1. When defining a STORY ticket a corresponding EPIC ticket needs to be referenced through the Epic/theme field.
  2. Any testing task, research, fix or whatever is related to an existing story needs to be saved as a sub-task of that STORY.
  1. A STORY ticket can't be closed if the story is not confirmed (is not tested) that it works.
  2. A STORY ticket should be reopened if it had been closed and the story's functionality was broken later. For example, in sprint x a story S was implemented, tested and closed. In sprint x+n as a result of some implementation task the story S was broken and it doesn't work any more. It has to be reopened and rescheduled to another sprint.

Issue types

Type Definition
Epic High-level function (e.g. "MPLS support" or "New graphical layout") requested by a user.
Story User story describing details of software behavior (e.g. "As a user I can add an interface to an MPLS node").
New feature New features not covered by any user story - TRY NOT USING IT
Improvement Improvements not requested by users (e.g. "More intuitive configuration panel")
Security Vulnerability E.g. "SQL injection possible using multi-line textual fields"
Bug E.g. "The Cancel button doesn't work"
Task Any other task, e.g.: architectural changes, update of a library version, update of the end-user's documentation

Story points

  1. Each new ticket (incl. sub-tasks) of type different than STORY and EPIC needs to have the ORIGINAL ESTIMATE specified.
  2. For tickets mentioned above a developer has to manage the SPENT and REMAINING time using the LOG WORK functionality.
  3. For STORY and EPIC tickets the above is not allowed. Such tickets aggregate the time vaules of sub-tasks.
  4. For STORY and EPIC the STORY POINTS value has to be defined when creating a new ticket.
  5. The above is necessary to be able to plan sprints basing on estimates.

Business value

  1. Each story should have a business value specified.
  2. When dividing a single story into two or more stories the business value should be updated accordingly (also divided).
  3. The business vaule should be a base for burn-up(down) charts.

Hints and good practices

  1. The less technical sub-tasks in a story the better. More tickets = bigger overhead for ticket management which can be very time-consuming and irritating.

Issues to be considered

  1. Code review done with use of Crucible once a week (only by package/module owners).
Skip to end of metadata
Go to start of metadata
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jul 07, 2011

    Current experience shows that 2 weeks is not enough for a sprint in current team. It should be rather 1 month. This is because the team has not much manpower available for cNIS implementation and it is very often that a single story can't be completed in a single sprint. However, this issue is still to be considered.

  2. Aug 08, 2018


    If you've recently upgraded to Windows 10, you may have to face that your wireless display Bluetooth icon is missing in Windows 10 fix windows 10 connections  you can not even find where it can turn on and off in your Bluetooth

Add Comment