1.0 Project summary

Project code

Project name

Project start date and end dates

Project type

Project objective

Project scope summary

Project deliverables summary

Project sponsor/client and contact details (phone, physical address and email)

Project team – full name (ID), contact details (phone & email), project role

End-users – description of users of system (if project product is system)

Assigned academic supervisor

2.0 Project background

2.1 Organisation

<<Insert background to the organisation here

 

Questions to answer:

• Who are they – name?
• Where are they located? Do they have web presence?
• How do they operate/business operations model?
• How many employees and where are these employees located?>>

NB: This “organisational” background is not relevant for research-oriented IT7x01 projects.

2.2 Problem/Opportunity

<<Insert the background to the problem and problem domain here in detail. This section could include the problem and/or the opportunity.>>

3.0 Project objectives & scope

3.1 Project objectives

<<Insert project objective (s) here – write at least a minimum of 1 paragraph

• Objectives discuss the desired end results of the project, not how those results will be accomplished. Include a timeframe (start/end dates)
• Objectives should flow logically from the problem statement/needs assessment.>>

3.2 Scope

<<Insert at least one paragraph introducing this section

3.2.1 Project scope

<<Insert project scope here. >>

3.2.2 Product scope

<<Insert product scope here. Only include high level scope, and NOT detailed requirements specification>>

3.3 Deliverables

<<Insert deliverables here scope here.

Clearly identify academic deliverables >>

4.0 Initial consultation

<<Insert at least one paragraph introducing this section, then (reformat) and insert the details of your initial meeting (consultation with the client/supervisor)>>

5.0 Communication plan

<<Insert at least one paragraph introducing this section, then use the template provided in the Level 7 Project management course.>>

6.0 Methodology

<<Insert at least one paragraph introducing this section.

Identify – the methodology

Outline why this methodology is appropriate for this project, with evidence to it used in similar projects

Detail the methodology – phases, outputs, roles/personnel etc. Include a diagram to depict the methodology. Clearly reference any diagrams and material you use. DO NOT COPY-PASTE material from the internet.>>

7.0 Resourcing and budgeting

<<Insert at least one paragraph introducing this section. Then

• Overview of resources required for this project – HR, tools/technologies,

8.0 Project plan

<<Insert at least one paragraph introducing this section. And the two(?) sections – WBS and Project iterations.

The project iterations can be extracted from the Gantt chart (if you create it first). The iteration could align with

• Phases, or
• Iterations (for iterative methods) or
• Milestones >>

8.1 Work breakdown structure

<<Insert at least one paragraph introducing this section. WBS can either be in a diagrammatic format or in a linear (tabular) format >>

8.2 Iterations and time estimates

<<Insert at least one paragraph introducing this section. Use the provide blank form for each iteration

Copy the table template below to create as many iterations you need.

 

An iteration is akin to a phase – and has outcomes; this section is work 20 marks in the proposal marking guide>>

Project Iteration 1
Project
Project Number
Project Name
Student Name		Student ID
Iteration Date
Iteration Detail
Iteration Number
Iteration Name
Iteration Completion Date
Iteration Objective
Iteration constraints and risks
	Iteration Products/Outcomes
1.	e.g. Database design
2.	e.g. Prototype presented to client
3.	e.g. Client feedback recorded
4.
5.	Add more rows if necessary

9.0 Risk analysis, contingency and mitigation

<<Comments: Insert all risks into the table below. Change the page format to landscape mode if required.

Put an introductory statement at the start of this section to introduce these risks

 

Group/categories your risks – see http://management.simplicable.com/management/new/130-project-risks for 130 project list for ideas

 

Typically you’ll have between 10-20 risks identified in this section>>

Risk #	Risk	Risk description	Impact	Probability	Contingency	Mitigation
1	System software corruption/ loss					Using SVN system

10.0 Skills analysis

<<Comments: This section requires you to conduct a skills analysis – including identifying the skills gap and what you intend to do to bridge this gap.

• Skills (and skill levels) required
• Team’s current skill levels
• Gap: how to the team will bridge this skills gap

 

Insert at least one paragraph introducing this section. Use the following table as a starting point for your analysis>>

