Tasks and Queues

Please read the Planning and Process page in the Operating Model. This defines the full process.

In OMAlab, we are ALL responsible for understanding the tasks we are trying to get done. To that end, we are ALL responsible for creating and defining the specifications/tasks that are necessary to get the job done.

As a developer, you have one job: To take the time you work on our project (and are paid), and to convert that into VALUE for the business. To that end, there are two things you primarily will do to accomplish this:

1. Write code, and

2. Define work to be done.

So, there are two main types of tasks that you will encounter:

• Atomic tasks (we just call them tasks). These are tasks you simply write the code, and check it in.

• Specifications tasks. For these tasks, you have to break down the task into "atomic" tasks. This requires that you understand what the section is trying to achieve, and break it down into its component parts.

At OMALab, you cannot simply do no work because there isn't a task pre-defined for you. If there isn't something defined for you, then you can pick it up and define it yourself.

If work is defined, take the next task and work it. Don't pick and choose your tasks. This is important, as it spreads knowledge around the team.