450 likes | 614 Views
INFO 380 Information Systems Analysis and Management. Instructor: Greg Hay TA: Yuan Lin. Words of Wisdom. From an ancient Systems Analyst. Words of Wisdom. “Don’t ignore the reading” “Look for the opportunity to challenge yourself” “Know what you do not know…and fix it”.
E N D
INFO 380Information Systems Analysis and Management Instructor: Greg Hay TA: Yuan Lin
Words of Wisdom From an ancient Systems Analyst
Words of Wisdom “Don’t ignore the reading” “Look for the opportunity to challenge yourself” “Know what you do not know…and fix it”
Agenda: Session 4 • Announcements • REVIEW!! Systems Analysis process • Project Document • Communicating with Client • Project Teams
Announcements • Guest Speakers next week • Tuesday (during lecture) • KeertiRane – Microsoft • Senior PM • Wednesday (12:30 somewhere in MGH) • Ryan Marberg – IS OutSource • Senior Consultant
Announcements • Guest Speaker protocol • Effective listening…these guys are knowledgeable • They are here to share experience not to hire us! • Ask questions! • Stay in contact: follow-up with future questions • These people are busy (be patient)
Announcements • Class calendar is ‘squishy’ • Topics are fluid…movable depending on where we are • Has relative dates for milestone purposes • The drop box has firm due dates
Announcements • Client Selection is ‘scheduled’ for today • Nothing to be turned in • Intended as a benchmark for scheduling/keeping pace
Announcements • Client Description is DUE on Tuesday • Don’t need to interview anyone to get description! • Do research!! We are information professionals • Visit organization’s website as well as others • Interviews will go MUCH better if we are informed
Announcements • Project topic should NOT be known yet • We go in to customer and DISCOVER problem • Some are expecting customer to define the project?
System Analysts: REVIEW! • General Definition • Study problems and needs of organization to determine how people, data, processes and information technology can best accomplish improvements for the business.
System Analysts: REVIEW! • Specialists: bring expertise/skills to table • 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
System Analysts: REVIEW! • Problem Solvers • Anticipates issues that require corrective action • Recognizes opportunities to improve a situation often in absence of complaints
Systems Development Projects REVIEW! • 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)
Systems Development Projects REVIEW! • 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
Principles of System Development • TEST QUESTION!!
Systems Analysis Team Project • Review Document • Milestones will help keep project on task • Incremental deliverables will go in proposal
What are the two3 key words this quarter? Communication Value LISTEN
Communicating with Client • Create an Agenda • Outlines next 8 weeks • Milestones • Deliverables • Frequency and method of communication • Batch questions!!
Communicating with Client • Managing work | managing a schedule • map out what you are expected to complete • Who needs it completed? • When do they need it • NOT when is it due • What are the dependencies?
Communicating with Client • Managing work | managing a schedule • don't wait until the last minute and expect help • I am the king of last minute deliverables • Be prepared! • more critical than school
Communicating with Client • Managing work: Why? • legacy and reputation are less forgiving than your credit score
Communicating with Client • Setting an agenda • bigger the project the bigger the risk • bigger the risk the more-detailed the agenda
Communicating with Client • Setting an agenda • Clear organization • most-often sequential • Make dependencies obvious • Duration • Due Dates • Cross outwhen completed • do not erase
Communicating with Client • Setting an agenda…Why? • People want to be organized • ‘Organize or Die’ • Not everyone knows how or is effective at it • Simplifies efforts for everyone
Communicating with Client • Managing expectations • under-promise and over-deliver • Immediate communication when things change • even when it just 'looks like' they might change
Communicating with Client • Managing expectations…Why? • No one likes surprises • people have lives • Hell hath no fury like a customer burned
Communicating with Client • Excellent Customer Service • Respect your customers • No matter how much it hurts • Find opportunities to make things easier
Communicating with Client • Excellent Customer Service • Enforce policies politely • Still have to do our job • When having to push back • explain why • look for alternatives • Be consistent
Communicating with Client • Excellent Customer Service • Be approachable and available • Reply to emails quickly! • Ask for feedback • Corrective action much easier early • Promotes professional attitude
Communicating with Client • Excellent Customer Service…Why? • These are the people who talk loudest • will cheer you or boo you
Communicating with Client • ‘Managing –Up’ • Clear communication always with manager • do not blind-side your manager with your crises • They will protect you if given warning • They need you
Communicating with Client • ‘Slamming’ deliverables • Finish the job • No short-cuts! • put the vacuum away • Always end a 'project' clearly\definitively • Even if only 5 minutes • Email is best
Stories first… • 1) Briefcase • 2) Spokane • 3) Portland • 4) Microsoft (Bldg 11)
Info gathering What are our goals? What are our tools?
Project Teams • Finalize possible projects: 15 minutes • SCRUM meeting at end of class • Prioritize potential opportunities • Task List RACI • TODAY: • Milestone: Client Selection • TUESDAY: • Due: Client Description • ~ 2 pages
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