Task life cycle

Question

What is the life cycle of your task? and combine tasks and errors with the tool you use? Typical task life cycle:

• Not started - entered, but not yet launched
• In-Progress - Work on
• Completed - task completed with exception statuses:
• Waiting for something
• Canceled - the task is no longer needed, possibly due to a change in requirements.

A typical error life cycle might be:

• New - Recently Introduced
• In progress - work on
• QA - testing through
• Client Review - Client-Validated Patch
• Ready for promotion - ready for next version
• Completed - put into production with exception statuses:
• On hold
• Duplicate Not playing.
• Works as designed

What are your life cycles?

Answer 1

I like to keep it simple:

• Pending
• In danger
• In production
• Full

I also have very specific visual help colors for these tasks when I list them in Excel systems or spreadsheets, as shown above:

Task Colors http://i44.tinypic.com/14dhp5l.png

A detailed overview of each of them:

It is expected for tasks that I don’t work on, mainly because it requires some external event, for example, some statement, or simply because I’m not sure that I will do it anyway.

In danger, it is intended for the tasks that I started, but they are approaching the appointed date, and I can not finish it at all. If I get too much in Risk tasks, I begin to arrange them to make them on time.

In production , this is a regular task that I work on. Perhaps he does not have the due date, so he will never fall into the "Risk", or maybe, if I delay too much, I set the payment date, and this task can change to "In danger."

Completed pretty much self-evident.

Answer 2

In fact, we manage to have one life cycle for different tasks

• Open
• IN
• Rejected
• Test
• Decided
• Close

This applies to our ITIL- based tasks (a set of concepts and policies for managing information technology (IT) infrastructure, development and operations.):

• happening
• change
• dependency (regroup several changes)
• release (regroup several dependencies)

Do not forget:

• For certain tasks, an additional task life cycle may be required: for example, before opening, processing, etc. REL (Release) must be sent first.
• testing the life cycle can be performed for certain tasks: it is impossible to send REL (Release) without a testing list.

Answer 3

We use one tool in which we mix errors and function requests (but we put each entry accordingly so that we can see if it is an error or requests).

Since we have several departments working on tasks, we have more statuses ... Our various life cycle statuses:

• specify (for product management)
• to reproduce (for testing, to check, for example, something is a software problem or just a wrong client configuration).
• develop (for developers)
• check / check (for testing)
• document (for documentation, for example, to include it in the user manual)
• implemented and verified (this is the time when we close the task)
• restriction / rejection / not reproducible

Answer 4

The part that I noticed is important - waiting for external dependencies to do something or create something, I think the vital status of the task for management is to easily see that they can advance and beat in motion ... ^^

Answer 5

Simpler than just

  open
 error / change analysis
 qa review
 closed / rejected 

Answer 6

I think that there are only 2 necessary elements: "Open" and "Closed", the rest are gradients.

I use:

• Open
• Pending
• Decided
• In standby
• Closed

Sometimes I add to this:

• Performed
• Announced
• In the test
• Overview
• Canceled

It depends on the work flow of the team.