INFO 380 Information Systems Analysis and Management

1. INFO 380Information Systems Analysis and Management Instructor: Greg Hay TA: Yuan Lin

2. Agenda: Session 13 • Announcements • Capability Maturity Model • Information Technology Infrastructure Library • Microsoft Frameworks • Microsoft Solutions Framework (MSF) • Microsoft Operations Framework (MOF)

3. Announcements • Feasibility Study: Due THURSDAY • TOES • Net Present Value • Payback Analysis • Return on Investment • Feasibility Analysis Matrix • Previous lecture • Chapter 10 of text

4. Announcements • Scheduling Team Project Presentations • March 7 - 10 • 4 or 5 presentations each day • 12 minutes each • Open positions: • Monday: 12:45 | 1:15 | 1:45 | 2:15 • Tuesday: 2:45 | 3:30 • Wednesday: 12:45 | 1:15 | 1:45 | 2:15 • Thursday: 2:30 | 2:45 | 3:15 | 3:30

5. Announcements • Guest Speaker Tomorrow • Virgil Bourassa Microsoft Corp. • “Invent vs. Buy” • Mary Gates Hall #420 • 1:30 PM • Extra-Credit involved

6. Questions?

7. Many standardized processes • Systems Development Lifecycle • Capability Maturity Model • ITIL • Microsoft • Many others…why?

8. Capability Maturity Model (CMM) • Standardized Framework for IT organizations • Why was CMMcreated?

9. Capability Maturity Model (CMM) • Standardized Framework for IT organizations • How did some organizations continuously have successful IT projects while others failed? • ‘Project timelines and cost decrease while productivity and quality increase’

10. Capability Maturity Model (CMM) • Created for Department of Defense • Method to evaluate potential defense contractors • Who had the capability to deliver successful project?

11. Capability Maturity Model (CMM) • Recognizes that successful IT projects followed certain characteristics • Not by ‘accident’ certain groups are successful • Does not depend on technical skills or technology

12. Capability Maturity Model (CMM) • Gained recognition as solid tool for assessing many business processes (not just IT) • What does CMM look like?

13. Capability Maturity Model (CMM) • Qualifies organizational maturity into 5 levels • Initial • Repeatable • Defined • Managed • Optimizing

14. Capability Maturity Model (CMM) • Level 1: Initial (a.k.a. ‘chaos’) • Characteristics • Development projects have no consistent process • Documentation is inconsistent • Little evaluation of mistakes; limited learning • All organizations start here

15. Capability Maturity Model (CMM) • Level 2: Repeatable • Characteristics • Project management processes established • Project costs, schedules and functionality tracked • Focus on project management • Processes followed but may vary between projects

16. Capability Maturity Model (CMM) • Level 3: Defined • Characteristics • Standard system development process created • All projects follow consistent process • High-quality documentation and deliverables • Process is stable and repeatable

17. Capability Maturity Model (CMM) • Level 4: Managed • Characteristics • Goals established for quality and productivity • Process measurements captured, stored and reviewed • Attempts to become proactive

18. Capability Maturity Model (CMM) • Level 5: Optimizing • Characteristics • Standard development processes monitored • Knowledge widely shared Continuous Process Improvement eradicates inefficiency

19. Capability Maturity Model (CMM) • Why do we need to be aware of CMM?

20. Capability Maturity Model (CMM) • What maturity level are most organizations? • Level 1: Initial (a.k.a. ‘chaos’) • Level 2: Repeatable • Level 3: Defined • Level 4: Managed • Level 5: Optimizing

21. Questions?

22. IT Infrastructure Library (ITIL) • International organization based in Europe • Developed best-practices for IT services • Goal was to providemechanism to drive organizational effectiveness by increasing consistency, efficiency and predictability into the business of managing IT services

23. IT Infrastructure Library (ITIL) • IT Infrastructure is in the background • Business does not interact directly • Old days: application/technology ‘silos’ • Expensive…why?

24. IT Infrastructure Library (ITIL) • ITIL structure/philosophy • Holistic approach combines technology ‘silos’ • Efficient…why?

