Anonymous, bureaucrat, administrator
7,528
edits
Changes
From All n One's bxp software Wixi
no edit summary
{|
|-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.
All tickets are logged in a custom form built for All n One's needs. The system can also hoover in emails and turn them into tickets. The tickets have a number of outcomes* 01 - A - Urgent - Quotation Required* 01 - New Ticket* 02 - A - Internally scoped - Awaiting PO* 02 - A - To Be Scoped* 02 - B - Escalation - Awaiting PO* 02 - C - Downgrade - Awaiting PO* 02 - D - Cancellation* 03 - PO Approved* 04 - Testing Outcome* 04 - Ticket details updated* 04 - Work Allocated* 04 - Work Item Requires Testing* 05 - A - Awaiting Clarification* 05 - B - Awaiting Sign Off* 05 - C - Long Term* 05 - D - Nice to have* 05 - E - Awaiting Testing* 06 - Work Complete* 07 - Invoiced* 08 - Complete and Paid Each outcome represents the ticket entering a different phase. The different phases then allow different members of the different departments to interact with the tickets. Where a work item is scoped in Phase 2 and it turns out to be a project, then a number of documentation procedures are carried. These template documents are attached to this record, so all documentation is stored in one place. Client update emails are also added to the ticket.
| style="width:30%" |
[[File:bxp_projectmanagement_009.png|500px]]
|- style="vertical-align:top;"
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.
| style="width:30%" |
[[File:bxp_projectmanagement_010.png|500px]]
|}
