Skip to the content

processMax 2i and 3i Release 8.0 - 8.07

Date Alert Type Portals Affected
08/07/2009 Process Definition All

 

 

Issue:

Confusing messages and results may occur when setting certain statuses to specific work products on the Process Management Programs portal. Very few customers are affected by this alert, and this alert is unrelated to accepting new processMax product releases. It affects your own internal process definition work on the process Management Programs portal.

Solution:

In any release that is 8.0 and higher, on the Process Management Programs portal there is a step named 'Upgrade instantiated portals to selected composition' that has an output named 'Instantiated Portals Upgrade'.

On 'Instantiated Portals Upgrade', do NOT select the status 'Ready for Upgrade' because you may get confusing messages and confusing results. Since 'Instantiated Portals Upgrade' will affect your operational portals, do NOT select 'Ready for Upgrade'. You may continue to select 'Ready for Analysis'.

In any release that is 8.0 and higher, on the Process Management Programs portal there is a step named 'Customize and test process changes' that has an output named 'Standard Processes Upgrade'.

On 'Standard Processes Upgrade', we recommend against selecting the status 'Ready for Upgrade' because you may get confusing messages and confusing results. Since 'Standard Processes Upgrade' does not affect your operational portals, you may choose to go ahead with selecting this status. In any case, it causes no harm to continue to select 'Ready for Analysis'.

pragma Systems plans are that in future processMax releases, processMax will enforce the Customization and Testing Guidelines, which is a reference material on the 'Customize and test process changes' step referenced above.

Date Alert Type Portals Affected
10/19/2009 Process Definition All Compliant Projects

 

 

Issue:

Clarification of the lanuguage for the step 'Plan to perform the project planning process' (to satisfy Project Planning GP 2.2).

Description:

The step description for 'Plan to perform the project planning process' and the text in its associated Task 79 are correct, but both may be replaced in a future release with the very specific language in the solution below.

Solution:

For use until first release AFTER 8.1:

Involve stakeholders as defined in Stakeholder Involvement.

Using best engineering and management judgement, plan to perform the project planning process.

Task 79 'Plan to perform the project planning process' should be set to Authorized before starting this step.

Select the output named 'Estimation of Work' and find Control Number 17. Double click and select Update. Complete the Detailed Description of this record.

In EOW 17, unless the planning effort is expected to be long and complex, it is unlikely that selecting a work product for:

'Tracked Work Products Maintained in processMax with Measurable Attribute' or

'Tracked Work Products Not Maintained in processMax with Measurable Attribute',

would be helpful in monitoring the planning work.

However, selecting the size for the Project Plan in 'Tracked Work Products Maintained in processMax with Measurable Attribute' could be helpful.

Select 'Identified' as the status and submit EOW 17.

Identify personnel via the additional assignees on Task 79 to assist in estimating this planning work and to assist in documenting the basis of their estimations in EOW 17.

With the identified personnel (i.e., additional assignees, who were already, or are now automatically added as, Stakeholders), 'Update' the fields in the various status sections of EOW 17 adequate to set its status to 'Cost Estimated'.

Revise the Project Plan's 'Planning Plan' section to summarize what was done on this step.

Each person who worked on Task 79 should revise their actual effort on Task 79 at least once per day for each day that they work on Task 79. For very small projects, Task 79 should take only a couple of hours, total. The primary assignee should set Task 79 to 'Completed' when it is completed. Otherwise, set its status to 'In Progress'.

Set the status of Task 79 to 'Completed' when the above work is done.

Linkage from Task 4 'Transition this project's work to processMax . . .' , which should already be marked as 'Completed', to Task 79 can be added at this time to the Work Breakdown Structure/Schedule (WBSS). The WBSS will be synchronized automatically, even if linkages are not in yet. All linkages will be added later as part of another step.

Move on to another authorized task, such as Task 51 'Monitor and control the project'.

Update each output, as needed.

Update and initiate Requests for Corrective Actions, as needed.

 

Date Alert Type Portals Affected
08/30/2010 Content PMP only

 

 

Issue:

There is no Glossary entry for 'Steering Committee Members'.

Solutions:

In the Glossary, for Steering Committee Members, see 'Process Management Programs Steering Committee'.

Date Alert Type Portals Affected
04/01/2010 Process Definition All Compliant Projects

 

 

Issue:

The step description for the step named 'Transition to processMax' includes language that applies only to projects that are new starts, but actually the language applies to all projects.

Solution:

On your portal, find the step named 'Transition to processMax', if, near the end of the step description you see,

". . . then submit one or more tailoring requests.

WHEN TRANSITIONING A NEW-START, read and perform the next section:

When processMax is deployed on a project that is a new-start, find the Task named 'Plan to plan the project', select 'Update' from its Actions popup menu, revise its pre-populated fields if needed, and complete the section adequate to set its status to 'Authorized'. Enter the Planned Start Date to be today or as soon as possible and enter the Planned End Date, based on a review of the steps associated with that Task. These dates will constrain MS Project, which is necessary in this early Task. Select 'No' for Level of Effort.

READ AND PERFORM the next section:

Find the as-delivered Task, or create a new Task, to 'Monitor and control . . .' the work . . ."

Be aware that in release 8.1 and higher, it is planned for the step description to read:

" . . . then submit one or more tailoring requests.

READ AND PERFORM the next section:

When processMax is first deployed on a project regardless of whether or not the project is a new-start, find the Task named 'Plan to plan the project', select 'Update' from its Actions popup menu, revise its pre-populated fields if needed, and complete the section adequate to set its status to 'Authorized'. Enter the Planned Start Date to be today or as soon as possible and enter the Planned End Date, based on a review of the steps associated with that Task. These dates will constrain MS Project, which is necessary in this early Task. Select 'No' for Level of Effort.

Find the as-delivered Task, or create a new Task, to 'Monitor and control . . .' the work . . ."

Basically, the heading and text that previously applied only to projects that are new-starts now applies to all projects as they transition to processMax.