schedulepro
play

SchedulePRO Scheduling made easy! Outline Staffing Chart - PowerPoint PPT Presentation

May 23, 2023 •95 likes •674 views

SchedulePRO Scheduling made easy! Outline Staffing Chart Meetings Today Problem Current Process SchedulePRO Process Customer Project Modules Workforce Development Risk Matrix Competition Matrix

  1. SchedulePRO Scheduling made easy!

  2. Outline Staffing Chart • Meetings Today • Problem • Current Process • SchedulePRO Process • Customer • Project Modules • Workforce Development • Risk Matrix • Competition Matrix • Conclusion • 11/28/2011 CS 410 - Green Team 2

  3. Staffing Chart 11/28/2011 CS 410 - Green Team 3

  4. Meetings Today There are over 11 million meetings held daily in the United • States (1) Most professionals attend a total of 61.8 meetings per • month (1) 1: EffectiveMeetings.com • 11/28/2011 CS 410 - Green Team 4

  5. Problem Scheduling meetings for large groups of people is a complex, • frustrating, and inefficient process 11/28/2011 CS 410 - Green Team 5

  6. Current Process 11/28/2011 CS 410 - Green Team 6

  7. Venue Availability for Dec. 25th 11/28/2011 CS 410 - Green Team 7

  8. Attendee/Venue “A” Availability for Dec. 25th 11/28/2011 CS 410 - Green Team 8

  9. Attendee/Venue “A” Availability for Dec. 20-25 11/28/2011 CS 410 - Green Team 9

  10. Attendee/Venues A/B/C Availability for Dec. 20-25 11/28/2011 CS 410 - Green Team 10

  11. SchedulePRO! SchedulePRO takes the grunt-work and back-and-forth out of • coordinating meetings, allowing you to focus on the real goal: an effective and well-attended event 11/28/2011 CS 410 - Green Team 11

  12. SchedulePRO Process 11/28/2011 CS 410 - Green Team 12

  13. Customer Higher Education • Geographically-distributed Teams • • Organizations/Businesses that utilize a shared calendar system 11/28/2011 CS 410 - Green Team 13

  14. Project Modules SchedulePRO Data Messaging Interface Algorithm Legal Interfaces System 11/28/2011 CS 410 - Green Team 14

  15. Project Modules SchedulePRO Data Messaging Interface Algorithm Legal Interfaces System Coordinator Interface Attendee Interface 11/28/2011 CS 410 - Green Team 15

  16. Milestones: Human Interfaces Requirements Phase: 1. Finalize list of parameters. a. Choose list of required parameters. 2. Sketch administrative functionality. 3. Write testing requirements. 11/28/2011 CS 410 - Green Team 16

  17. Milestones: Human Interfaces Design Phase: 1. Elaborate coordinator workflow. 2. Design input/output/profile GUIs. 3. Write tests. 11/28/2011 CS 410 - Green Team 17

  18. Milestones: Human Interfaces Implementation Phase: 1. Code. a. input GUI b. output GUI d. external profile c. administrative functionality 2. Integrate with algorithm. 3. Integrate with messaging system. 11/28/2011 CS 410 - Green Team 18

  19. Meeting Creator GUI 11/28/2011 CS 410 - Green Team 19

  20. Room and Resource Creation 11/28/2011 CS 410 - Green Team 20

  21. Meeting Timeframe 11/28/2011 CS 410 - Green Team 21

  22. Attendee Managment 11/28/2011 CS 410 - Green Team 22

  23. Coordinator Management 11/28/2011 CS 410 - Green Team 23

  24. Room and Resource Management 11/28/2011 CS 410 - Green Team 24

  25. Update Daemon Configuration 11/28/2011 CS 410 - Green Team 25

  26. Project Modules SchedulePRO Data Messaging Interface Algorithm Legal Interfaces System 11/28/2011 CS 410 - Green Team 26

  27. Project Modules SchedulePRO Data Messaging Interface Algorithm Legal Interfaces System Optimization Algorithm 11/28/2011 CS 410 - Green Team 27

  28. Optimization Algorithm Requirements - Establish a means to populate a list of possible • meetings and establish a means to sort and exclude meetings based on coordinator preference • Analysis - Research established algorithm methods and determine applicability • Implementation - Implement developed design • Integration - Integrate algorithm with GUI and data interfaces Testing - Use randomized test cases, as well as custom test cases, to • evaluate accuracy and performance in various situations. 11/28/2011 CS 410 - Green Team 28

  29. Optimization Algorithm Algorithm Start Create a comprehensive list of possible meetings Calculate fitness for each potential meeting, based on parameters set by coordinator Order potential meetings based on fitness Present ordered list to coordinator review interface Algorithm End 11/28/2011 CS 410 - Green Team 29

  30. Project Modules SchedulePRO Data Messaging Interface Algorithm Legal Interfaces System 11/28/2011 CS 410 - Green Team 30

  31. Project Modules SchedulePRO Data Messaging Interface Algorithm Legal Interfaces System Local Server Calendar Import Resource Database 11/28/2011 CS 410 - Green Team 31

  32. Data Interfaces Google Calendar, Microsoft Exchange Server, and Banner • Acquire availability and resource information from third party • data sources By customer request, SchedulePRO will be tailored to retrieve • data from additional data sources 11/28/2011 CS 410 - Green Team 32

  33. 11/28/2011 CS 410 - Green Team 33

  34. Project Modules SchedulePRO Data Messaging Interface Algorithm Legal Interfaces System 11/28/2011 CS 410 - Green Team 34

  35. 11/28/2011 CS 410 - Green Team 35

  36. 11/28/2011 CS 410 - Green Team 36

  37. 11/28/2011 CS 410 - Green Team 37

  38. 11/28/2011 CS 410 - Green Team 38

  39. 11/28/2011 CS 410 - Green Team 39

  40. Workforce Development 11/28/2011 CS 410 - Green Team 40

  41. Risk Matrix T1, C3 S1, F1 C2 Impact C1 Probability C1 - Adoptability & GUI Difficulty S1 - Development time C2 - Data Inaccuracy T1 - Third-Party Data Availability C3 - Schedule Privacy F1 - Development costs 11/28/2011 CS 410 - Green Team 41

  42. Schedule Risks S1 - Development Time • • Impact: 3 • Probability: 1 • Problem: Development must proceed as quickly as possible to prevent competition from producing product first. • Mitigation: Proper estimation of development time and efficient scheduling. 11/28/2011 CS 410 - Green Team 42

  43. Financial Risks F1 – Development Cost • • Impact: 3 • Probability: 1 • Problem: Development cost may outweigh either initial investment or expected income from sales • Mitigation: We will create a proper cost estimation, as well as research into necessary product price point and annual service charges 11/28/2011 CS 410 - Green Team 43

  44. Technical Risks T1 - Third-Party Data Availability • • Impact: 4 • Probability: 2 • Problem: There may be legal roadblocks preventing us from accessing data that is part of a proprietary system. The data also may not exist • Mitigation: SchedulePRO will provide tools that an attendee can use to enter & update their availability 11/28/2011 CS 410 - Green Team 44

  45. Customer Risks C1 - Adoptability & GUI Difficulty • • Impact: 2 • Probability: 4 • Problem: The large number of parameters that both coordinators & attendees enter in their respective interfaces creates potential for a cumbersome, difficult interface • Mitigation: The SchedulePRO attendee & coordinator interfaces will be easy to learn & scalable 11/28/2011 CS 410 - Green Team 45

  46. Customer Risks C2 - Data Inaccuracy • • Impact: 3 • Probability: 3 • Problem: The scheduling algorithm can only produce results as good as the data it is given. Attendee availability accuracy is affected by the "human factor," some people just do not maintain or update their schedule • Mitigation: SchedulePRO will send attendees an update notification message that will contain a link to the SchedulePRO availability editor in which they can revise and confirm their availability 11/28/2011 CS 410 - Green Team 46

  47. Customer Risks C3 - Schedule Privacy • • Impact: 4 • Probability: 2 • Problem: People may not want to share details about personal events or obligations 11/28/2011 CS 410 - Green Team 47

  48. Risk Matrix T1, C3 S1, F1 C2 Impact C1 Probability C1 - Adoptability & GUI Difficulty S1 - Development time C2 - Data Inaccuracy T1 - Third-Party Data Availability C3 - Schedule Privacy F1 - Development costs 11/28/2011 CS 410 - Green Team 48

  49. 11/28/2011 CS 410 - Green Team 49

  50. 11/28/2011 CS 410 - Green Team 50

  51. 11/28/2011 CS 410 - Green Team 51

  52. Conclusion Is this a problem? • Why more software? • Headroom in the market • Expected long product life cycle • 11/28/2011 CS 410 - Green Team 52

Recommend

More recommend