A process creating a new Cost Plan.
Cost Plan properties:
|
790 results
-
-
This training document is a Rego Consulting Quick Reference Guide to assist with creation of agreements in Clarity’s Modern User Experience. Agreements can be created between Project, Ideas and Custom Investments. The Agreement can convey things needed for predecessors and successors while defining appropriate dates to meet the agreement. Blueprints can be leveraged to customize the agreements as required.
-
A Quick Reference Card to assist in the creation of project level dependencies. You can create dependency relationships that exist between investments in a portfolio using the dependencies page of project or program properties. A dependency can occur when a task in an investment requires to be completed before a task in another investment can begin.
-
PMOs/EPMOs are feeling some pressure from Agile disruptors in their organizations. Some Agile purists insist that they can do everything with an Agile tool and no PMO governance, but this really isn’t the case. If you belong to a PMO or EPMO, this session will help you to better collaborate with your Agile counterparts in finding better and more holistic solutions to value delivery. Tips on how to use Agile principles in your talking points will also be shared.
-
PMOs/EPMOs are feeling some pressure from Agile disruptors in their organizations. Some Agile purists insist that they can do everything with an Agile tool and no PMO governance, but this really isn’t the case. If you belong to a PMO or EPMO, this session will help you to better collaborate with your Agile counterparts in finding better and more holistic solutions to value delivery. Tips on how to use Agile principles in your talking points will also be shared.
-
A presentation slide deck from Rego University 2022. The document reviews creating views and using Apps in Rally. Then digs into creation of Dashboards.
- Refresh on Creating View and Using Apps
- Introduction to Concepts of Dashboards
- Configuring Dashboards & Apps
- Patterns of Useful Dashboards
- Dashboard Patterns
- Examples
- Exercise: Lets create a Dashboard
-
The Dashboard: Baseline Comparison portlet compares multiple baselines on a single project. The portlet is added to the dashboard page of a project and will pull in both baselines for that project and perform a comparison between the two. This portlet provides a quick way for project managers to view the differences between their baselines, especially if they have multiple members updating the project.
-
The Dashboard: Baseline Comparison portlet compares multiple baselines on a single project. The portlet is added to the dashboard page of a project and will pull in both baselines for that project and perform a comparison between the two. This portlet provides a quick way for project managers to view the differences between their baselines, especially if they have multiple members updating the project.
-
The Dashboard: Baseline Comparison portlet compares multiple baselines on a single project. The portlet is added to the dashboard page of a project and will pull in both baselines for that project and perform a comparison between the two. This portlet provides a quick way for project managers to view the differences between their baselines, especially if they have multiple members updating the project.
-
The Dashboard: Change Requests portlet gives an overview of all change requests on the project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The portlet sorts the issues first by priority and then by target date. It displays the name, owner, status, target date, approved by, and the priority.
-
The Dashboard: Change Requests portlet gives an overview of all change requests on the project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The portlet sorts the issues first by priority and then by target date. It displays the name, owner, status, target date, approved by, and the priority.
-
The Dashboard: Change Requests portlet gives an overview of all change requests on the project. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. The portlet sorts the issues first by priority and then by target date. It displays the name, owner, status, target date, approved by, and the priority.