Employee Scheduling System
NDSU Student Technology Services Help Desk
Project Manager:Michael Attewell System Analyst: Michael Kraft Programmer/Web Analyst: Abram Jackson
Request for System
Help Desk of STS at NDSU needs a new scheduling system
Current Solution works poorly, high costs $260 weekly in scheduling management $225 weekly in employee time $5000 yearly savings from current license
Need a streamlined process
Request for System
Functions User accounts User availability Time-off requests Scheduling Management
Other Requirements Web-based Easy-to-use
Request for System
Organization will improve Employees will be happier with better system Employees will be more aware of upcoming
shifts so they will miss or be late less frequently Managers will spend more time on other areas of
the Help Desk
Technical Feasibility
Two of three analysts have experience using either the user or management portions of the current solution
Technology used is similar to current system Small to mid-size project Will be web-based, so compatibility will not
be an issue
Economic Feasibility
Largest development costs will be development labor
Initial costs will also involve purchase of a dedicated web server
First year of costs should be near $25,000 Additional years should only require $1,200
for maintenance
Economic Feasibility
Yearly benefits of saved employee and management time ~$17,000
Total yearly benefits ~$22,000
Break-Even Point 11-12 months
Cumulative Net Profit Value ~$35,000 at the end of 2009
Intangible benefits include both employees and managers devoting less time to scheduling
Stakeholders
The project's champion: John Underwood (Help Desk Workgroup Manager)
Senior manager Stephanie Robinson (Student Technology Services)
The users of the system All those employed by the Help Desk Other workgroups within STS
All students and faculty will be affected in some way
Project Management - Size
69 Function Points based on requirements Processing Complexity of 8 ASP.net requires 69 Lines of Code per
Function Point Adjusted Processing Complexity * Function
Points = 75 Total Function Points Project will require around 5100 Lines of
Code in ASP.net
Project Management – Effort and Time
Basic COCOMO model D=cb(E)^db
5.8 Person-Months 5.79 with 3 developers = 2.4 Months based on
favorable outcomes of risk assessment
Risk Assessment – #1
The programmer has limited ASP.NET coding experience.
Likelihood of Risk: High probability of Risk
Potential Impact on the Project: This risk could increase the time to implement the
IS by 50%. Ways to Address this Risk:
Provide adequate ASP.NET training to the programmer as soon as possible.
Risk Assessment - #2
The IS may not be able to handle multiple users at one time.
Likelihood of Risk: Low probability of Risk
Potential Impact on the Project: This risk could increase the time to implement the
IS by 15% Ways to Address this Risk:
Carefully design system to handle up to 100 users at one time.
Risk Assessment - #3
The interface for this IS may not be user friendly and could require considerable training for both staff and management.
Likelihood of Risk: Low probability of Risk
Potential Impact on the Project: This risk could increase the time to implement the
IS by 15% Ways to Address this Risk:
Carefully design the interface to ensure ease of use.
Risk Assessment - #4
The reports designed for this IS may not give management the perspective they need to effectively manage their staff
Likelihood of Risk: Medium probability of Risk
Potential Impact on the Project: This risk could increase the time to implement the
IS by 10% Ways to Address this Risk:
Interview managers to pinpoint the specific metrics they need to see on the report. Also design the report in way that is easy to read and usable.
Risk Assessment - #5
The IS may not be compatible with all web browsers
Likelihood of Risk: Medium probability of Risk
Potential Impact on the Project: This risk could increase the time to implement the
IS by 35% Ways to Address this Risk:
This IS must be designed so that it can be viewed by the most popular web browsers such as Internet Explorer, Safari, and Firefox.
Staff
Function Points = 75 Lines of Code = (TAFP)*(LOC per FP) = 75 * 69 = 5142
Effort in Person-Months required = (LOC/1000)*1.4 = 5.14*1.4 = 7.2
Schedule Time in Months = 3 * Effort^1/3
= 3*7.2^1/3 = 5.79 Staff needed = Effort / Schedule Time = 7.2/5.79 = 1.24
Staff
3 people to compensate for setbacks
M ich a e l A tte we llP ro je ct M a n a g e r
A b ra m Ja ckso nP ro g ra m m e r/ W e b A n a lyst
M ich a e l K ra ftS yste m A n a lyst
Work Plan – Breakdown Sheet
Work B reakdown S heetTask # Task Name Dur. Dependency Status
1Analyze Feasibility of Project 3 days Complete2Prepare a System Request 7 days 1 Complete3Meet with Help Desk Staff 1 day Open4Research Costs for Web Server/Server Software7 days 3 In Progress5Meet to Discuss Staffing 1 day 4,1,2 Open6Meet to Discuss Ground Rules for Project 1 day 5 Open7Develop Work Plan 2 days 5 In Progress8Compile Project Plan 1 day 7 In Progress9Compile System Proposal 7 days 8 Open
10Compile System Specification 7 days 9 Open
Work Plan - Gantt
Questions?