INFO 380 Information Systems Analysis and Management

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

2. Agenda: Session 3 • Announcements • Project Document • Overview of Systems Analysis/Development • Communicating with Client • Project Teams

3. Announcements • Homework topic this week is on you! • What topic did you find new or interesting? • Go beyond basic definitions; why should I care? • Impress me in 500 - 650 words(remember to cite sources!) • Office Hours • I am available if people have questions\concerns

4. Announcements • Washington Technology Industry Association • Improve employment opportunities • Seminars & training • Social networking events • Student membership is $95/year • http://www.washingtontechnology.org/

5. Systems Analysis Team Project • Review Document • Milestones will help keep project on task • Incremental deliverables will go in proposal • Who does not have a sponsor? • Who might have several potential sponsors?

6. What are the two key words this quarter?

7. What are the two key words this quarter? Communication Value

8. What are the goals of Systems Analysis?

9. What are the goals of Systems Analysis? Deliver on promises: • Features • Value defined by client • Timeframe • ‘On time’ • Money • On/under budget • Up-front expense • On-going maintenance

10. How do we improve our odds of success?

11. How do we improve our odds of success? • Repeatable process

12. How do we improve our odds of success? • Repeatable process • Measure effectiveness

13. How do we improve our odds of success? • Repeatable process • Measure effectiveness • Document what worked

14. How do we improve our odds of success? • Repeatable process • Measure effectiveness • Document what worked • Learn from our mistakes

15. What is a process called that does these?

16. What is a process called that does these? Methodology: an organizing system; methods or organizing principles underlying a particular art, science, or other area of study

17. Information Systems Development • Why do we need a methodology • Is there just one?

18. Information Systems Development • How to choose an appropriate methodology? • Industry • Experience • Business culture • Expense and risk of project

19. Design Implementation Evaluation Feedback Loop System Development Process Analysis

20. Why have a standard process?

21. Why have a standard process? • Standard processes increases the probability of having a successful project: • Project completes on time • Project completes at/under estimated cost • Functional featuresthat work (customer satisfaction)

22. Why have a standard process? • Efficiencies are gained and quality improves • consistent process allows for clarity of status • better visibility of ‘where we are’ • better ability to adjust efforts & resources as needed

23. Why have a standard process? • Efficiencies are gained and quality improves • consistent process allows for learning • What went well? What did not? • documentation reduces costs • New people get up to speed quicker • Knowledge is shared versus hoarded

24. What makes a standard process?

25. Principles of System Development • Get the system users involved • Use a problem-solving approach • Establish phases and activities • Document through development • Establish standards • Manage the process and projects • Justify systems as capital investments • Don’t be afraid to cancel or revise scope • Divide and conquer • Design systems for growth and change

26. Principles of System Development • TEST QUESTION!!

27. Thoughts/Questions?

28. System Analysts • General Definition • Study problems and needs of organization to determine how people, data, processes and information technology can best accomplish improvements for the business.

29. System Analysts • Specialists • A programmer/analyst (or analyst/programmer) includes the responsibilities of both the computer programmer and the systems analyst. • A business analyst focuses on only the non-technical aspects of systems analysis and design. • A user analystfocuses on the experience users have with the systems and processes

30. System Analysts • Problem Solvers • Anticipates issues that require corrective action • Recognizes opportunities to improve a situation • often in absence of complaints

31. System Analysts • Most departments have analysts • Financial Management • Human Resources • Operations • Research and Development • Information Services

32. System Analysts • Skills of successful Analysts • Working knowledge of information technology • General business knowledge • General problem-solving skills • Good interpersonal communication skills • Character and ethics

33. The Systems Analyst as a Facilitator

34. Thoughts/Questions?

35. Where Do Systems Development Projects Come From? • PIECES Framework (James Wetherbe) • Need to correct or improve: • Performance • Information • Economics (control costs or increase profits) • Control (security) • Efficiency (people and processes) • Service (customers, suppliers, partners, employees)

36. Where Do Systems Development Projects Come From? • Problem – an undesirable situation that prevents the organization from fully achieving its purpose, goals, and/or objectives • Opportunity – chance to improve the organization even in the absence of an identified problem • Directive - requirement imposed by management, government, or some external influence

37. We have a ‘problem’… • Now what?

38. Gathering Data • Analyst as Witness and Instrument • Assemble data in a politically agnostic view • Cross-verify interview information • Document and validate processes • Amazing what you can observe just from watching

39. Gathering Data • The Key Tasks • Picking the places to study • Getting in to the right places • Immersing into the process • Getting along with the people you study • Building the data log assembling notes

40. Focusing Data • Remember why you are there! • Whose agent are you? • If you become one of them, you can’t help them • Remain politically agnostic (allegiance to data)

41. Focusing Data • The Tasks: • Asking questions about the topics • Creating a formal understanding with the audience • Clarity arouses interest

42. Analyzing Data • Results: • Analysis emerges from the interaction of data • Stay faithful to the facts • Keep an eye on the big-picture • What is the impact going to be in fixing problem? • People • Process • Economics • Competitiveness

43. Stakeholders • A stakeholder is any person who has an interest in an existing or proposed information system. Stakeholders can be technical or nontechnical workers. They may also include both internal and external workers. • Information workers are those workers whose jobs involve the creation, collection, processing, distribution, and use of information. • Knowledge workers are a subset of information workers whose responsibilities are based on a specialized body of knowledge.

44. Thoughts/Questions?

45. Project Teams • Finalize possible projects: 15 minutes • SCRUM meeting at end of class • Prioritize potential opportunities • Task List RACI • Thursday: • Milestone: Client Selection

46. Communicating with Client • Create an Agenda • Outlines next 8 weeks • Milestones • Deliverables • Frequency and method of communication • Batch questions!!

47. Where We Are Heading • Proposal • Table of Contents • Executive Summary • Introduction • Client Overview • Problem Statement • Methodology • Analysis and Findings • Opportunities • Proposal • Recommendations and Conclusions • Appendix (exhibits) Presentation