-
Learn about the various techniques and emerging methods companies are taking to capitalize Agile work. You'll learn how some companies are moving away from timesheets and using models based on story points and team rates to generate capitalization reporting. -
It is quite common for Rally and Jira to coexist. However, connecting them effectively enhances the value stream for development teams and product owners. Learn what is available to make this happen along with some typical design patterns. -
Rally Software introduction including high level feature and functionality for Agile and portfolio planning and tracking, analytics and reporting, and overall benefits of Rally in the marketplace along with a product demo. -
The Dashboard: Project Status Single-line portlet gives an overview of the project overall status as well as the status indicators on the "current" status report object. The portlet will pull the "id" from the page it is placed on, so this portlet is usually placed on the project dashboard tab. This portlet displays the report date, symbols relating to the overall status, scope, schedule, cost/effort, and the overall explanation across a single line in the portlet. -
This portlet displays the % allocation of resources to projects. The portlet shows if the resource is allocated to the projects as an individual resource or as part of an Agile team, in which case it will display the resource % allocation to the team and what that will represent in terms of % allocation to the project. The Total Allocation % display the allocation of the resource to all investments is allocated to. Remaining Capacity and Over/Under columns will help identify the resources that still have availability and the ones that are over allocated. -
It is quite common for Rally and Jira to coexist. However, connecting them effectively enhances the value stream for development teams and product owners. Learn what is available to make this happen along with some typical design patterns. -
Course Description: Are you struggling to implement Agile tools at your organization alongside Clarity PPM? This class will review best practices for implementing Agile tools in conjunction with Clarity PPM while living in a bimodal world. We will discuss how Clarity PPM can govern both types of work and teams and how Agile tools should interface with Clarity PPM. -
Course Description: This class will provide a list of daily and weekly activities that every project manager should follow to leverage Clarity PPM more effectively. -
The PM Stalker – Submit Status Report workflow process will email any project manager that has not submitted a status report in the last two weeks. This process will ensure that all status reports are kept up-to-date and provide management with a reliable overview of the status on the project. -
The Grant Team Project Edit Rights workflow allows a project manager to grant Project – Edit Management rights to all users staffed on the project. This workflow saves not only the project manager time by allowing all users on the project to update information, but also saves the administrator time from granting each resource these rights individually. The process will also remove any rights from members that have been removed from the project. -
The Project Compliance Stalker – PM sends an email to Project Managers (and also their managers if so desired) at a set interval to alert them to project compliance issues. Areas of compliance that are reviewed include: stale project tasks (stale = past due date), late issues and risks (past due date) and late status reports. -
This process, Shift Project Dates, helps Project Managers change an entire Project / Idea’s dates to a new start date. Once the three attributes are added to the Idea /Project Views, the PM can trigger the process by entering a date in the New Start Date field and checking the Shift checkbox. The process runs automatically on Save. The process calculates the date difference between the original Start Date and New Start Date then shifts all Allocation, Task, and Assignment dates by the calculated difference. For example, if a Project is set to begin on January 1st and needs to be pushed to a February 1st start date, the process first determines that there are 31 days between the original start date and the new date. Next the process increases the start date for each Task, Allocation and Assignment by 31 days. NOTE: The process will shift Allocation dates regardless of resource restrictions such as a Termination Date or non-working time as marked on their calendar. The Team page will reflect the Available Start and Finish as shifted by the process, but the Allocation hours and % will take unavailable time into account. For example, if a shift process sets the start date for a resource to be after their date of termination the dates will change by the date difference, but the Allocation hours will correctly be calculated as zero.
Copyright 2023 • Rego Consulting Corporation • Privacy Policy