Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

8.
Supply < Demand What Questions are we Trying to Answer? Business (external): • Why aren’t my projects getting resources? How are projects prioritized? • How can we get more resources for projects? What am I getting for my [allocated] IT budget? IT (internal): • Why aren’t my business partners’ projects getting resources? How are projects prioritized? How do we prioritize projects, operations and break-fix support while servicing multiple constituents (business and IT)? • Why are we working on [this activity] and not [my project]? When can we lock-in Committed Dates? How can we bridge from High-Level Forecast to Tactical Plan? RPM: Framework for Answering Questions – Define Standards for Allocation of Resources – Facilitate Project Specification, Prioritization and Scheduling – Maintain Visibility to Resource Allocation and Assignment 8

54.
Major Change brings Major Bumps Challenge: Multiple, Large, Concurrent Projects • Six major projects in 2011; go-lives 10/1, 11/1, 12/1, 1/1, 2/1 • Functional resources (operations, finance, etc.) not in the forecast, but often the constraint Challenge: Large Influx of New Users • Internally developed system; documentation is good, not great • Rules of Golf represent some fundamental philosophy changes 54

61.
MixWhat is the `best mix? Admin (25%) “RTB” (25%) “Maint” (25%) Projects (25%) “Maint” Admin (20%) “RTB” (30%) Projects (40%) (10%) “Maint” Projects Admin (30%) “RTB” (50%) (10%) (10%) Next Steps - Define Standards for Allocation of Resources How much time on Admin? Department standards / expectations What tasks, what % of time for “RTB”? Which systems, resources, time commitment for “Maintenance”? How much time / resources on the prioritized list of Projects? 62

62.
Symphony 2008 Objectives Problem: We [still] prioritize and schedule more work than we can get done! Cause / Effect: – Stuff takes a long time to finish – Stuff takes a long time to get started – Outside factors stop progress; restarts are painful – 1 / 2 / 3 / 99 … difficult / inconsistent / squishy – Stopping something that is already started is almost unheard of Result: – Angst about overscheduling … – Frustration over Constrained Resources – Frustration over Lack of Control of My Schedule – ... and we avoid the "most difficult" conversations with business units that want this stuff we avoid the "No"s