Using Serena Demand Manager

The following steps describe the general process for using Serena Demand Manager. This process assumes that SBM, Demand Center, and the Demand Plan process app have been configured and that you have access to each interface and application through roles or privilege assignments.

1. Plans are submitted. There are two types of plans:
   • "Normal" plans analyzed, assigned to a plan owner, and approved. During the approval process the budget, review frequency, reviewers, and plan portfolio are also captured. Pending plans are available in Demand Center, but items cannot be added to plans until they are approved.
   • "Pre-approved plans are immediately available in Demand Center and demand items can be added.
2. Demand items are made available through demand views. In Demand Center, the plan owner creates demand views and shares them with demand analysts.
3. The plan owner and demand analysts work together to determine each item's value and importance to your organization. Items are also sized so that the scope of the work is understood.
4. After analysis, demand items can be:
   • Moved to an approved plan.
   • Moved to a backlog.
   • Rejected.
5. The plan owner edits approved plans to:
   • Allocate resource teams to the plans.
   • Share the plans with others, who can view assigned items and analyze data for those items.
6. The plan owner can then:
   • Allocate each item to resource teams.
   • Split large items into multiple smaller items.
   • Move items to another plan or backlog.
   • Return items to analysis if they are no longer appropriate for the plan.
7. Once plan items have been assessed and allocated to a resource team, the plan owner marks them as complete.
8. At this point, normal plans are sent to review for approval or directly to in flight.
9. Work begins on items in the plan. Resources associate work items with the plan items, and record the amount of time they spend on work items.
   Note: Once a plan is in flight, demand items are "unpaused" and follow their assigned application processes. For example, if your plan contains approved items from the Change Management application, planners must manually move them from the "CAB Review/Planning" state to the "Approved" state, and then on to the "Implementation" state.
10. Review cycles occur based on a schedule set in the demand plan or on an ad-hoc basis.
11. Throughout the process, the plan owner, managers, and other stakeholders monitor actual costs and resource allocations.
12. Once work is completed on all items in a plan, the plan owner submits it for a final review, if required. If not, the plan is closed as completed.