790 results
-
Course Description: Do you want to improve the success of your projects? This class will discuss some lessons learned on making projects more successful. We will discuss things like: • Developing robust test plans, creating effective use and test cases, and implementing test scripts that make sense.
- Why failures occur and what you can do to minimize the impact and plan for success—including a case study on lessons learned.
- Developing, testing, fine-tuning, and executing deployment plans for success.
-
Course Description: Do you want to talk to other customers that are using or plan to use project management? In this moderated round table, customers can share experiences and provide insights on process, configurations, challenges, and successes. We will divide into small groups and discuss customer selected topics—100% sharing
-
Course Description: Do you want to analyze the cost and utilization of Agile development resources? Do you struggle to integrate financial information with work execution information from Agile tools such as Rally Software®, Jira, or VersionOne? This session explores reporting and dashboarding approaches to provide technology leaders with KPIs and trends for Agile execution, along with views that relate Agile team activity with cost and delivery.
-
Course Description: Have you ever thought of using Clarity PPM for surveys or quality audits? Would you like to create dashboards with metrics from surveys, lessons learned, project audits, and quality? In this class, we will review a customer use case where all of this was done in Clarity PPM—linking to SharePoint to capture survey results, then producing dashboards inside of PPM and SharePoint based on very specific metrics.
-
Course Description: Struggling to figure out how to best organize your blueprints? This class will walk through best practice blueprint design, including how many to have, how to use channels, using custom subobjects within the blueprint, and swapping blueprints at various project stages to mimic project phases or ideas. We’ll highlight some of the creative ways we’ve seen blueprints used in client implementations.
-
Do you want to add interfaces to your CA PPM instance? This class will review the pros and cons of various integration methods and provide best practice on how to handle various interfaces. We’ll walk you through specific interface examples and showcase Rego’s pre-built interface sets you can leverage to reduce the time and cost of implementation.
-
Most organizations use CA PPM as part of an annual planning process, in conjunction with an ITFM or financial system. There is often a struggle to know where CA PPM fits into the process and how to effectively connect the data and processes between these tools. In this class, we will discuss how a PPM tool and an ITFM tool fit together to support annual planning.
-
Are you on an older version of CA PPM? Do you want to understand the value of the new features and functions in recent versions? Have you seen the new UX and do you wonder when is the right time to move over? This class is a demonstration of the new UX, new features in both classic and new UX, and the value of these features for customers.
-
Do you want to know the best practices for implementing program management within CA PPM? More and more companies are moving to a form of program management, where projects may not be individually funded, but programs are funded instead. We will walk through how to leverage Clarity for program management, including use cases and what can and cannot be used OOTB.
-
Does project and idea estimation take too long and lack visibility? This class will address one of the most common pain points within organizations: how to involve the right people within a timely project estimate. Learn some Rego best practices for defining, calculating, and modifying idea and project estimates, so you can increase throughput and ROI.
-
The Re-Baseline via Change Request process is a simple method for a member of the project (who has the ability to create change requests) to request a re-baseline of the project without the project manager having to perform it. First, the user must create the change request. The user must then start the process within the change request by using the Processes tab. Once started, the process will route an action item to the Project Manager. If rejected, the process will end and the user must start it again (if needed). If approved, the process will then baseline the project and close out the change request.
-
The Re-Baseline via Change Request process is a simple method for a member of the project (who has the ability to create change requests) to request a re-baseline of the project without the project manager having to perform it. First, the user must create the change request. The user must then start the process within the change request by using the Processes tab. Once started, the process will route an action item to the Project Manager. If rejected, the process will end and the user must start it again (if needed). If approved, the process will then baseline the project and close out the change request.
-
The Re-Baseline via Change Request process is a simple method for a member of the project (who has the ability to create change requests) to request a re-baseline of the project without the project manager having to perform it. First, the user must create the change request. The user must then start the process within the change request by using the Processes tab. Once started, the process will route an action item to the Project Manager. If rejected, the process will end and the user must start it again (if needed). If approved, the process will then baseline the project and close out the change request.
-
The Convert Incident to Task workflow process allows users to quickly create tasks from incidents without the need to input the information twice. It utilizes a newly added checkbox and project fields on the incident object. The user will need to select the project that he or she wants the task added to using the “Project” field on the incident object. Next, the “Convert to Task” checkbox will kick off the process. Once ticked, the process will perform the necessary actions to create a task on the specified project.
-
The Convert Incident to Task workflow process allows users to quickly create tasks from incidents without the need to input the information twice. It utilizes a newly added checkbox and project fields on the incident object. The user will need to select the project that he or she wants the task added to using the “Project” field on the incident object. Next, the “Convert to Task” checkbox will kick off the process. Once ticked, the process will perform the necessary actions to create a task on the specified project.
-
The Convert Incident to Task workflow process allows users to quickly create tasks from incidents without the need to input the information twice. It utilizes a newly added checkbox and project fields on the incident object. The user will need to select the project that he or she wants the task added to using the “Project” field on the incident object. Next, the “Convert to Task” checkbox will kick off the process. Once ticked, the process will perform the necessary actions to create a task on the specified project.
-
The Grant Project Edit Rights workflow process allows a project manager to grant project edit rights to another user without contacting an administrator. The workflow uses the Out-of-the-box field for Business Owner. The script starts when the field is updated. It will assign project edit rights to whichever user is added to the Business Owner field. This process can be modified to grant project edit rights to any user within a project field.
-
The Grant Project Edit Rights workflow process allows a project manager to grant project edit rights to another user without contacting an administrator. The workflow uses the Out-of-the-box field for Business Owner. The script starts when the field is updated. It will assign project edit rights to whichever user is added to the Business Owner field. This process can be modified to grant project edit rights to any user within a project field.
-
The Grant Project Edit Rights workflow process allows a project manager to grant project edit rights to another user without contacting an administrator. The workflow uses the Out-of-the-box field for Business Owner. The script starts when the field is updated. It will assign project edit rights to whichever user is added to the Business Owner field. This process can be modified to grant project edit rights to any user within a project field.
-
The Give RM Calendar & Time Rights workflow process can be run through the "Execute a Process" job. The workflow will execute a query that gives a Resource Manager Calendar Edit and Timesheet Edit rights for their resources. These rights are not inherent for Resource Managers when they are named as an individual’s resource manager.
-
The Project Close Process workflow process aides the Project Manager in some routine close out tasks that accompany every project. Marking the project inactive starts the process and it will continue down one of two paths:
- Once the project is inactive, the process will then check to see if there is no remaining estimate to complete (ETC) still on the project. If there is ETC leftover, then the process will go into a waiting state for 14 days to allow the project manager to cleanup or to cancel the process if it was done in error. After 14 days, the process will check to see if the project is active. If the project is active, then the process will end. However, if the project is still inactive, the process will continue with the closeout activities even if there is ETC still on the project.
- If the project is marked inactive after the initial 14 days of waiting if applicable, then the process will immediately move to the closeout activities.
- Turning off time entry for the project, tasks and project members
- Updates the ETC, proposed ETC, and pending estimates to 0
- Updates the task status and assignment status to Completed
- Sets the task, assignment and project finish dates to today’s date only if the finish dates are after the process run date
- Sets all Risks and Issues to Closed with a resolution of “## This was closed automatically as part of the project close process ##”
- Set future hard allocation and allocation finish dates to today when the date is after today’s date
-
The Status Report Publish workflow process pushes values from the status report sub-object to the parent project object. The process is started when the user ticks the “Publish” Boolean field on the status report (custom field added). This workflow will update the project object with the overall status indicator, the status comment, the previous overall status, and the as of date. This eliminates the project manager having to update the fields in both the status report and the project overall.