Requirements and Release Planning

HID_using_req_plan
ccppmop151
HID_using_req_plan
Comprehensive requirements, releases, and release plans help you manage the delivery of projects, services, products, programs, applications, and features.
CA PPM
 Requirements Planning provides a framework to define and track the deliverable requirements of your business. As a product owner or stakeholder, use requirements planning to achieve the following goals:
  • Deliver intelligent requirements to team members.
  • Streamline the innovation process.
  • Capture ideas and business value in the form of requirements.
  • Associate the requirements with other investments and initiatives to flow into their release planning cycles.
  • Gather insight into how requirements fit into your overall business processes and goals.
: Verify that each user has the appropriate access rights to create, edit, view, or delete requirements, releases, and release plans.
2
Requirements Planning Workflow
Requirements planning typically follows this workflow:
  1. Create the requirements.
  2. Create one or more releases.
  3. Create one or more release plans.
  4. Add the releases to the release plans.
  5. Add the requirements to a release or a release plan.
  6. Approve the release.
The following diagram shows a typical requirements planning workflow:
Image showing a typical requirements planning workflow
Image showing a typical requirements planning workflow
 
The documentation may not match what you see in the product user interface. This difference can occur because all access to features, menus, pages, buttons, and objects is determined by your access rights. Your organization can also configure the application pages, objects, lookups, partitions, processes, and user interface. Contact your administrator if you are not able to complete any of the steps in the documentation.
Requirements
As a product manager or business analyst, you have visibility and control over your requirements from any source.
CA PPM
 can automatically categorize your requirements to deliver a complete view of customer needs. You can produce visual roadmaps, dashboards, and product plans. Define requirements and connect them to projects and their activities. 
: Improve the effectiveness of the delivered product or service by connecting the project work of different teams to the requirements that your product owners, stakeholders, or customers define.
As projects move forward and requirements evolve, verify that changing requirements do not lose their original intent. You can apply versioning and track changes. To restore from previous versions, use the approval history. You can also restrict requirement changes to authorized editors and approvers.
Requirements typically follow this workflow:
  1. Create the requirements and set their business priority.
  2. Define the requirement effort and cost budget and estimates.
  3. Create the release plan and the release.
  4. Add the requirements to the release or the release plan.
  5. Approve the release.
  6. Link each requirement to a project task.
  7. Deliver the requirement and change the requirement status to 
    Implemented
    .
