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

User Tools

Site Tools

Story definition

  • The story is defined and presented to the group by the customer. It is already defined in the Jira(?).

Task definition

  • The group discusses the story presented.
  • It will be split up into workable fragments and is assigned to participants. (On paper!)
  • Each task will then include a detailed description.
  • The assignees will write/copy an (detailed) outline of the task in/to JIRA, so other people can inform about the task and see who is working on it.
  • Please include still the “TASK: ” prefix, because it improves readability when e.g. linking.
  • Please let it “Fixes version” = “Iteration X” (where X is the current Iteration-number).
  • Please add a “is-part-of” link to the appropriate story.
  • Please estimate working times in JIRA.

Task work

  • Write down the starting time on the task sheet.
  • Start working!
  • Once you stop for a while (break, lunch, sleep), write down the time where you stopped working (to the paper).
  • When you restart working, recontinue from upper instruction.
  • At the end of the day, calculate the sum of working times and track it into JIRA.
  • Please try to give a summary of things done to the program at the only time you log your work, so other people can wonder about your efforts.

Task overhead

  • If you experience an unestimated overhead on the task, split it up yourself.
  • Please report this split-up as a comment in JIRA.
  • Write a new task (on paper!) and put it on the “Unassigned” wall.

Task ending

  • Close the task in JIRA.
teaching/labs/xp/2004b/jiratracking.txt · Last modified: 2018/05/09 01:59 (external edit)

SEWiki, © 2021