25. IT Infrastructure Library (ITIL) • IT as a service • Business process that ‘provides value to customers’ • Service Lifecycle • Strategy: who are customers & what do they need? • Design: technology & process architecture; metrics • Transition: build, test, deploy & validate • Operation: ongoing routine maintenance • Continual Service Improvement: KPI mechanisms

26. IT Infrastructure Library (ITIL) • IT as a service • Business process that ‘provides value to customers’ • Business processes may rely on others services • Example: Payroll relies on Time Tracking, Database Administration and Server Administration

27. IT Infrastructure Library (ITIL) • Benefits of ‘IT as a service’ approach • Why?

28. IT Infrastructure Library (ITIL) • Benefits of ‘IT as a service’ approach • Why? • Customer focused (expectations easier to meet) • Aligns IT to business needs (proactive) • Predictable, consistent/repeatable process (efficient) • Standardized (people are interchangeable) • Flexible to change (built-in to process) • Measureable/improvable processes (KPI/efficient)

29. Questions?

30. Microsoft Solutions Framework • What is the Microsoft Solutions Framework?

31. Microsoft Solutions Framework • What is the Microsoft Solutions Framework? • Solution delivery framework for creating software, deploying infrastructure solutions and consulting • Several revisions over the past 20 years • Established in 1991\made public in 1993 (version 1) • fully revised in 1998 (version 2) • January 2003 (version 3) • March 2006 (version 4)

32. Microsoft Solutions Framework • Simplified • Guidelines for developers during SDLC • Set of software engineering processes • Principles • Proven ‘best’ practices

33. Microsoft Solutions Framework • How is MSF related to Operations Framework? • MSF = ‘Build IT Right’ • emphasis is on projects • MOF = ‘Run IT Right’ • emphasis is running the production environment

34. IT Lifecycle Microsoft Solutions Framework Plan Operate Build Deploy Microsoft Operations Framework

35. Microsoft Solutions Framework • What is a ‘Framework’?

36. Microsoft Solutions Framework • What is a ‘Framework’? • Different from a methodology • Set of conceptual tools and best practices • ‘Flexible and adaptable to scale’ • MSF has both frameworks and methodologies

37. Microsoft Solutions Framework • Why would Microsoft develop a whole new set of processes, principles and best practices for software engineers?

38. Microsoft Solutions Framework • Why would Microsoft develop a whole new set of processes, principles and best practices for software engineers? • There are millions of developers out there and more than half develop for the MS platform • Creating processes increases the ability to deliver a successful project • People become interchangeable • Deliverables are clear • Communication improves

39. Microsoft Solutions Framework • Why would a Systems Analysis instructor add one more boring standard process?

40. Microsoft Solutions Framework • Why would a Systems Analysis instructor add one more boring standard process? • Being conversational on MSF\MOF might be the difference between you getting hired or not

41. Partners involved in MSF v4

42. Microsoft Solutions Framework • What are some foundation principles of MSF?

43. Microsoft Solutions Framework • What are some foundation principles of MSF? • Foster open communication • Work towards a shared vision • Empower team members • Establish clear accountability and shared responsibility

44. Microsoft Solutions Framework • What are some foundation principles of MSF? • Focus on delivering business value • Stay agile, expect change • Invest in quality • Learn from all experiences

45. Microsoft Solutions Framework • Sounds familiar, did Microsoft invent standardized software development?

46. Microsoft Solutions Framework • Sounds familiar, did Microsoft invent standardized software development? • No…but they do a great job of assembling and circulating the material • ‘Better meatloaf’

47. Microsoft Solutions Framework • Standard principles • Foster open communications • Work toward a shared vision • Empower team members • Establish clear accountability and shared responsibility • Focus on delivering business value • Stay agile, expect change • Invest in quality • Learn from all experiences

48. Microsoft Solutions Framework • Foster open communications • Why? • How does abandoning ‘need to know’ basis improve the odds of a successful project?

49. Microsoft Solutions Framework • Work toward a shared vision • Where does this need to happen?

50. Microsoft Solutions Framework • Empower team members • What does this look like? • What are the benefits? • ‘Wolves vs cows’