Create Requirements
The first step in requirements planning is to create your requirements. The information that you define helps you trace each requirement from the planning to implementation phase. You can also create requirements from a requirement hierarchy.
Follow these steps:
  1. Open Home, and from Requirements Planning, click Requirements.
  2. Click New and complete at least the required fields.
  3. To categorize the requirement, complete the Type, Theme, and Status fields.
  4. To specify that the requirement must be delivered to satisfy an organizational commitment to a group or individual, select Committed.
  5. To define the requirement risk, select one of the following values in the Risk field:
    • Low: The requirement objectives, scope, and benefits are reasonable, clearly defined, measurable, and verifiable.
    • Medium: The requirement objectives, scope, and benefits are fairly reasonable, clearly defined, measurable, and verifiable.
    • High: The requirement objectives, scope, and benefits are not reasonable, clearly defined, measurable, and verifiable.
  6. To link the requirement to an investment, complete the Investment field. Indicate the product, application, asset, service, project, or program that delivers the requirement. The relationship provides a mechanism to group related requirements for a specific investment. For example, you can have a list of requirements that describe new features for a product. Define the product investment as the owner of the requirement.
  7. Click Save.
  8. In the Effort section, define your budgeted and estimated effort to deliver the requirement.
    • The budgeted effort amount that you see is the requirement budgeted effort. The effort does not aggregate up or down the hierarchy of requirements, but is used in the top-down planning cycles. The effort represents the amount that is allocated to deliver the requirement.
    • The estimated effort is the aggregated effort for the hierarchy of requirements. Effort estimates are used in bottom-up scoping cycles and represent the planned work to deliver a requirement. The total effort estimates include the estimated requirement effort plus its descendant requirement effort estimates. The work effort default display unit is recorded in hours. The administrator defines the work effort display unit.
    • The Aggregate Effort (Estimate) includes the estimated child requirement effort to deliver the requirement:
      Aggregate Effort (Estimate) = Effort (Estimate) + Child Requirement Effort (Estimate)
       
  9. In the Cost section, define the budgeted and estimated operating expenses and capital.
    • The budgeted cost amount is the allocated cost to deliver the requirement. The budgeted cost does not aggregate up or down the hierarchy of requirements, but is used in top-down planning cycles. The estimated cost amount is aggregated costs of the requirements hierarchy. Cost estimates are used in bottom-up scoping cycles and represent the planned cost to deliver a requirement. The aggregated amount includes the descendant requirements cost estimates.
    • Operating Expense (Budget)
      . Defines the requirement budgeted portion of the total cost for operating expenses.
    • Capital (Budget)
      . Defines the requirement budgeted portion of the total cost for capital expenses.
    • Total (Budget)
      . Displays the requirement total budgeted cost:
       
      Total Cost (Budget) = Operating Expense (Budget) + Capital (Budget)
    • Operating Expense (Estimate)
      . Defines the requirement estimated portion of the total cost for operating expenses.
    • Capital (Estimate)
      . Defines the requirement estimated portion of the total cost for operating expenses.
    • Total (Estimate)
      . Displays the total requirement estimated cost:
        Total (Estimate) = Operating Expense (Estimate) + Capital (Estimate)
    • Aggregate Operating Expense (Estimate)
      . The aggregated requirement includes the child requirement estimate of the total cost for operating expenses:
        
      Aggregate Operating Expense (Estimate) = Operating Expense (Estimate) + Child Requirement Operating Expense (Estimate)
    • Aggregate Capital (Estimate)
      . The aggregated requirement estimate of the total cost for capital expenses is based on this formula: 
      Aggregate Capital (Estimate) = Capital (Estimate) + Child Requirement Capital (Estimate)
    • Aggregate Total (Estimate)
      . The total requirement aggregated cost inclusive of child requirements is based on this formula: 
      Aggregate Total (Estimate) = Aggregate Operating Expense (Estimate) + Aggregate Capital (Estimate)
  10. In the Organizational Breakdown Structures section, define the OBS that you want to associate with the resource. Optional OBS settings are for security, organizational, or reporting purposes.
    • Department
      . Defines the financial department and entity that is associated with the requirement. The department requires to belong to the same entity as the location.
    • Location
      . Defines the location of the financial department that is associated with the requirement. The location requires to belong to the same entity as the department.
  11. Click Save and Return.
You have created a requirement and it appears in the requirements list.
You can add an attachment to a requirement, such as a requirements document or a detailed design document. Open the requirement, open the Properties menu, and click Attachments. Define the path of the document that you want to attach to the requirement and click Save and Return.
Set the Requirement Business Priorities
Typically, a panel of key stakeholders reviews the requirements for an upcoming release. The stakeholders analyze the requirements and rank them after discussing the priorities. The rankings are edited and the overall priority is calculated immediately. This step is important to assess the requirement business impact.
Follow these steps:
  1. Open the requirement, open the Properties menu, and click Business Priority.
  2. Complete these fields. For each field, specify a value of Low (1 - 33), Medium (34 - 67), or High (68 - 100).
    • Innovation & User Experience
      . Defines the requirement business priority for innovation and user experience.
    • Revenue Impact
      . Defines the requirement business priority for revenue impact.
    • Developer Productivity
      . Defines the requirement business priority for developer productivity.
    • Cost of Operations & Support
      . Defines the requirement business priority for cost of operations and support.
  3. Save the changes.
