Changes

Scenario - bxp as a Project Management Toolkit

1,036 bytes added, 11:02, 21 August 2015
no edit summary
Each user is given access to projects that have been set up and can select from the work types.
 
 
The system can store billable and non-billable work. So when a report is done for a client at the end of the month it becomes very clear how many extra hours you have put into the project and not charged for.
= Managing Change =
 
{|
|-
| 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.
 
 
We operate a very clear program of triage for requests coming in. [[Bxp_Support_Triage_Process]] This is supported operationally by a tool called LogicFlow which provides clear branches for how the request is to be handled. [[Module_-_LogicFlow]] Where it is a request to be investigated, which could become a project, it is converted to a "ticket".
 
 
All tickets are logged in a custom form built for All n One's needs.
 
| style="width:30%" |
[[File:Meetingmanager_009.png|500px]]
|}
 
 
 
Ticketing and trouble shooting
7,528
edits