- Introduction (What & Why)
- Definition & Uses of Requirements
- The Challenges in Requirements in Software
- Revisit the Agile Taxonomy
- The Transition from Traditional to Agile
- Rethink the Agile Portfolio
- Guidelines and Characteristic of Taxonomy
-
A presentation slide deck from Rego University 2022. The course discusses factors that differentiate Requirements. -
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 Executive Dashboard portlet displays information regarding projects the user has security rights to view. It provides a one-stop place for the PMO or management to view all critical information about projects. The portlet not only displays status indicators as well as dates for late items, variances and days late, but also displays the project status fields from the Status Report sub-object. -
The Executive Dashboard portlet displays information regarding projects the user has security rights to view. It provides a one-stop place for the PMO or management to view all critical information about projects. The portlet not only displays status indicators as well as dates for late items, variances and days late, but also displays the project status fields from the Status Report sub-object. -
The Executive Dashboard portlet displays information regarding projects the user has security rights to view. It provides a one-stop place for the PMO or management to view all critical information about projects. The portlet not only displays status indicators as well as dates for late items, variances and days late, but also displays the project status fields from the Status Report sub-object. -
This configuration and accompanying process allows users to capture Financial and Non-Financial (Metrics, Soft, etc.) Benefit in a custom sub-object, then programmatically create an out-of-the-box Benefit Plan with just the Financial Portion from the custom sub-object. The solution is comprised of:- Sub-Object (Benefit Plan Details, Parent = Project)
- Process: Create Benefit Plan (uses sub-object as primary input, native BP is output)
- Process: Update sql - Cost Benefit Plans (one-time script to update Projects)
- Ensure on the Benefit Details List view the Planned and Realized Amounts are displayed
- Modifying the Create Benefit Plan Process in support of a BP naming convention consistent with local PMO Practices
- Modifying the Create Benefit Plan Process to link the BP to the Cost Plan of Record
- Creating a Portlet that pulls together rows of data from the sub-object across multiple projects in a summarized view as well as a detailed view
-
This configuration and accompanying process allows users to capture Financial and Non-Financial (Metrics, Soft, etc.) Benefit in a custom sub-object, then programmatically create an out-of-the-box Benefit Plan with just the Financial Portion from the custom sub-object. The solution is comprised of:- Sub-Object (Benefit Plan Details, Parent = Project)
- Process: Create Benefit Plan (uses sub-object as primary input, native BP is output)
- Process: Update sql - Cost Benefit Plans (one-time script to update Projects)
- Ensure on the Benefit Details List view the Planned and Realized Amounts are displayed
- Modifying the Create Benefit Plan Process in support of a BP naming convention consistent with local PMO Practices
- Modifying the Create Benefit Plan Process to link the BP to the Cost Plan of Record
- Creating a Portlet that pulls together rows of data from the sub-object across multiple projects in a summarized view as well as a detailed view
-
This configuration and accompanying process allows users to capture Financial and Non-Financial (Metrics, Soft, etc.) Benefit in a custom sub-object, then programmatically create an out-of-the-box Benefit Plan with just the Financial Portion from the custom sub-object. The solution is comprised of:- Sub-Object (Benefit Plan Details, Parent = Project)
- Process: Create Benefit Plan (uses sub-object as primary input, native BP is output)
- Process: Update sql - Cost Benefit Plans (one-time script to update Projects)
- Ensure on the Benefit Details List view the Planned and Realized Amounts are displayed
- Modifying the Create Benefit Plan Process in support of a BP naming convention consistent with local PMO Practices
- Modifying the Create Benefit Plan Process to link the BP to the Cost Plan of Record
- Creating a Portlet that pulls together rows of data from the sub-object across multiple projects in a summarized view as well as a detailed view
-
The Financial Summary by Transaction Class provides a visual graph for each year’s financial picture for multiple years. Report contains the following items: KPIs: Displays total benefit, capital, expense and net cash flow for the selected filter criteria Grid: Displays year wise break up of benefit, capital, expense and net cash flow for the selected filter criteria Graph: Benefit, capital, expense and net cash flow are depicted in graphical way for multiple years. This report will show the user where they need to concentrate their efforts in order to meet financial commitments. User can further narrow their search by OBS Type & Path. -
Aligning work to organizational strategy is a fundamental requirement in today's ever-changing marketplace. High performing organizations are moving beyond basic connections to introduce strategic hierarchies that are tied to real measurements of business value via Clarity's Objectives and Key Results (OKRs). Join our expert guides as they present key concepts, best practices, and the evolution of strategic alignment.