Link Requirements to Project Tasks
You can link a requirement to the project task. The task represents the effort to deliver this requirement as part of an implementation project. The linked project task is a separate relationship from the investment that owns the requirement. You can link a requirement to a task that is already linked to other requirements. However, you can only link a requirement to a single task. When you link a requirement to a project task, the requirement is
assigned to
and
associated with
the task. You can only initiate this relationship from the requirement. When necessary, you can also unlink a requirement from the project task.
If you delete the associated task, the requirement is no longer associated with the project task. The requirement is not deleted.
Follow these steps:
  1. Open the requirement.
  2. Click Link.
  3. Choose an option for an existing or new task and click Next.
  4. Follow the instructions to link to a task.
    The requirement is linked to the project task. The name of the project and task appear in the Associated Task field on the General page.
To unlink a requirement, open the requirement and click
Unlink
. The name of the project and task no longer appear in the Associated Task field on the properties page.
Requirement Hierarchy
You can group requirements into requirement hierarchies. For example, a requirement to deliver a new phone comprises requirements that describe the features of the phone. Each requirement is split into sub-requirements. Together, the requirements form a hierarchy that represents the new phone.
Add a Requirement to a Hierarchy
Follow these steps:
  1. Open the requirement.
  2. Click Hierarchy.
  3. Click Add.
  4. Select the check box next to the requirement, and click Add.
    A child requirement is added to the hierarchy. To view the requirement hierarchy, open the requirement, and click Hierarchy. To expand and collapse the list, use the plus and minus icons.
Move a Requirement in a Hierarchy
You can move a requirement from one location in a hierarchy to another location in a hierarchy. When you move a requirement after another requirement, it becomes a child to that requirement. When you move a requirement before another requirement, it becomes the parent to that requirement.
Follow these steps:
  1. Open the requirement.
  2. Click Hierarchy.
  3. Select the check box next to the requirement and click Move.
  4. Select a new requirement position. Click
    Insert Before
    or
    Insert After
    .
Indent and Outdent a Requirement in a Hierarchy
You can create hierarchical relationships between requirements. You can indent a requirement to make it a child of the requirement above it. You can designate individual requirements as parent or children. Parent requirements are top-level requirements that have child requirements that are associated with them. Child requirements are nested beneath parent requirements. The requirement above it in the hierarchy can be a top-most requirement, or a second, third, or fourth-level requirement relative to the requirement above it. You can create an unlimited number of hierarchy levels.
Follow these steps:
  1. Open the requirement.
  2. Click Hierarchy.
  3. Select the check box next to the requirement to indent or outdent, and select one of the following options:
    • Indent
      . The selected requirement appears one level under the nearest higher-level requirement. A plus icon appears in front of the higher-level requirement.
    • Outdent
      . The selected requirement appears as outdented relative to the requirement above it.
Remove a Requirement from a Hierarchy
You can reduce the aggregate totals for budget and estimated cost and effort for any parent (ancestor) requirements in the hierarchy. To accomplish this goal, remove a requirement from the hierarchy. Consider this information when removing requirements from a hierarchy:
  • Removal of a child requirement includes any lower-level requirements relative to the child.
  • The requirement is not deleted; it is only removed.
Follow these steps:
  1. Open the requirement.
  2. Click Hierarchy.
  3. Select the check box next to the requirement, and click Remove.
Requirement Dependencies
You can indicate dependencies existing between requirements. A dependency can occur when a requirement requires completing before another can begin.
Add a Requirement Dependency
You can create dependencies to other requirements, or a mutual dependency between requirements.
 
For example, you have a feature to build a new phone, requirement WOW Phone (RA). This requirement has a dependency on two other requirements: Security Requirement (R1), and Bluetooth Requirement (R2). The feature requires requirement R1 (
needed by
); however, R2 depends on the feature (
depends upon
).
Follow these steps:
  1. Open the requirement to create a dependency relationship.
  2. Click Dependencies.
  3. Click Add.
  4. Select the check box next to the requirement to add as a dependency, and click Add.
  5. Choose one of the following options:
    • Mutual Dependency
      . Defines the selected requirement as mutually dependent on the target requirement.
    • Needed By
      . Defines the selected requirement as depending upon the target requirement.
    • Depends Upon
      . Defines the selected requirement for the target requirement.
    The dependency relationship is created.
