For SCORE Project Sponsors
(NOTE: Only SCORE Program Committee members may sponsor a project. This page is for them)
We need a good number of projects for teams to choose from!
A project sponsor (or proposer) does not need to expect to take on a tremendous burden of work. Yes, you will need to define the project, but you can determine your own level of interaction with teams (even down to none), and we can adjust your reviewing activity to compensate. So propose a project!
A project definition needs to have:
- A project short name: try to make a catchy, self-explanatory name for your project.
- The project title and a short description (abstract) of the idea.
- A longer narrative of the problem that gives enough detail for a team to actually go out and work on the project.
- A scoping statement for the project that helps teams understand what must be, what may be, and what does not need to be part of the project, in order to help them understand what is asked for.
- A statement of any process requirements that teams must follow.
- A statement of expected user capabilities if your project is user oriented.
- A statement of any environmental constraints (equipment, external interfaces, or other external constraints) that must be satisfied.
- A statement of the level of involvement that you as the project sponsor will undertake; this can be something like "will answer selected questions once per semester (Spring and Fall 2015)" or "teams must find and document their own customers to clarify problem requirements; project sponsor will not be involved".
- Any restrictions or requirements on what external software cannot or can be used, including commercial tools, open source libraries or frameworks, etc.
You are encouraged to use this project template (open and then save-as in your browser). You may also want to look up project descriptions from previous editions of SCORE to get an idea of the variety of aspects that you can cover.
A project sponsor has a conflict with a team if one or more of the team members are students of the same institution as the sponsor during project development (the whole calendar year 2015), or if the sponsor has collaborated with one or more team members in research or other work-related activities during the years 2014, 2015, or both. A team cannot develop projects proposed by sponsors that are in conflict with members of the team. The team can still enter SCORE by picking another project topic. In this case, the sponsor cannot be the team's reference faculty member and will not review the team's submissions.