Technology Management for Small Business2. What is Technology Management? A technology manager is any person controlling work to assure operation of the organization's information technology and computer systems. In small organizations, someone may be responsible for technology as well as many other functions. Often the ‘operations manager’ or ‘business manager’ is also responsible for technology. Small businesses may depend on external vendors for technology services because they are too small to warrant an internal IT department. Therefore good vendor management is imperative for the small business. Technology managers should understand their own contributions in context of overall business responsibilities. 10/11/2010 ALL CONTENTS ©COPYRIGHT 2009 MMT CONSULTING, LLC. except where referenced 2 3. Why does small business need Technology Management? “The company is definitely set up in a way where myself and the other founders have a lot of control over it.” Mark Zuckerberg, founder, Facebook, March 2010 “If at first you don't succeed, try once more. Then do something else.” Peter Drucker, “father” of modern management “Smaller projects [and businesses] have less resources to devote to controls and governance yet the risks of failure are the same. “ Lance McClain, Quality Services Manager, PepsiCo, October 2010 Take control of what you have…it might get really big You only have one or two shots to succeed Take care of your precious resources and watch your risks ALL CONTENTS ©COPYRIGHT 2009 MMT CONSULTING, LLC. except where referenced 10/11/2010 3 4. Why do technology projects (even small ones) fail? Yuck That happens in small business too! “92% of large scale IT projects fail” CIO.com “Five Principles for Reducing IT Failure” Need to: Communicate Consolidate Prioritize Requirements Manage Time 82% of employees within companies with significant organization wide projects under way believe those projects will fail; 78% believe they are working on a “doomed” project; 90% knew early on that the project would likely fall short of the objectives; 81% believe it is impossible to approach the failing project’s key decision-maker CapTech Blogs “Key Reasons for Project Failure” Reasons: Poor Planning Poorly Defined / Missed Requirements Poor User Involvement Poor Change Management / Communication These are management issues Ick Wow – does my team feel that way too? These are management issues ALL CONTENTS ©COPYRIGHT 2009 MMT CONSULTING, LLC. except where referenced 10/11/2010 4 5. 10/11/2010 Practical Project Management(this is a way of working for all of us) every day management Process Groups: * Initiating Planning Executing Monitoring and Controlling Closing Knowledge Areas: * Integration Scope Time Cost Quality Human Resources Communication Risk Procurement #1 Earn the Trust of OthersRelationships, spirit, people, communication, and creating value#2 Balance the Three-Legged StoolTime, cost, quality - the delicate balance#3 Know the DifferenceRisks, Issues, Actions#4 Get the Right StuffRequirements & Decisions, Equipment and staffing acquisition, Procurement#5 Don’t Work in a VacuumIntegration, dependencies, scope and when to stop Some Structure helps A little structure doesn’t hurt * Project Management Institute PMBOK ALL CONTENTS ©COPYRIGHT 2009 MMT CONSULTING, LLC. except where referenced 5 6. Solution Leadership(align IT to business) common language for the entire team A Solution Process is the framework to create a common language for the entire team. “Good enough practice” for governance and service management *can be right sized for small business. The Enterprise Architecture aligns technology areas. Business process Data Applications Technology Business Domain Areas define functional opportunities and priorities. For example, Executive, Business Intelligence, Public Relations Business Development, Commercial Team, Customers Operations Administrative Integrations, dependencies opportunities, priorities * Refer to COBIT and ITIL best practice ALL CONTENTS ©COPYRIGHT 2009 MMT CONSULTING, LLC. except where referenced 10/11/2010 6 7. Vendor Management(critical for small business) select based on weighted criteria Vendor Selection Scorecard: Compare alternatives using a weighted scorecard. In a spreadsheet, list features down the left with the importance of each, alternatives across the top with a rating of how they satisfy each feature. Importance X Rating = Score. Make sure one of the alternatives is to "do nothing". Hold vendors to a service level agreement (SLA) Service Management is the service delivery and support as visible by IT customers. Service management provides integrity and reliability of computer systems, incident/problem management, support and training, and user-provisioned equipment. The value of IT is often judged by service management quality. Are service level agreements (SLAs) in place with your vendors? How are they being managed and monitored? What end-user services are being provided? Are these service keeping up with demand and technology trends? What is the response time and integrity of application and reporting systems? Are people able to do their jobs without "waiting on the computer"? What type of performance monitoring and predictive tools are in place so you can react to and plan for future needs? What control processes and communication plans are in place to make sure changes to systems provide security and business continuity? How are problems and incidents handled? What performance measurements and SLAs are in place for resolution? What does the IT infrastructure look like (e.g., data centers, service providers, cloud computing, network, operating systems, programming language standards, software licensing, hardware leasing/purchases). Is the infrastructure keeping up with demand and technology trends? Are you able to provide business continuity in the event of a disaster or outage? ALL CONTENTS ©COPYRIGHT 2009 MMT CONSULTING, LLC. except where referenced 10/11/2010 7 8. Impacts and Stabilization(Communicate, Train, Reinforce) Balance impact of change with readiness Change Management Plan* - a roadmap that leads to desired results Triggers for change Impacts on organizations & individuals “what’s in it for me?” (WIIFM) Resistance Communication Training Reinforcement Change is usually met with resistance - Be prepared * Refer to PROSCI ALL CONTENTS ©COPYRIGHT 2009 MMT CONSULTING, LLC. except where referenced 10/11/2010 8 9. References Project Management PM Institute (www.pmi.org) IT Governance: COBIT Framework for IT Governance and Control (www.ISACA.org) IT Service Management ITIL (www.itil-officialsite.com) Change Management PROSCI (www.prosci.com) Enterprise Architecture The Open Group Architecture Framework (TOGAF) (www.opengroup.org/togaf) ALL CONTENTS ©COPYRIGHT 2009 MMT CONSULTING, LLC. except where referenced 10/11/2010 9 10. Reading List(all available at amazon.com) The Essential Drucker: The Best of Sixty Years of Peter Drucker's Essential Writings on Management (Collins Business Essentials) by Peter F. Drucker Cobit 4.1 by IT Governance Institute A Guide to the Project Management Body of Knowledge, Third Edition (PMBOK Guides) by Project Management Institute ADKAR: a Model for Change in Business, Government and our Community : How to Implement Successful Change in our Personal Lives and Professional Careers by Jeff Hiatt Togaf Version 9 - A Manual (TOGAF Series) by The Open Group ITIL V3 Foundation Handbook - Pocketbook from the Official Publisher of ITIL ALL CONTENTS ©COPYRIGHT 2009 MMT CONSULTING, LLC. except where referenced 10/11/2010 10 11. Presenter Info Margaret Thomas is a technology management consultant providing expertise in technology management, software development leadership, business process design, and change management. Ms. Thomas is the author of four blogs available at www.margaretmarythomas.com: 360.CIO Innovative Process Change Technology Solution Leadership The Practical Project Manager Margaret loves to ski, bike, swim, run, and hike. She lives in Edwards, CO and Denver, CO with her husband, Greg margaretmarythomas@yahoo.com 303.324.9278 ALL CONTENTS ©COPYRIGHT 2009 MMT CONSULTING, LLC. except where referenced 10/11/2010 11