Cisco Executing Cisco Advanced Business Value Analysis and Design Techniques Set 1

lowest possible cost ✘ most advanced solution, both technically and for the business operation ✘ an appropriate mix of risk, technology capability, and business capability, based on customer priorities ✘ must fit within the current IT budget ✔

Support solutions that can be fully implemented with current capabilities on the IT staff. ✘ Give extra weight to projects that give the business unit responsibility for risky activities. ✘ Bring the IT and business executives together where possible to forge a unified viewpoint. ✘ Push investments out to the future, where possible, to delay larger investments. ✔

Focus mainly on near-term investments and leave discussion about rollout until after a pilot is complete. ✘ Give a comprehensive picture of the costs, benefits, and considerations that the customer should think about. ✘ Ask the IT executive to publicly commit their support for your recommendation. ✘ Be cautious when you discuss the risks that the organization should consider to gain support without raising possible challenges. ✔

They should allow for the shortest total project elapsed time, regardless of risk. ✘ They should have a good balance across a variety of business groups. ✘ The timing should be realistic, given the scope, budget, risk, and potential benefits. ✘ The duration should be set by a single executive sponsor so that accountability is easiest to determine. ✔

Ask mangers if their employees need new skills. ✘ Look at prior problem tickets. ✘ Conduct interviews with people who represent major user roles. ✘ Identify where the system is most confusing to use. ✔

the customer's go-to-market approach for generating revenue ✘ competitor prices ✘ the organizational structure ✘ the company's budget for marketing products planned for two years in the future ✔

Ask open-ended questions about the organization's priorities and goals. ✘ Ask questions about the IT organization's track record for problem resolution. ✘ Provide an overview of your sales team's reporting structure and metrics. ✘ Ask detailed questions about the process to acquire cloud computing solutions. ✔

Ask an IT stakeholder to inquire with the executive on your behalf. ✘ Brainstorm with the internal team to get feedback from peers. ✘ Ask the executive whether you could join a future staff meeting and present for 15 minutes. ✘ Offer to show the executive a demonstration of the latest security software. ✔

A higher level of politics and uncertainty typically exists with larger initiatives. ✘ The IT department most likely has a higher level of influence as compared to other projects. ✘ The stakeholder analysis 2x2 framework -- interest vs. power -- only works for small scope projects. ✘ It is necessary to assess 90% or more of the stakeholders for an effort. ✔

Discovery should be performed to a lower level of detail than for smaller projects. ✘ Planning for discovery activities may take more effort, but this step is essential. ✘ The project team should be staffed with more subcontractors to keep the costs down. ✘ Request that the customer captures a baseline of needs in advance of your work. ✔