IT Solution Consultancy
Main contact
Timeline
-
January 7, 2018Experience start
-
October 26, 2017Midway Check In
-
January 30, 2018Project Scope Meeting
-
April 16, 2018Experience end
Timeline
-
January 7, 2018Experience start
-
October 26, 2017Midway Check In
In the mid way point of the project (Week 6), students will produce and submit a project proposal. In the proposal, students present a clear diagnosis of the problem or opportunity, high-level definition of systems requirements, a preliminary feasibility analysis (economic, operational and technical), and a project plan (details of their next steps until the end of the project). To your company, this will be the equivalent of a go-no-go decision. You will required to give students permission to continue, feedback and suggestions for improvement are welcome.
-
January 30, 2018Project Scope Meeting
Meeting between students and organization to confirm: project scope, communication styles, and important dates.
-
April 16, 2018Experience end
Experience scope
Categories
Information technologySkills
it consultancy process analysis project planning risk assessment schedulingTeams of student-consultants will research and develop technological solutions to a challenge or opportunity of an organization's choosing. They will provide a cost-benefit analysis and recommended vendors and an implementation plan.
Students
Student-consultants will submit a report that includes:
- A comparison of three possible technology solutions.
- Justification for the selection of the top solution.
- A feasibility study and risk analysis.
- A cost-benefit analysis.
- An implementation plan.
Project timeline
-
January 7, 2018Experience start
-
October 26, 2017Midway Check In
-
January 30, 2018Project Scope Meeting
-
April 16, 2018Experience end
Timeline
-
January 7, 2018Experience start
-
October 26, 2017Midway Check In
In the mid way point of the project (Week 6), students will produce and submit a project proposal. In the proposal, students present a clear diagnosis of the problem or opportunity, high-level definition of systems requirements, a preliminary feasibility analysis (economic, operational and technical), and a project plan (details of their next steps until the end of the project). To your company, this will be the equivalent of a go-no-go decision. You will required to give students permission to continue, feedback and suggestions for improvement are welcome.
-
January 30, 2018Project Scope Meeting
Meeting between students and organization to confirm: project scope, communication styles, and important dates.
-
April 16, 2018Experience end
Project examples
Requirements
Beginning this January, student-consultants in teams of four will spend 200+ hours per group developing a technological solution to a challenge or opportunity of organization's choosing.
Based on your goals and the information provided, student-consultant groups will help you clarify your needs, develop high-level requirements for a new system, procure potential vendors, and recommend the best IT solution for your needs.
Project scopes can include, but are not limited to:
- Improving sales and marketing performance by identifying a suitable CRM system.
- Addressing website performance issues with a new hosting provider.
- Streamlining procurement and accounts payable by identifying procurement software.
- Using technology to build your recruitment pipeline or streamline the recruitment process.
- Improving sales and order fulfillment with an inventory management software tool.
- Identifying marketing tools to increase customer acquisition.
Additional company criteria
Companies must answer the following questions to submit a match request to this experience:
Main contact
Timeline
-
January 7, 2018Experience start
-
October 26, 2017Midway Check In
-
January 30, 2018Project Scope Meeting
-
April 16, 2018Experience end
Timeline
-
January 7, 2018Experience start
-
October 26, 2017Midway Check In
In the mid way point of the project (Week 6), students will produce and submit a project proposal. In the proposal, students present a clear diagnosis of the problem or opportunity, high-level definition of systems requirements, a preliminary feasibility analysis (economic, operational and technical), and a project plan (details of their next steps until the end of the project). To your company, this will be the equivalent of a go-no-go decision. You will required to give students permission to continue, feedback and suggestions for improvement are welcome.
-
January 30, 2018Project Scope Meeting
Meeting between students and organization to confirm: project scope, communication styles, and important dates.
-
April 16, 2018Experience end