Franske ITC-2900 Assignments: Difference between revisions

From ITCwiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
==Statement of Work==
==Statement of Work==
After your team has selected a project to work on your next objective is to develop a Statement of Work (SoW). The SoW is your opportunity to take the very high level description of the project you were given and turn it into a more detailed description of your specific goals, operational procedures and timeline for the project. In order to successfully do this you will need to meet with the sponsor of the project and any other involved or related parties. One way to think of the SoW is as part of the contract you, as a consulting team, have with the project sponsor and ensure everyone is on the same page.


* Your group must develop a plan/schedule for your project, this can be updated as needed but you need to know when you are going to try and have certain phases of the project complete
Goals for the SoW:
* Clearly define the purpose of the project. Make sure that you understand what is important to the customer
* Give an overview/background of the technology involved. Make sure you have a basic understanding of the concepts you will be investigating and the problems you might encounter. Show that you have already started background research on the project.
* Define the scope of work. What will you need to do for the project sponsor to consider this a success?
* Describe any resources or cooperation you believe you will need in order to be successful
* Develop a plan/schedule for your project, this can be updated as needed but you need to know when you are going to try and have certain phases of the project complete
 
SoWs should be written in a narrative (paragraph) format (with the exception of a timeline) and should typically be about three or four pages single spaced. Your SoW will be graded based on how you meet the goals for the SoW listed above as well as professionalism (grammar, punctuation, etc.)


==Project Work Log==
==Project Work Log==

Revision as of 22:51, 14 January 2014

Statement of Work

After your team has selected a project to work on your next objective is to develop a Statement of Work (SoW). The SoW is your opportunity to take the very high level description of the project you were given and turn it into a more detailed description of your specific goals, operational procedures and timeline for the project. In order to successfully do this you will need to meet with the sponsor of the project and any other involved or related parties. One way to think of the SoW is as part of the contract you, as a consulting team, have with the project sponsor and ensure everyone is on the same page.

Goals for the SoW:

  • Clearly define the purpose of the project. Make sure that you understand what is important to the customer
  • Give an overview/background of the technology involved. Make sure you have a basic understanding of the concepts you will be investigating and the problems you might encounter. Show that you have already started background research on the project.
  • Define the scope of work. What will you need to do for the project sponsor to consider this a success?
  • Describe any resources or cooperation you believe you will need in order to be successful
  • Develop a plan/schedule for your project, this can be updated as needed but you need to know when you are going to try and have certain phases of the project complete

SoWs should be written in a narrative (paragraph) format (with the exception of a timeline) and should typically be about three or four pages single spaced. Your SoW will be graded based on how you meet the goals for the SoW listed above as well as professionalism (grammar, punctuation, etc.)

Project Work Log

  • Each INDIVIDUAL in your group must keep a work log indicating what was worked on, when, and for how long. This should be written in narrative (paragraph) format. It must be turned in at the end of the course but must be kept up to date throughout the course. Your instructor may ask to see a copy of your work log at any time.
  • You should also keep a separate log of the hours you INDIVIDUALLY worked on the project in a spreadsheet by date so that they can be graphed.

Progress Updates

  • Your group must provide weekly updates to the instructor on the progress of your group, these can be meetings or written updates
    • Written updates should be approved by the team before submitting to the instructor
    • Written updates sent to the instructor should be copied to all team members and
  • At least once every two weeks you must have a meeting with the instructor where your progress is discussed
    • Not all team members must attend this meeting but it is to your advantage to have as many as possible attend
    • Meetings may be held over the phone, by web conference, or in person

Presentations

Peer Evaluations

Final Written Report

Participation