To remove a requirement dependency, open the requirement, click Dependencies, select a dependency, and click Remove.
Delete a Requirement
You can delete a requirement at any time, with the following exceptions:
  • You cannot delete a requirement that is assigned to a release.
  • You cannot delete a requirement having the 
    Approved
     or 
    Rejected
     status.
Deleting a requirement that is linked to a project task does not delete the task. Instead, the association with the linked task is removed.
Follow these steps:
  1. Open Home, and from Requirements Planning, click Requirements.
  2. Select the check box next to the requirement and click Delete.
Releases
A release represents a new future deliverable and includes requirements, priorities, processes, an audit trail, and a dashboard.
Releases typically follow this workflow:
  1. Define the investments that are associated with the release.
  2. Create the release.
  3. Define the projects or programs that are implementing the release.
  4. Define the release effort budget and estimates.
  5. Define the release cost budget and estimates.
  6. After you create the release plan, add the release to the release plan.
  7. After you add the requirements to the release plan, approve the release.
  8. Link the release to a project or program.
Create a Release
The first step when working with releases is to create the basic information for a release.
Follow these steps:
  1. Open Home, and from Requirements Planning, click Releases.
  2. Click New.
  3. Create the release. These fields require a description:
    • Investment
      . Indicate the product, application, asset, service, project, or program representing the work to deliver a release. Unlike the project or program that tracks the release implementation effort, the investment that you define is the owner of the release.
    • Associated Project/Program
      . Displays the name of the project or program that is linked to the release. The release can only be linked to one project or program.
    • Currency Code
      . Defines the currency that is used to calculate the release budget and estimate values.
    • Effort (Budget)
      . Defines the budgeted effort to deliver the release.
    • Effort (Estimate)
      . Displays your organization estimated effort amount to deliver the release.
  4. Click Save.
  5. In the Cost section, define the budgeted and estimated capital and operating expenses for the release.
    • Operating Expense (Budget)
      . Defines the budgeted operating expenses from the total cost for a release.
    • Capital (Budget)
      . Defines the budgeted capital expenses from the total cost for a release.
    • Total Cost (Budget)
      . Displays the total budgeted cost for the release that is based on this formula: 
      Total Cost (Budget) = Operating Expense (Budget) + Capital (Budget)
    • Operating Expense (Estimate)
      . Displays the estimated portion of the total cost attributed to operating expenses of the release.
    • Capital (Estimate)
      . Displays the estimated portion of the total cost attributed to capital expenses of the release.
    • Total Cost (Estimate)
      . Displays the total estimated cost of the release that is based on this formula: 
      Total Cost (Estimate) = Operating Expense (Estimate) + Capital (Estimate)
  6. In the Organizational Breakdown Structures section, define the OBS that you want to associate with the resource for security, organizational, or reporting purposes.
  7. Click Save and Return.
You have created a release and it appears in the releases list. When appropriate, you can approve a release by updating the release status to 
Approved
.
You can add an attachment to a release. Open the release, open the Properties menu, and click Attachments. Define the path of the document that you want to attach to the release and click Save and Return.
Link a Release to a Project or Program
Link the release to a project or program to track the release implementation effort. When linked, the release is assigned to the project. The linked project or program is a separate relationship from the investment that owns the release. You can link an unlimited number of releases to a project or program. However, you can only link a release to one project or program. You can establish this relationship from the release or from the project or program. When necessary, you can also unlink a release from the project or program.
Follow these steps:
  1. Open the release.
  2. Click Link.
  3. Click the Choose Existing option and click Next.
  4. Select the option next to the project, and click Save and Return. The release is linked to the project or program.
    The name of the project or program displays in the Associated Project/Program field on the General page.
  5. To unlink a release, open the release and click Unlink. 
    The name of the project or program no longer displays in the Associated Project/Program field on the properties page.
