Customising Project Statuses
Page: 1
Chris Dymond
on Oct 25. 2007. 12:20 pm
Dear aC team,
is it (or will it be) possible to change the set of project statuses in aC?
Even better would be to allow different sets of statuses depending on project type (or project group).
Has this been considered?
Chris D. (UK)
is it (or will it be) possible to change the set of project statuses in aC?
Even better would be to allow different sets of statuses depending on project type (or project group).
Has this been considered?
Chris D. (UK)
Chris Dymond
on Oct 26. 2007. 8:27 am
Hi Ilija,
we have two problems, one more serious than the other.
The first one is that the 4 statuses that are hard-coded in aC1.0 don't cover all of the states one of our projects can be in. We emply a tailored version of the PRINCE2 project methodology and we really need our process to be consistent throughout our toolset. So we'd like to be able to add a few statuses to the list to indicate what stage of the process the project had got to, such as 'In Start-up', 'In Planning', 'In Closure', etc. Being able to change the default statuses would allow us to do that quite well I think.
Our second problem is that different project types have different lifecycles, so for example small enhancements to an existing system which are to be carried out under a client's rolling retainer go through a different set of stages than a large consultancy and development project. So the ability to associate project status lists with groups would be useful (but not essential as we can of course just use the superset of statuses).
Best regards,
Chris D.
we have two problems, one more serious than the other.
The first one is that the 4 statuses that are hard-coded in aC1.0 don't cover all of the states one of our projects can be in. We emply a tailored version of the PRINCE2 project methodology and we really need our process to be consistent throughout our toolset. So we'd like to be able to add a few statuses to the list to indicate what stage of the process the project had got to, such as 'In Start-up', 'In Planning', 'In Closure', etc. Being able to change the default statuses would allow us to do that quite well I think.
Our second problem is that different project types have different lifecycles, so for example small enhancements to an existing system which are to be carried out under a client's rolling retainer go through a different set of stages than a large consultancy and development project. So the ability to associate project status lists with groups would be useful (but not essential as we can of course just use the superset of statuses).
Best regards,
Chris D.
Chris Dymond
on Oct 26. 2007. 9:19 am
Thanks Ilija,
to give you an idea of the project statuses we use, here's a set of statuses for small maintenance projects:
* Requested
* Authorised
* Briefed
* Internally Approved
* Client Approved
* In Production
* In Testing
* In UAT
* Live
* Accepted
* Closed & Invoiced
Our Project and Account Managers may have 30+ of this type of project active at the same time, so the ability to see where they are would be a great help (to the client as well). We could use groups to do this, however we'd rather use groups to show the project *type*.
One other method we could use would be to have a default checklist which we could attach to new projects with each of those statuses as a separate task that can be completed. This would at least allow us to see for a given project what status it is in (without having to change the name of the project). We'd also like to use this to track the statuses of tickets.
CD
to give you an idea of the project statuses we use, here's a set of statuses for small maintenance projects:
* Requested
* Authorised
* Briefed
* Internally Approved
* Client Approved
* In Production
* In Testing
* In UAT
* Live
* Accepted
* Closed & Invoiced
Our Project and Account Managers may have 30+ of this type of project active at the same time, so the ability to see where they are would be a great help (to the client as well). We could use groups to do this, however we'd rather use groups to show the project *type*.
One other method we could use would be to have a default checklist which we could attach to new projects with each of those statuses as a separate task that can be completed. This would at least allow us to see for a given project what status it is in (without having to change the name of the project). We'd also like to use this to track the statuses of tickets.
CD
Sebastian Tänzer
on Oct 26. 2007. 9:45 am
+1
Need this for reporting to our project managers.
Please don't hardcode these but give us the possiblity to have our own project states.
Need this for reporting to our project managers.
Please don't hardcode these but give us the possiblity to have our own project states.
cyandesign
on Oct 26. 2007. 1:58 pm
I agree with Sebastian,
This would be great but please don't hard code it. We have a small shop & would find all of the fields that Chis Needs overkill for us. Plus it would be nice to add statuses on the fly as our company dynmics change.
+1
This would be great but please don't hard code it. We have a small shop & would find all of the fields that Chis Needs overkill for us. Plus it would be nice to add statuses on the fly as our company dynmics change.
+1



