Page MenuHomekolab.org

Create Sheet to describe development process
Open, NormalPublic3 Story Points

Description

Create s sheet to describe the process and the responsibilities in each step.

Details

Ticket Type
Task

Event Timeline

petersen created this task.Apr 14 2015, 1:56 PM
petersen updated the task description. (Show Details)
petersen raised the priority of this task from to 60.
petersen claimed this task.
petersen changed Ticket Type from Task to Task.
petersen renamed this task from Create Sheet to describe to Create Sheet to describe development process.
petersen moved this task from Backlog to Doing on the Sprint Process 201516 board.
petersen added a subscriber: petersen.
petersen edited a custom field.Apr 14 2015, 1:58 PM

First iteration

petersen moved this task from Doing to Review on the Sprint Process 201516 board.Apr 22 2015, 5:50 PM

I would like to consider T47 to examplify the following remarks:

  • The tasks A, B, C and D need not be created as items on the workboard for Product Owners, but can instead block the epic.
  • The tasks A, B, C and D need not maintain a Product Owners association.
  • The development team must appreciate Release Management aspects such as for T47 (and blocking tasks).
  • The association with a sprint_current or sprint_next label is supposed to be a one-time thing, the auto-completion is supposed to provide the actual sprint associated with the alternative tag at that moment, such that what is associated with sprint next today, will be associated with #sprint_server_201518 until forever, and won't automatically move forward to Sprint Server 201520. In effect, you type 'sprint next' but what the task is associated with is what at that moment is the next sprint (i.e. gets tagged with #sprint_server_201518).
grote added a subscriber: grote.Apr 23 2015, 1:15 AM
vanmeeuwen lowered the priority of this task from 60 to Normal.Mar 28 2019, 8:13 AM