Define the Release Schedule
Specify the release scheduling to define the release start and finish dates, alpha and beta start dates, and the scheduled date of release to the market.
Follow these steps:
  1. Open the release.
  2. Click Properties, Schedule.
  3. Define the release schedule:
    • Start
      . Defines the scheduled start date of the release.
    • Finish
      . Defines the scheduled finish date of the release.
    • Alpha
      . Defines the alpha start date of the release.
    • Beta
      . Defines the beta start date of the release.
    • Release to Market
      . Defines the scheduled date of release to the market.
  4. Click Save and Return.
Add Requirements to a Release
After associated requirements to investments, you can group them into releases. Add a requirement to a single release using the release or from the release plan.
Follow these steps:
  1. Open the release.
  2. Click Requirements.
  3. Click Add.
  4. Select the check box next to the requirement and click Add.
    The requirement displays on the release requirements page.
  5. Change the requirement status to Assigned to a Release.
To remove a requirement from a release, open the release, click Requirements, select the check box next to the name of the requirement to remove, and click Remove.
Monitor Requirement Business Priorities
You can monitor the requirement business priorities that are assigned to a release. You can view all of the requirements that you have assigned to the release. In addition, you can view the overall business priority, innovation and user experience, revenue impact, developer productivity, and cost of operations and supports for the requirement.
Follow these steps:
  1. Open the release.
  2. Click Priorities.
Monitor Release Performance
You can monitor a release performance to view the following information about the release:
  • Scorecard
    . Displays the requirements that have been added to the release based on their scorecard. The requirements are linked to project tasks. The status is based on the associated tasks status.
  • Requirements By Theme
    . Displays a graph displaying requirements by theme.
  • Requirements By Priority
    . Displays a graph displaying requirements by priority.
  • Business Priority
    . Displays a grid displaying requirements by business priority.
  • Requirements By Risk
    . Displays a graph displaying requirements by risk.
You can customize the page using
CA PPM
 Studio. Open the Release Layout portlet page in Studio and modify the Dashboard tab content.
You can configure the portlets on the page. For example, on the Scorecard you can reorder the columns. On Requirements by Theme, you can change the chart type from pie to funnel, bar, and so forth. Select Configure on the Options menu.
Follow these steps:
  1. Open the release.
  2. Click Dashboard.
Delete a Release
You can delete a release at any time. When you delete a release with added requirements, the requirements become unassigned to the release.
Follow these steps:
  1. Open Home, and from Requirements Planning, click Releases.
  2. Select the check box next to the release and click Delete.
  3. Confirm the deletion.
Release Plans
Release plans provide you with an intuitive and quick way to assign requirements across upcoming releases on a per-investment basis. Use release plans to map one or more requirements to a release.
Release plans typically follow this workflow:
  1. Create the investments that comprise part of your release plan.
  2. Create the release.
  3. Create the requirements.
  4. Create the release plan.
  5. Add the investments to the release plan that own the releases that comprise part of the release plan.
  6. Add the release to the release plan.
  7. Add the requirement to the release plan.
: Apply the following best practices when working with release plans:
  • Link release plans to a project plan and then implement them.
  • Link requirements to the project task that represents the effort to deliver this requirement.
  • Use the Release Dashboard to monitor the performance of a release. This dashboard shows the status of the tasks and provides insight into the execution of the deliverables.
  • Implementing a release plan allows for the traceability of requirements.
 
Create a Release Plan
The first step when working with release plans is to create the basic information for the plan.
Follow these steps:
  1. Open Home, and from Requirements Planning, click Release Planning.
  2. Click New.
  3. Enter the information for the release plan and click Save. The following field requires a description
    :
    • Currency Code
      . Defines the currency to calculate the release plan budget and estimate values.
  4. Click Save and Return.
The new release plan displays on the Release Plans page.
After you create a release plan, you can view and optionally edit the release plan details by opening the release plan and clicking Properties from the Release Planner page. On this page, the Total Cost (Budget) field displays the total budgeted cost for the release that is based on this formula:
Total Cost (Budget) = Operating Expense (Budget) + Capital (Budget)
Add an Investment to a Release Plan
You can add an investment to a release plan, and the investment forms part of the release plan.
Follow these steps:
  1. Open the release plan, and click Contents.
  2. Click Add.
  3. Select the investment to add to the release plan, and click Add.
    The investment appears in the contents list.
