Ticket Workflow

The Scientific Computing team uses a hybrid Agile-Scrum model to identify work load, and complete desired work in two-week sprints. Click below to see an overview of individual workflow as well as how CSSC currently leverages the agile process.

The most basic workflow of members of the scientific computing team is as follows:

While tickets can be entered for a variety of reasons from a variety of stakeholders, ultimately, it is this workflow that propels all the projects completed by the department.

The Scientific Computing team ultimately uses a hybrid Agile-Scrum model to identify work load, and complete desired work in two-week sprints. Prior to each sprint, PM will schedule meetings for team members to determine which tickets from the backlog will be a part of the sprint, as well as the ticket priority, estimated timeframe of completion & ticket owner.

Agile-Scrum Workflow

Please note tickets are elicited throughout the entire sprint process. During sprint execution all new tickets are added to the backlog to be assigned at a later time unless under exceptional circumstances.