1. “Good judgment comes from experience, and often experience comes from bad judgment.”

2. Return to Latinitas – DAY 1

3. How can Latinitas team ensure success?

4. What impressed me is NOT that you caught important requirements like security, automation. These are just features. It’s how manage clients, scope, time, risk, org impact, non-functional requirements, change... Important things to note: o 90% of conflict on projects are due to poor comm. o 80% of failed projects site lack of acceptance to change

5. MIS 374 – Day 2 Outline 1.Latinitas revisited: more of the story 2.The SDLC 1.Stakeholders & Communication 1.Next class reminders 2.Exercise #2 – in-class: Stakeholders Table for Latinitas

6. Latinas Revisited: A “Database Project” Became a “CRM Project” The Fantastic Five (Spring 2007) Tracy Ma, Flowserve, Dallas Zakria Malik, Hewlett-Packard, Austin Robin Moore, Simpler-Webb Inc., Austin Gretel Paronzinni-Fredette, Deloitte, Austin Aaron Thompson, KPMG, Dallas The team’s slides are linked to Schedule, Day 2.

7. Latinitas

8. Latinitas Donation System – As Is Volunteers contact donors to request donations for a particular event based on previous history and keep records on various forms – by hand, spreadsheets, etc. Management reports on donors for events are not easily accessible. Volunteers record donations on various forms and send Thank-you letters to donors. Donors Information

9. Latinitas Donation System – Proposed Volunteers contact donors to request donations for a particular event based on reports or system searches. Volunteers enter donor’s information by filling in easy-to-use screens. Management reports and searches on donors are available for events and date ranges. Volunteers record donations on centralized database and send Thank-you letters to donors by using templates stored in the database. Donors Automated Database

10. Original Project Volunteer Database Keep track of volunteer information o Volunteer Information o Volunteer Schedules o Reports o Search capability o Editable database with GUI Donor Database Keep track of donor information o Donor Information o Donor Status o Donor Interaction o Track Donations o Reports o Search capabilities o Editable database with GUI MS-Access SQL DB + WEB GUI Doubled in size

11. Functional Requirements  Create a Donors database  The Donors database will collect information concerning:   Organization/business  Contact person at organization/business  Contributions  Solicitors  Follow-ups  Develop a web application that includes the following items:  Database searching capabilities  User should be able to search database using grid view with sorting capabilities and search fields. The fields to include on the grid view are:  ConstituentType  OrganizationName  ContactFirstName  ContactLastName  City  State  ZipCode  Active  Notes (from tblConstituents)  CampaignID  GiftType  GiftSubtype  Value  Campaign  Appeal  Database reporting capabilities (including letters):  Donors who donated to a specific event sorted by donor. Fields to display: Event Name, Donor, Amount Donated, Donation Type, and sum of all donations and amounts  Donors who made a donation during a specific period of time, sorted first by event and then by donor. Fields to display: From date, To date, Donor, Event, Donation Type, Amount Donated  Donor’s contact person. Fields to display: Organization, Individual, Contact Person, Contact Information, E-mail, Mailing Address, Phone, Cell Phone  Mailing Labels. Fields to print/display: Organization, Contact Person, Mailing Address  Donations Received, ordered by event. Fields to display: Organization/Individual, Event Name, Date, Amount Donated, Donation Type.  Database insert/update/delete capabilities for donors and donations tables  User friendly graphical interface  Login capabilities to accommodate 3 levels of access  Administrator: full control  view, add, modify, delete, print reports  Management: everything the administrator does with the exception of deleting records from databases  Employees: should only be allowed to search for data and to print reports  Employees do not add, modify, or delete records on the table  Develop the needed tables to grant access to different users to the application/database.  Provide Angie with documentation regarding how to add/delete/modify records on the login database using SQL  Help menu capabilities on website  The current help menu on the prototype should be accessed by Angie only  There should be a second help menu for the rest of the users that allows them to view the documents, site map, and Angie’s e-mail  Ability to upload more documents in the future under the help menu  Create Customer Relationship Management (CRM) module  Send Thank You letter  Send Request for Donation letter  Create tracking for letters sent  Create tracking for e-mail sent  Create tracking for phone calls made

12. Scope, Time, Resources Scope = HUGE Time = FIXED Resources = Limited (5 MIS Student s with no organizational support) Conclusion: Cut the Scope Let’s discuss: Are there other options?

13. Consider options before building Found free software & eliminated programming!

14. Cut Scope – even with open source software CiviCRM 1.Eliminate mass mailing features -- export.csv file instead 2.Eliminate automatic email and mail tracking -- Only track thank you letters 3.Reduce access control from 3 levels to 2 4.Reduce number of searches/reports 5.Prioritize in-scope requirements 6.Determine critical path

15. Figure 3.6, p. 178 Preliminary investigation Analysis Design Preliminary construction Final construction System test and installation User Review Cut Over: Put system in production P D C A Phased Development Our Delivery 1 work led to a new view and an open source software solution. But we still had lots of tasks to get this into production for Latinitas !!

16. More Analysis, Design, & lots of Construction  Cutting the scope took away a large part of the system’s functionality  Search for a solution  SourceForge.net SourceForge.net  Wikipedia Open Source List Wikipedia Open Source List  inWent inWent  Google Google  Finding a web host  After 4 installs, found byethost  Learned PHP

17. MIS 374 – Day 2 Outline 1.Latinitas revisited: more of the story 2.The SDLC 1.Stakeholders & Communication 1.Next class reminders 2.Exercise #2 – in-class: Stakeholders Table for Latinitas

18. SDLC Approaches

19. Middle tasks MIS 374 Development Process Model * Construction 1 Inception Early tasks Wrap-Up *SDLC: System Development “Life Cycle” 374 compared to Agile Construction 2 Construction #n

20. MIS 374 – Day 2 Outline 1.Latinitas revisited: more of the story 2.The SDLC 1.Stakeholders & Communication 1.Next class reminders 2.Exercise #2 – in-class: Stakeholders Table for Latinitas

21. Katie gives you everything in K! Functional Requirements ___________

22. Middle tasks In 333K: Web flow design Web page design Coding – build functionality Final Construction n Inception Early tasks In 333K: ERD design Wrap-Up But don’t worry. You’ve used parts of SDLC Unit testing with build? You have to figure all this in 374!

23. Who will benefit by the new MIS 333K system is affected by the

24. Who needs to be involved in the development of the first release of the MIS333K system

25. Who will support the system in production

26. Who will enhance and trouble shoot the MIS 333K system

27. Who will be opposed to this system and the change

28.  Develop a plan to communicate!  Who to & How (Obj/Message, Channel, Timing)  Have Escalation Plan too – What if no responsiveness? We know our stakeholders…what next?

29. Result of poor stakeholder analysis & communication planning?

30. MIS 374 – Day 2 Outline 1.Latinitas revisited: more of the story 2.The SDLC 1.Stakeholders & Communication 1.Next class reminders 2.Exercise #2 – in-class: Stakeholders Table for Latinitas

31. Exercise 3a –Process Modeling Resource (due before next class) Schedule Page

32. Exercise 3b – Root Cause (due before next class) Resource Page Schedule Page

33. Also bring to class Schedule Page

34. Dreamspark– Visio and MS Project

35. Exercise #2 Work alone or with a partner Now until end of class Turn in via link on Canvas by deadline in class

36. Walter Golding  Senior, MIS Major  Tennis, biking, cooking  Client Project = Structured Motivation  Summer: Google  Tips for Success on Client Project  Meet weekly with your client  Learn any new languages before you even try to start working

37. Garrett Kreitman