SDA SE Wiki

Software Engineering for Smart Data Analytics & Smart Data Analytics for Software Engineering

User Tools

Site Tools


The workflow for stories and tasks should be sequential. Here are some notes.

Stories

  • represented as “Story”
  • Summary starts with “STORY: ”
  • NO estimated time filled in
  • Fix Version is the Iteration. (NO Affects Version)
  • only the customer creates stories
  • States:
    • created (=open)
    • in progress. Additional action: enter date into the release plan. The preliminary list of task has to be defined. Enter number of tasks to the release plan. Each of these tasks “is part of” the story.
    • resolved. If all tasks are closed
    • closed. If acceptance test passed. Additional action: enter date into the release plan. Enter actual number of tasks into the release plan. Also the sum of estimated and actual times.

Tasks

  • represented as “Task”
  • Summary starts with “TASK: ”
  • Fix Version is the Iteration. (NO Affects Version)
  • ESTIMATED TIME must be filled in. (Adaquate accuracy: quarters of an hour.)
  • States:
    • created (=open)
    • in progress. Additional action: assure that the estimated time is filled in. Enter the name of both developers to the Summary.
    • resolved. If the work is done and all tests passed.
    • closed. If the changes are checked into the CVS repository.
XP Jira Conventions
Story Story Summary starts with “STORY: “
Task Task Summary starts with “TASK: “
assured major
surplus minor
deferred trivial
Iteration Version use “fix for” field



Check for completness
List mappings of XP/JIRA terms
Make the text more readable.
teaching/labs/xp/2004b/proceduresjira.txt · Last modified: 2018/05/09 01:59 (external edit)

SEWiki, © 2020