Web Servies works on large systems that affect every person on campus. We're a pretty busy bunch, but if you have a project, problem, or idea, we'd love to hear about it. Here's how we handle new projects in Web Services:
Start talking with your colleagues not about technology, but about the needs of your department and the problems you are trying to solve. Gather your notes and ideas and shoot us an email at firstname.lastname@example.org.
After your email, we'll start an initial discovery process, usually a few meetings with your team. During this time, we might be able to solve your problems with existing solutions, or point you in the direction of some off-the-shelf software which meets your needs. If so, great, we're done! If it's determined that you do need a custom project, then it's off to the next step.
If we do end up working on a new project, then we'll need to put together a quote. Don't worry, we're not charging money, but we do charge time and access to your team members to ensure a project starts and finishes on time.
A typical quote is for a period of time (i.e. one month), as well as access to key team members that we can sit down with for long periods of time to test and refine your project. Web Services uses agile development, meaning even after the first few days of working on your project, you'll have something for your team to work with.
After figuring out how long it will take to work on your project, Web Services in consultation with the CIO will identify the project's priority that will ultimately give you a timeframe of when the project will begin. Projects are prioritized by their impact on students and retention first, followed by other enterprise concerns.
From day one of your project, we'll have a project website where all team members can login, see the progress of the project, give feedback, and answer our team's questions. We will give short, daily updates on your project's status, and hold weekly meetings with your team about what has happened that week. These weekly status meetings will help determine what features are done, and which ones should be worked on for next week, which helps prioritize work in a tight schedule.
At the end of a project's alloted time period, either the project is done, or it's at least partially functional. Projects that run over their quoted time will need to have additional time alloted, which means you might have to wait some more time before we can return to your project. This is why the discovery process is so important.
After a project is complete, we'll hand off the project to your team, and identify key people who can provide support to your users. Since they've been involved every step of the way, they'll be in a position to run the project on a day-to-day basis. After the hand-off, Web Services will work with these key team members to identify future issues and bug fixes, but any general questions or support requests should be handled by your team's support people.
No solution is without bugs, and we try to respond quickly when one is found. If you have a problem with a system on campus, report a bug using an IT Service Request, and make sure to select a "Web Services" problem type.