General	Current skill level	Required skill level	Gap
Project management	5	7	Take tutorials on Project management tools and review previous PM course
Technical documentation
Technical
CMS configuration	4	8
Template design
Web programming – ASP.NET
Etc.

Rating scale of 1 to 10, where 1 is novice and 10 is expert

11.0 Project agreement

Student Team Project Agreement

WHITIREIA COMMUNITY POLYTECHNIC

FACULTY OF BUSINESS AND INFORMATION TECHNOLOGY

STUDENT(S) PROJECT AGREEMENT

The Parties

This Student(s) Project Agreement (the “Agreement”) is made between:

1. a) Whitireia Community Polytechnic Faculty of Business and Information Technology (the “Faculty”);
2. b) the nominated computing student(s) (the “Student(s)”) (as listed under section 6); and
   ________________________________ the proposed Industry Organisation (the “Organisation”).

BACKGROUND

1. a) As part of an established course of study at the Faculty, Bachelor of Information Technology students take a course module IT301, in which the Student(s) completes a project (“the Project”) with the Organisation on the basis set out in this Agreement.
2. b) The Organisation agrees to allow the Student(s) access to its premises if needed to undertake that Project on the basis set out in this Agreement.
3. c) The Faculty is satisfied that the Organisation is suitable for the Student(s) Project.

TERMS

1. Effective Date
   This Agreement shall be effective as of ____________________ until ________________

 

2. Undertakings

 

2.1   The Organisation has accepted the Student(s) and agrees to allow that Student(s) access to its premises as needed.

2.2   The Organisation agrees to be responsible for meeting the requirements of its statutory obligations, eg Health and Safety in Employment Act, Human Rights Act, etc., for the Student(s).

2.3   The Student(s) will use his or her best efforts in undertaking the Project for the Organisation, as mutually agreed by the parties and set out in a separate written proposal which will form part of this Agreement.

2.4   The Organisation understands that the primary reason for the Project is education and advancement of knowledge, and, consequently, the Project must further that purpose.

2.5   Neither the Faculty nor the Student(s) guarantee specific results and the Project will be undertaken only on a best efforts basis.

2.6   The Student(s) agrees to submit his or her IT301 report to his or her nominated supervisor at the Organisation.

3       Copyright, Patents, Trade Marks and other Intellectual Property Rights

 

The Faculty and Student(s) each acknowledge that all copyright, trade marks, trade names, patents and other intellectual property rights belonging to the Organisation that the Faculty and Student(s) come into contact with are and shall remain the sole property of the Organisation, and no claim or right to them is to be made by or created in the Faculty or Student(s).

4       Confidential Information

4.1   The parties may wish, from time to time, in connection with the Project undertaken under this Agreement, to disclose certain information of a confidential nature (“Confidential Information”) to each other.  Each party will use reasonable efforts to prevent the disclosure of any of the other parties Confidential Information to third parties for a period of three (3) years from receipt of that information, provided that the recipient party’s obligation shall not apply to information that:

1. a) is not disclosed in writing or reduced to writing and marked with an appropriate confidentiality legend or designated in writing as Confidential Information within thirty (30) days of disclosure;

1. b) is already in the recipient party’s possession at the time of disclosure;

1. c) is or later becomes part of the public domain through no fault of the recipient party;

1. d) is received from a third party having no obligations of confidentiality to the disclosing party;

1. e) is independently developed by the recipient party; or

1. f) is required by law or regulation to be disclosed.

4.2   Application may be made to any party for written permission to use Confidential Information.  No party shall unreasonably withhold such permission.

4.3   If permission to use Confidential Information is withheld by a party, then that party will state the reason or basis for refusal of permission.

5       Intellectual Property Rights

 

5.1   The parties agree that both the Faculty and the Student(s) may use the intellectual property rights that are created as a result of the Project work undertaken by each Student for the Organisation for portfolio purposes to promote the Faculty and/or the Student(s).

5.2   The following intellectual property rights are agreed between the parties:

(Please indicate which option is agreed upon by placing a tick in the appropriate box and deleting the options that do not apply.)

Project Proposals are a very important part of a number of courses and students find Project proposals very hard to complete. Hence, for Project Proposal Assignment Help, you can visit www.makemyassignments.com.