1. After class… Reach out to your GP1 group Setup time to meet Get started on GP1 asap!

2. Mark you calendars Client Project Kickoff Monday, Feb 15 th at 6:30pm Follows Client Bid Day (Feb 12 th ) Bruce and I will serve pizza and you can meet your client. Not required but strongly encouraged some or all of team comes

3. MIS 374 - Day 3 Outline 1.Group Project 1 Overview & team meeting 2.Root Cause Analysis Figuring out the underlying problem & objectives for a solution Reminder: Exercise 4 due before next class.

4. Final Construction Inception Early tasks 1.Stakeholder table 2.Sw & Hw Environments table 3.Root Cause Analysis 4.Context Diagram 5.Data Flow Diagrams GP1 Deliveries – Focus on the “As Is” situation Last class HW & this class Before & During next class In 333K

5. Group Project 1 Process  Stakeholders, Roles, and Responsibilities Table  Software & Hardware Environments Table  Root Cause Analysis Suggested order Use a highlighter and jot notes while you read the case.

6. Group Project 1 DFD Process  Media Marketing Context Diagram  Media Marketing Process Create a rough draft of each of these when you read the case. Create your summary DFDs (the Figure 0 and final Context Diagram) last.

7. Work Place MIS 374 Project 1 1.Download and print the case. 2.Read the RFP (request for proposal) and review any documents provided by your supervisor or client. 2.Read the case and project specifications. 1.Your supervisor assigns a project.

8. Work Place MIS 374 Project 1 3.You arrange interviews and meetings with appropriate users, SMEs, and tech experts to learn more about symptoms, problems, objectives, constraints, and details about all the stakeholders, data, information, software, and hardware environment. 4.You conduct the interviews and meetings. 3.Just read the case for details. 4.Just use the case.

9. Work Place MIS 374 Project 1 5.You create drafts & notes. 6.You work with your team and stakeholders to arrive at a clear definition of the project. 5.Same: You create drafts & notes as an individual. 6.You work with your team to complete the specifications.

10. Group Project 1– Meeting at end → We’d give you 5 minutes at the end of class to set next meeting → Reminder: Exercise 4 due at the beginning of the next class.

11. MIS 374 - Day 3 Outline 1.Group Project 1 Overview & team meeting 2.Root Cause Analysis Figuring out the underlying problem & objectives for a solution Reminder: Exercise 4 due at the beginning of next

12. Where are we in the SDLC? Final Construction Inception NOTE: We’ll be focusing here a while in class because upfront part of project is critical for success!

13. Root Cause Analysis A series of symptoms, one causing the next, can lead to the root cause. Why do we do this? To come to an early agreement on the scope of the project but…it’s important that it’s the right scope! Also we don’t want to jump to solutions or else we may not solve the REAL problem

14. Digging Down Through Layers of Symptoms Declining profits Total expenses up Travel expenses up Sales Territory Assignment Symptom 1 Symptom 2 Symptom 3 Symptom 4 or Problem or root cause? Why? Root Cause Analysis

15. See reading for ASTA example

16. ASTA  Symptoms can be user-oriented or process-related  “Points of pain” sometimes but doesn’t have to be a negative symptom

17. Solution/Definition for Root Cause Symptom(s) Cause(s) Solutions Objective(s) Performance criteria System Definition effort External constraints Internal constraints Solution effort Group Project #1

18. For each objective have at least 1 performance criteria that we can measure ASTA

19. Through a standard methodology, we have a consistent approach to address any company’s issue Use a standard process © 2015. For information, contact Deloitte Touche Tohmatsu19 1.Confirm the issues faced by company 2.Develop business processes and perform analysis 3.Determine scope of project/issue that the project team will address 4.Identify any key design assumptions and then gather and prioritize business requirements 5.Design final solution Identify Symptom(s) Identify Problem(s) Objective(s) Performance criteria Deloitte ActivityMIS374 Activity Constraints Develop a Problem Chain Develop Final Solution

20. Example: Root-Cause Analysis Background: Global multi-billion dollar manufacturer looking to implement a global ERP system 20 © 2015. For information, contact Deloitte Touche Tohmatsu Symptoms Problems Objectives Performance Criteria Constraints Multiple countries perform the same processes differently Inconsistent customer experiences depending on the country Orders are managed differently in each country With different supporting systems, each country has a different standard and process to handle customer orders To implement a global system To design global processes to ensure consistent customer experiences Manual orders can be entered within 5 mins Online orders must be processed within 24 hrs from submission Customer questions must be acknowledged within 24 hrs from submission The largest part of the business needs to be up and running within 1 year and the rest of the globe within 2 years. There must be a clear change management plan so all of the countries understand what is expected

21. Thought Exercise

22. Email from project manager Thought exercise © 2015. For information, contact Deloitte Touche Tohmatsu22

23. Background: Global multi-billion dollar manufacturing/ distribution company has implemented an Accounts Receivable system Thought exercise: answer 23© 2015. For information, contact Deloitte Touche Tohmatsu Symptoms Problems Objectives Performance Criteria Constraints One of the countries deployed feels the new system is cumbersome The in-country team did not understand the training that was provided There has been a very large increase in unapplied dollars which has never happened before The users didn’t understand that they couldn’t manually change exchange rates in the system since the previous system allowed this To implement and enforce the new global process To determine what needs to be done with the dollars now unapplied System should provide a warning when someone tries to manipulate exchange rates Training must be provided in multiple languages and test understanding of exchange rates System should provide a warning when unapplied dollars meets a specific threshold Training courses need to held with the users within the next 2 months The correct accounting treatment for all of the dollars not accounted for must be determined before the next month end close