You can remove an investment from the release plan. Open the release plan, and click Contents on the Release Planner page. Select the check box next to the investment and click Remove.
Update the Release Planner
Plan releases using the Releases and Requirements portlets on the Release Planner page.
Follow these steps:
  1. Open the release plan.
  2. For Releases, edit these fields:
    • Operating Expense (Budget)
      . Defines the budgeted operating expenses from the total cost for a release.
    • Capital (Budget)
      . Defines the budgeted capital expenses from the total cost for a release.
    • Effort (Budget)
      . Defines the budgeted effort to deliver the release.
    • Start Date
      . Defines the scheduled start date of the release.
    • Finish
      . Defines the scheduled finish date of the release.
    • Alpha
      . Defines the alpha start date of the release.
    • Beta
      . Defines the beta start date of the release.
    • Release to Market
      . Defines the scheduled date of release to the market.
  3. For Requirements, edit these fields:
    • Operating Expense (Budget)
      . Defines the requirement budgeted portion of the total cost for operating expenses.
    • Capital (Budget)
      . Defines the requirement budgeted portion of the total cost for capital expenses.
    • Effort (Budget)
      . Defines your organization budgeted effort amount to deliver the requirement.
    • Release
      . Specifies the name of the release that is assigned to the requirement. Select a release to assign to the requirement.
Add a Release to a Release Plan
Add the existing releases to your release plan. Investments-owned releases that are linked to the release plan can be added to the release plan. When you add a requirement-linked release to a release plan, the associated requirement is automatically added to the release plan. The added requirements display in the list in the Requirements portlet on the release plan Release Planner page.
Follow these steps:
  1. Open a release plan.
  2. In the Releases portlet, click Add Release.
  3. Select the check box next to the release and click Add.
    The release is added to the Releases portlet on the release plan Release Planner page.
Approve a Release in a Release Plan
When appropriate, approve a release in the release plans.
Follow these steps:
  1. Open a release plan.
  2. In the Releases portlet, select the check box next to the release and click Approve Release.
    The release status changes to Approved and a yellow checkmark appears in the Approved column.
You can also approve a release using the releases list page and the release properties page.
Remove a Release from a Release Plan
When appropriate, remove a release from the release plans.
Follow these steps:
  1. Open a release plan.
  2. In the Releases portlet, select the check box next to the release and click Remove Release.
    The release is removed from the Releases portlet. When you remove a requirements-linked release from the release plan, the requirements are also removed from the release plan.
Add a Requirement to a Release Plan
When appropriate, add a requirement to the release plans.
Follow these steps:
  1. Open a release plan.
  2. In the Requirements portlet, click Add Requirement.
  3. Select the check box next to a requirement and click Add.
    The requirement is added to the release plan and displays in the Requirements portlet. If a release plan contains a release that is linked to a requirement, the associated requirement is automatically added to the release plan.
View a Requirement Hierarchy for a Release Plan
You can view a requirement hierarchy by opening a release plan and looking in the Requirements portal. You can only view the requirement hierarchy on the page.
Use the Plus and Minus icons to the left of the requirement name to expand and collapse the list.
View a Requirement Dependency in a Release Plan
You can link directly to a requirement dependencies list from a release plan.
Follow these steps:
  1. Open a release plan.
  2. In the Requirements portlet, click the dependencies icon next to the requirement.
    The requirement dependencies page appears.
Remove a Requirement from a Release Plan
When necessary, you can remove a requirement from the release plans. When you remove a requirement, the requirement is not removed from its associated release.
Follow these steps:
  1. Open the release plan.
  2. In the Requirements portlet, select the check box next to the requirement and click Remove Requirement.
    The requirement is removed from the Requirements portlet on the release plan release planner page.
View the Release Plan Roadmap
The release plan roadmap is a graphical, time-scaled representation of upcoming releases for a product, service, or other investment. The release plan roadmap represents the game plan that your organization has to release the new product, service, or other investment.
Follow these steps:
  1. Open the release plan.
  2. Click Roadmap.