|- style="vertical-align:top;"
| style="width:70%" |
So how does a Project come to be? They all come to light as a result of a request from a client. Maybe inspired by a client or a Business Development manager on behalf of a client, but it is a request into the Project Manager that gets the ball rolling. All n One is no different in this regard.
|- style="vertical-align:top;"
| style="width:70%" |
Once the project has become 03 - PO Approved, then the work itself is broken down into smaller "Jobs". These jobs are mini-tickets that have their own form.
For larger project traditional project management tools such as Microsoft Project can be employed to scope work. These documents are also attached to the Ticket.
These Jobs are allocated to different developers to perform.
Each Job goes through a number of phases as well
* 01 - Add request
* 02 - Add another work request for this job
* 03 - Investigating client request
* 03 - Request details updated - Dev stage
* 04 - Request assigned for testing
* 05 - Testing new issue found
* 06 - Testing complete
* 07 - Request awaiting clarification
* 08 - Request awaiting sign off
* 08 - Request cancelled
* 08 - Request complete
This isolation of Jobs allows the Technical Operations Manager (Carolann Diskin) to manage the project and the elements within it from numerous projects simultaneously.
| style="width:30%" |
|}- style="vertical-align:top;"| style="width:70%" | Each developer has the ability to view all of the Jobs that have been assigned to them as a separate worklist. For stress management, it is possible to limit the jobs assigned to a developer. The Due Date field helps with prioritisation especially across multiple projects. Visible queues enable management to be able to review any individual to see what they have on.
As each developer logs their hours in Time Tracker (as above) the time slot can be linked to a specific Job for even closer management.
| style="width:30%" |
[[File:bxp_projectmanagement_011.png|500px]]
Ticketing and trouble shooting|}
So for any given project there are a number of steps which are performed in sequence.
* A project is decided on (see managing change below for how this begins)
= Quality Assurance =