Are Decision Points compulsory ?

[Former Member]

Hello,

It is perhaps a strange question ! In a first stage, my client does not need Gates and Decision Points.

I have created Item Type without link with DP. I was not able to create Item in my portfolio !

Is there a custo about this ??

Thanks.

Dali

[Former Member · Accepted solution]

Hello Dali

Decision points are required - you need at least 1

From a governance perspective I would suggest that you workshop Item Lifecycles (Decision Points) and that you configure them; even if you don't use them straight away...i.e. design for the end state even if you not going to use this initially

Regards
C

[Former Member · Accepted solution]

Hello Chatsworth,

Thank you very much for your confirmation !

I will follow your advice with 2 ou 3 DP.

Should i also manage some statuses ? They need to be managed by users and they won't do it ...

Regards,

Dali

[Former Member · Accepted solution]

Hello Dali,

Are you referring to status management at Item and/or Decision Point level, or in general?

Status management differs from object to object - e.g. at Initiative level there are default (standard) statuses such as Created, Released, Closed etc. The same applies to cProject objects such as the cProject header, phases, etc. In order to perform certain standard business processes such as confirmation of tasks, phases, etc you will need to perform status updates (release, complete, etc).

In addition to this - but this is not compulsory, you can add additional user statuses to reflect and control certain business processes.

At Item level no standard status management exists - i.e. you can map statuses to Items, such as Create, Approve, Closed, etc. but these do not constrain/control standard processes and therefore is different from Initiative and cProject status management. You can therefore get away with "not doing anything" here, but again I would strongly suggest from a best practice business process that you do workshop and enable statuses. Design with the end state in mind even if this is not currently used. How would you for example reflect an Item as approved if you do not use statuses to do so?

Decision point statuses is again configured and you control, for example, that a particular status sets the decision point as complete. Not using this will therefore disqualify you from using effective lifecycle management

My concern is that users "don't want to use" certain key components that should, from a best business practice, be used. You potentially need to present a stronger case to decision makers

Not sure this helps

Regards

C

[Former Member · Accepted solution]

Sure it helps me !!

Thanks again 🙂

Best regards,

Dali