Client

Shannon Osburn, CIT Custom Development
Email: <sml34@cornell.edu>

Additional contact

Ryann Levo
Email: <ryann.levo@cornell.edu>

Student contact

Qi Sun, <qs66@cornell.edu>

Project Summary

The client has written the following description of the project.

The Team

Custom Development is a unit within CIT’s Enterprise Application division. Primarily the team provides for-fee web application and website services to the Cornell Campus, supporting over 150 websites and web applications along with running 40-60 projects at any given time. The team size is roughly 30, ranging from web developers to web designers and UX specialists to Customer Engagement Managers.

Project Summary

The team currently uses a very large Excel file driven by many Macros to schedule all project and support hours across all resources. This is critical to maintaining normal workloads across team members. Ensuring they can schedule and meet customer deadlines, have the ability to know when they can take on new work and ensure time away, internal projects and training are all factored in to the allocations. The current file (known as the Resource Chart) provides calculations at the bottom flagging when someone is overbooked during a given week. When the Macros break a contractor is needed to try and repair. Losing the file drastically hinders the business function provided to the university.

The Timeline

The new application could be put in to production for use as soon as its production ready. Ideally, by the end of the spring semester a fully functional and tested system would be ready for production and support handoff.

Technology

Ideally one of the following technologies would be used so the system can be supported once in production: PHP, Laravel, Drupal or WordPress. Drupal backend with a React frontend could be considered as well.

Overall, the team would need to have the following experience (or be willing to learn):

• Light business analysis (reviewing the current file to document all needed functionality)
• One of the technologies noted above
• Full-stack development
• SSO (by Cornell NetID)
• Web security best practices
• Some knowledge of hosting environments
• Some knowledge of creating usable web interfaces