Service: Research Proposal Writing
Style: Other
Number of pages: 6 pages (1650 words)
Number of sources: Up to the Writer
Topic of your paper: IT Project Management Proposal (choose any project topic such as building a Shopping Website!)
Subject: – IT Management
Comment:
Hello there! 🙂
First, for the Paper Type, I did not know what to choose since this is a “Project Proposal” from my IT Project Management class.
Second, and this is important! My grammar is always better than my vocabulary, so please keep the vocab as SIMPLE as you can, I never write too complex sentences or
high-level, fancy terms. I’m not a native english speaker! My overall IELTS score is 6.5 if that can help you estimate my level in english.
Please read the professor’s requirements in the template attached carefully.
If you have any questions or concerns, please ask ahead of time so I can ask my instructor and get back to you.
Senior
Project Proposal
Date
Author(s)
? Project Overview
? Introduction
The introduction provides a brief summary of what the project is designed to achieve, along with some background information on why the project is being done –
describe benefits or usefulness of the project. This should be one or two paragraphs; no more than one page. Think in terms of “business requirements.” We do
projects to satisfy some type of business/customer need. The introduction should identify the primary customer for the project, the customer’s needs or requirement
(at a summary level) and what the project will deliver to satisfy the customer’s business need.
? Period of Performance
This section should define the time period over which the project will occur. The timeframe for the project can be pre-determined or based on a completion date to
coincide with some external requirement (i.e. new Government regulation). It is important to define the period of performance since this is usually a variable in the
project’s cost. Additionally, if there are delays in a project and it will not be completed within the defined period of performance, a contract modification may be
required and the costs of the project will increase as well. For the purposes of this assignment, establish project dates assuming you would be conducting the
project next semester.
? Project scope statement (this is the most critical element of the project proposal; in it you specifically identify your deliverables and may also need to
provide an explanation of some tasks or deliverables that will be considered outside of your project scope. WHILE YOU DO NOT NEED TO CREATE THESE PROJECT DELIVERABLES
FOR THIS ASSIGNMENT; YOU MUST IDENTIFY A PROJECT THAT YOU OR YOUR TEAM COULD REALISTICALLY IMPLEMENT!)
The project scope details the work to be taken in order to satisfy the customer’s business requirement. This scope is ultimately be the basis of the project plan. The
primary focus of this section is to identify the project deliverables that will be provided to the customers to satisfy their requirements. It can be useful to
include a work breakdown structure of deliverables (see example high-level WBS for website development).
This section only outlines the project scope and the approach for implementing the project. This is a very high-level/executive summary of the project. For example,
what work will you do. What support do you expect to receive from faculty or project sponsor? For example, you may need faculty or lab technician support to identify
and configure hardware required to support the effort. You may need some participation from project sponsor (if there is one) or intended user to further refine
project requirements or provide other required information. Identify major milestones, the expected project duration, and budget estimate (if applicable). Identify
the major milestones.
Include a final sentence in this section indicating that more detailed project description are included in the attached project SOW at Appendix A and project WBS-
schedule at Appendix B.
? Assumptions and Constraints
In order to plan this project it may be necessary to make a number of assumptions. These assumptions are based on the knowledge of the stakeholders, the student and
faculty advisor, in this case. In some cases, these assumptions will need to remain throughout the duration of the project, but it should be expected that the majority
will be validated or adjusted as the project progresses.
? Assumptions can be listed as simple bullet points, just make sure that they are comprehensive enough to allow all readers to understand what is being assumed.
See example of a list of realistic project constraints. You can modify for use as appropriate and should probably want to add some additional assumptions.
Assumptions used in creating this project proposal include:
? Project requirement suitably defined and agreed upon by student (team), faculty advisor, and project customer (if applicable) by date stipulated in project
milestone.
? Student team and faculty advisor already possess requisite technical knowledge to create specified deliverables or will be able to develop required knowledge
during the course of the project.
? Hardware and software required to implement project will be available in time to support project schedule at Appendix B.
? Faculty supervisor will provide timely approvals and feedback on interim project deliverables.
? Project customer (if applicable) will provide timely approval and feedback on interim deliverables.
? Work time estimated to complete project tasks reasonably accurate.
? Project schedule assumes no extended illness or family emergency on the part of student (team), faculty advisor, and customer (if applicable).
? Risks
Demonstrate that you have thought about factors that might keep the project from being successful by listing project risks.
Project risks identified in creating this proposal include:
? Failure to clearly understand project requirements.
? Lack of technical knowledge required to create project deliverables.
? Unavailability of or delay in obtaining resources, primarily hardware and software, but also including information, required to complete project design and
development of deliverables.
? Unforeseen extended health or family emergency (one that impacts student availability to work on project for two weeks or longer)
? Major Stakeholders including Roles & Responsibilities
The chart below identifies the roles that will be played by the main groups on this project. As the project structure becomes clearer, this chart will be updated to
reflect individuals rather than generic roles, and will also identify any exceptions for specific work areas. Additionally, a greater level of detail will be provided
through the addition of additional tasks. There are five different functions in the RASCI chart:
Responsible – The role(s) that is expected to complete the work
Accountable – The role that is expected to ensure that the work is completed (escalation point)
Sign-Off – The role(s) that is expected to approve the work
Consulted – The role(s) that is consulted on/contributes to the completion of the work
Informed – The role(s) that receives the output of the work and/or receives status reports on the progress of the work
Roles / Responsibilities
Student (add columns as required for team Faculty supervisor Project sponsor Lab technician Vendor support
Create project proposal A, R C C C C
Approve project proposal I A, R C C
Select significant tasks from project schedule; examples below:
Create software (or website) design A, R C C
Approve design A C R
Develop software A, R C I
Some key points on a RASCI chart:
? Change the columns to reflect what works for you, and use rows that make sense – these are very generic examples, but you can make it as detailed as you wish.
My only guidance here is to make it meaningful – no one is going to read a 200-row RASCI chart
? There aren’t too many rules on the roles that go into a RASCI chart, but try and keep the following in mind:
? Every task should have a role that is identified as accountable, but only one
? Every task should have a role that is identified as responsible, and there may be more than one role responsible
? Schedule/Milestones
This section should define the schedule of deliverables and milestones for this project. Since the SOW often accompanies the RFP for the project, it is imperative
that all milestones, tasks, and schedule information are as accurate as possible since vendors will need to consider these items in their proposals.
Acceptance
Approved by:
Date:
<Approvers Name-Faculty advisor>
<Approvers Title>
Appendix A. Statement of Project Requirements
This is important but tricky section to write. As we have discussed, we need a firm understanding of project requirements to plan a good project. But in many IT
projects, our understanding of requirements grows and the project progresses. Furthermore, there are many different types of projects so there are many different
types of project requirements. The following guidelines relate to the development of generic software development projects. BUT THESE EXAMPLES CAN BE ADAPTED TO MEET
THE REQUIREMENTS OF YOUR PROPOSED PROJECT.
? User Classes
<The identification of user classes is most often identified with software development projects, e.g., describes types of users and their capabilities who is going to
use the database or mobile application. But this idea also applies to purchased software and even the use of hardware. Identify the various user classes (types of
users) that you anticipate will use this product. For each category or class of user, briefly describe their anticipated technical capabilities. That is, will the
system be used by an untrained user, or an IT technical professional? Some requirements might pertain only to certain user classes. >
? Operating Environment external interfaces (if applicable)
<Describe the environment in which the software, system or service will operate, including the hardware platform; operating systems and versions; geographical
locations of users, servers, and databases; and organizations that host the related databases, servers, and websites. List any other software components or
applications with which the system must peacefully coexist. If extensive technical infrastructure work needs to be performed in conjunction with developing the new
system, consider creating a separate infrastructure requirements specification to detail that work THIS SECTION IS VERY IMPORTANT AS IT IDENTIFIES LAB REQUIREMENTS
THAT YOU MAY NEED TO COORDINATE WITH THE CTI LAB COORDINATORS. IF YOU PROJECT REQUIRES A CAPABILITY THAT WE CANNOT PROVIDE IN THE LAB, THAT IS A PROJECT CONSTRAINT
AND MAY REQUIRE A CHANGE TO YOUR PROJECT PROPOSAL.>
? System Features/Functional Requirements
<This template is primarily designed to support software specifications but can be adapted to other types of projects. The template illustrates organizing the
functional requirements for the product by system features, the major services provided by the product. You may prefer to organize this section by use case, mode of
operation, user class, object class, functional hierarchy, stimulus, response, or combinations of these, whatever makes the most logical sense for your product.>
? System Feature 1 or Project requirement 1
<Don’t really say “System Feature 1.” State the feature name in just a few words Provide a short description of the feature and indicate whether it is of High, Medium,
or Low priority.>
? Functional Requirements
<This level of detail required for software development projects. Describing requirements at the feature level is probably adequate for lab oriented projects where
you are demonstrating the features of some open source or commercial software. Itemize the specific functional requirements associated with this feature. These are
the software capabilities that must be implemented for the user to carry out the feature’s services or to perform a use case. Describe how the product should respond
to anticipated error conditions. Use “TBD” as a placeholder to indicate when necessary information is not yet available. It may be useful to create context diagram,
use cases, or DFDs to support description of the functional requirements. You and your faculty supervisor will determine what level of detail is required.>
? System Feature 2 or project requirement 2 (and so on, should have at least three system features)
? Other Requirements
<For the purposes of capstone projects, these would primarily consist of reports, presentations, instructions or procedures. But any document or other project
artifact to be delivered to the faculty supervisor. >
Appendix B
A professionally formatted MS project report showing project tasks and Gantt chart.
