New training curriculum course 1


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • - we may need to assess whether logging who has taken the training is of value
  • Administraoter = govern the portfolio (governs what data goes in and out)
  • New training curriculum course 1

    1. 1. Demand Clearing - Training Curriculum<br />Demand Clearing Team<br />Course 1<br />September2011<br />
    2. 2. Course 1: Module 1<br />Course Definitions<br />Course 1 – A high level introduction and overview of the various facets of the Demand Clearing process<br /><ul><li>Audience: Directors/Managers, PMO, and anyone new to DC</li></ul>Course 2 – A detailed understanding of the operational aspects of Demand Clearing<br /><ul><li>Audience: PMs/SMEs, Technical Leads and Architects</li></ul>Course 3 – Further details on other subsidiary processes<br /><ul><li>Audience: PMs/SMEs, Technical Leads, and Architects</li></li></ul><li>Course 1: Module 1<br />Training Curriculum<br /><ul><li>Introduction to Demand Clearing
    3. 3. Demand Clearing Process Overview
    4. 4. Dependent Processes – How do they tie to DC?
    5. 5. Roadmap Planning
    6. 6. Infrastructure Allocation
    7. 7. Funding
    8. 8. Demand Capture Phase
    9. 9. Provisioning Spec
    10. 10. Standard vs Non Standard Services
    11. 11. Estimation Phase
    12. 12. Cost Breakdown of a Bundle
    13. 13. Commit Phase
    14. 14. Post Commit Phase
    15. 15. Evolution of a bundle
    16. 16. Workflow Approvals
    17. 17. Escalation Process
    18. 18. Change Request Process
    19. 19. PROPEL Training
    20. 20. CREI Process
    21. 21. Net Zero Process
    22. 22. NDCS Service Costing Model for Client Funding
    23. 23. Standard Technologies</li></ul>Course 3<br />Course 2<br />Course 1<br />Infrastructure Allocation/Funding<br />
    24. 24. Course 1: Module 1<br /> Introduction to Demand Clearing<br /><ul><li>Process that matches supply of, and demand for, constrained IT Shared Infrastructure
    25. 25. Drives increased predictability and visibility of IT requests
    26. 26. Shared Resources include people (skills) and material resources (physical and logical things)
    27. 27. Shared Resources assigned across multiple IT organizations</li></li></ul><li>Course 1: Module 1<br /> What problem is Demand Clearing tryingto manage?<br />Connecting Demand and Supply<br />Demand is greater than Supply<br />No clear accountability<br />Limited to nopredictability<br />Limited to no visibility<br />
    28. 28. Course 1: Module 1<br />Project / Program matures and evolves<br />SharedResourcesDemand<br />Business Changes<br />Timeline Changes<br />Trade-off Between Initiatives and Operations<br /> What problem is Demand Clearing<br /> trying to manage?<br />Shared Resources<br />Raw Demand<br />Quarterly Releases<br />DBAs<br />JVM<br />Projects<br />Storage<br />Strategic Programs<br />Communication Gap<br />Bug Fixes<br />Architects<br />Fleet Refresh<br />Etc.<br />Shared Resources Demandis constantly changing.<br />Demand Teams utilize different processes and do not speak the same language as Shared Resources.<br />
    29. 29. Course 1: Module 1<br /> Why Do We Have Demand Clearing<br /><ul><li>Reduce time delays
    30. 30. Single point of contact
    31. 31. Fewer iterations
    32. 32. Track accountability among teams</li></ul>Fix this slide<br />
    33. 33. Course 1: Module 2<br />Demand Clearing – Current Process<br />Demand Clearing Scope<br />Handled directly between GBP and Infra teams<br />Commit Notification<br />Resource Names, <br />Delivery Dates<br />DC Prov Spec<br />Execution Work Plan, CtB/RtB Cost<br />Output<br />Post Commit<br />Hand-off <br />Demand Capture<br />SRM Commit<br />Estimation<br />Process<br />Execution<br /><ul><li> Clarify requirements as needed
    34. 34. Share Self Fund Cost Information with DE team.
    35. 35. Push bundles for commit.
    36. 36. Create and submit estimates (WP, SP, PDB)
    37. 37. Approve estimates.
    38. 38. Confirm Funding Info.
    39. 39. Approve commit dates.
    40. 40. Attend Re-Commit mtgs.
    41. 41. Secure Infra Commits
    42. 42. Share Infra Commit Info.
    43. 43. Setup Commit Review and Re-Commit mtgs
    44. 44. Share commit Info. (Resource name, delivery date)
    45. 45. Share revised commit info.
    46. 46. Attend Commit Review mtgs.
    47. 47. Submit demand via DC spec.
    48. 48. Submit Updates to Spec.
    49. 49. Attend Discovery / Triage mtgs.
    50. 50. Validate spec.
    51. 51. Create bundles.
    52. 52. Schedule Discovery /Triage mtgs.
    53. 53. Submit bundles to estimation.
    54. 54. Review spec.
    55. 55. Attend Discovery / Triage mtgs.
    56. 56. Coordinate with Infra on Execution.
    57. 57. No Action</li></ul>(Demand Clearing engagement officially ends at Post Commit Hand-off)<br /><ul><li> Coordinate with DE team on Execution
    58. 58. Delivery of Infra.
    59. 59. Execution Planning.
    60. 60. Share Formal Commit Notification. (Resource name, delivery date, work plan and BOM)
    61. 61. End DC engagement, move to Execution
    62. 62. Execution Planning.
    63. 63. Secure the Transfer of Funds from DE Team.</li></ul>Project Team<br />DC Team<br />Supply Team<br />
    64. 64. Course 1: Module 3<br />Engaging Demand Clearing<br />Time <br />Specification<br />Confidence<br /><ul><li>ASAP
    65. 65. Capacity planning
    66. 66. Avoid “demand collisions”
    67. 67. Engage individual teams
    68. 68. Account for supply team cost
    69. 69. Specify your requirements
    70. 70. Architecture Process
    71. 71. Be responsive</li></ul>Stephen Estes (sestes)<br />Allocate<br />Commit<br />Assign<br />
    72. 72. Course 1: Module 3<br />Service Level Agreements (SLAs)<br /><ul><li>Fast Track Services –Readily understood services in terms of end deliverables, resource requirements, cost, and SLAs; usually basic in nature (simple database schemas, basic storage, JVMs, etc.)
    73. 73. Non Fast Track Services – Services for which resource requirements and costs are not clear upfront </li></li></ul><li>Course 1: Module 3<br /> Associated Programs, Processes, & Tools<br /><ul><li>PROPEL
    74. 74. Cisco Docs
    75. 75. Architecture Process
    76. 76. Global Data Center Program
    77. 77. Aspirin Process
    78. 78. DC Escalation Process
    79. 79. Database Tools
    80. 80. Remedy 7</li></li></ul><li>Course 1: Module 3<br />Demand Clearing Pre-Reqs<br /><ul><li> A valid PROPEL project record
    81. 81. Completed Demand Clearing Provisioning Spec OR Standard Services Questionnaire
    82. 82. Engagement with your platform’s Partner Architecture Team – Enterprise Architecture Representative (PAT EAR)</li></li></ul><li>Course 1: Module 4<br />Roadmap Planning<br /><ul><li>Importance of Roadmap Planning: Why Do You Need To Forecast?
    83. 83. To provide Supply Entities with adequate lead time for approval
    84. 84. GBP clients should verify Non-Core needs with ERMO
    85. 85. Engage with DC as early in release cycle as possible
    86. 86. DC Exception/Escalation procedure</li></li></ul><li>Benefits of Prepaid Funding<br />Faster passage through Demand Clearing process<br />Budget stability and predictability<br />Includes CtB and RtB* costs – no budget surprises later <br />No on-boarding cost of resources<br />Improves resource availability and commit time<br />Demand and Supply collaborate to plan prepaid funding <br />Ability to reallocate and serve urgent requests<br />Improved visibility into CtB/RtB* cost and utilization of resources<br />Retain ‘Cisco trained’ human resources, increasing productivity and quality<br />* RtB costs are currently under discussion<br />Course 1: Module 5<br />
    87. 87. Quarterly Prepaid Process<br />Course 1: Module 5<br />Annual Prepaid<br />Planning<br />Historical Costs (CtB/RtB)<br />Projected Pipeline<br />Current Pipeline from Propel<br />GBP PMOs, PMs, <br />POCs<br />Starts at least 4 weeks before <br />Start of next quarter<br />U[dated Infra Costing Calculator<br />Prepaid Reconciliation Report<br />
    88. 88. Annual Funding Process<br />Course 1: Module 5<br />Pass 2, 3<br />Pass 1<br />Planning Guidance from Finance<br />FY Review<br />Pass 1<br />FY Review<br />Pass 2,3<br />Annual <br />Budget <br />Plan<br />CoS Planning Team <br />Determine data & level of detail<br />Consolidate, generate reports<br />Consolidate, generate reports<br />Cost elements into Apptio<br />IT Planning Mgrs, PMOs, PMs<br />PMOs/PMs document FY priorities<br />Refine priorities & update costs<br />Infra Costing Calculator<br />Summarize Infra Costs<br />DC<br />DC summarize infra Costs<br />
    89. 89. Quarterly Prepaid Activities Timeline<br />Course 1: Module 5<br />Week 6<br />Weeks 7-8<br />Weeks 9-10<br />Weeks 11-13<br />Mid Quarter Reconciliation<br />GBP and SE FAs complete funding transactions<br />GBPs prepare for next Quarterly Portfolio Review<br />Data Sources:<br /><ul><li> Planned Projects
    90. 90. Propel data
    91. 91. Reconciliation Report
    92. 92. Infra Costing Calculator
    93. 93. Outcome: Estimated prepay</li></ul>Portfolio Reviews for coming quarter<br />Data Sources:<br /><ul><li> Planned Projects
    94. 94. Propel data
    95. 95. Reconciliation Report
    96. 96. Infra Costing Calculator
    97. 97. Outcome: Prepaid Agreements</li></li></ul><li>Course 1: Module 5<br />Prepaid Demand Clearing Process<br />Demand Clearing Process<br />Estimation<br />Execution<br />Performance<br />Supply Commit<br />Demand Capture<br /> Triage/Discovery<br />Yes<br />Delivery Commit<br />Supply provides CtB/RtB<br />Estimate<br />Supply confirms Prepaid funds avail<br />?<br />All projects enter as prepaid<br />Supply Debits<br />GBP<br /> Prepaid<br />Client Requirements<br />No<br />No<br /><ul><li>Defer project
    98. 98. Revise scope
    99. 99. Reprioritize pipeline
    100. 100. Adjust prepaid funding</li></ul>GBP agrees to Pay-as-you –go<br />funding<br />Delivery Commit<br />Note: This represents a non Fast Track Request. Funding for Fast Track will be confirm at the time of entry into Demand Clearing.<br />
    101. 101. Reconciliation Report<br />Provides Quarterly View for each Functional Organization<br />What was funded<br />How much has been spent to date<br />Break out by CtB,RtB and Supply (ATS/NDCS/ITAS)<br />Used operationally to manage prepaid project commit<br />Used by Demand Clearing Governance and OC to manage Prepaid adoption<br />Project/Bundle level reporting near future<br />On Demand Availability near future<br />Course 1: Module 5<br />
    102. 102. Primarily provide human resources<br />Pay by PR only<br />Pay prior to start of quarter<br />Additional payments, whether prepaid or pay-as-you-go, are not accepted after week 8 of quarter<br />Primarily cost recovery for staff in place<br />Pay by cross-charge<br />Pay in Month 1 of quarter<br />Cost recovery on a service level<br />Capital and human resources<br />Pay by cross-charge<br />Pay at end of quarter<br />Current<br />ATS Prepaid<br />Current<br />ITAS Prepaid<br />Current<br />NDCS Prepaid<br />Course 1: Module 5<br />This represents the current state as reviewed in the cross-functional team discussions. Work is in progress to standardize this process across Supply and Demand entities.<br />