/
Vetting Process

Vetting Process

Mar 01, 2010

The 200-45 process of submitting applications for review is a good higher level process.  I'd like to see something where IT or non-IT people can bring their ideas to the table for comments.  A simple SmartSite forum perhaps would do fine.  From here we can take ideas not only generated by software developers, but by the people who need the software in the first place: they will always be the ones who know their processes best so why rob them of the ability to have input?

I see the process being similar to the below, with modification as anyone sees fit:

  1. Site for submitting application ideas: has it been done?  Is it useful to multiple departments?

    1.  Feedback from users, developers, IET.

    2. Use feedback to refine needs and details of what users require

    3. Have a meeting or two to define the software specifics and answer all questions

  2. Once an idea has been chosen, consider the elements of the SSWG rubric as you create the development plan.

  3. Determine funding model if shared/reusable application: bug fixes free, new features cost?  Who will host?  Who will be phone support?

    1. Include who will be in charge of development: College or IET

    2. Can you leverage programmers from other areas to work on portions of the software?

    3. Possible funding models

      1. Recharge rates for programming, maintenance, support via contract or hourly billing

      2. Software-in-kind: I'll make changes to Timesheets if you make changes to Faculty Recruitment

  4. 200-45 formal review for large scale projects

    1. Re-apply the rubric for feedback

  5. Development of application in platform decided by SSWG recommendations.

  6. Demo and pilot.