The best titles are descriptive, succinct, and a little bit clever
(1 to 3 paragraphs)
- What is the history of the problem?
- Why is this problem interesting?
- When and why does the problem occur?
- Is the problem already solved? What is done now?
- Are there any similar systems or solutions to the one you propose? If so, reference and very briefly explain them.
- Are there are possible improvements to current solutions?
What in general will this project achieve? (Do not delve into details or timelines.)
What to Include in a Project Scope Statement
A good Scope Statement includes the following information:
- Justification: A brief statement regarding the business need your project addresses. (A more detailed discussion of the justification for the project appears in the project charter.)
- Product scope description: The characteristics of the products, services, and/or results your project will produce.
- Acceptance criteria: The conditions that must be met before project deliverables are accepted.
- Deliverables: The products, services, and/or results your project will produce (also referred to as objectives).
- Project Exclusions: Statements about what the project will not accomplish or produce.
- Constraints: Restrictions that limit what you can achieve, how and when you can achieve it, and how much achieving it can cost.
- Assumptions: Statements about how you will address uncertain information as you conceive, plan, and perform your project.
- You and your team commit to producing certain results.Your project’s requesters commit that they’ll consider your project 100 percent successful if you produce these results.
- You and your team identify all restrictions regarding your approach to the work and the resources you need to support your work.Your project’s requesters agree that there are no restrictions other than the ones you’ve identified and that they’ll provide you the support you declare you need.
- You and your team identify all assumptions you made when setting the terms of your Scope Statement.Your project’s requesters agree that, if any of these assumptions prove to be invalid, you may have to modify some or all of your project plans.
Reduce total cost of ownership by extending the life of older systems.
Use Terminal Services to provide a Windows 2000 desktop experience to systems that would otherwise require an upgrade.
Make it easier for users to locate and access resources on the network.
Use Microsoft® Active Directory™ to store information about all objects on the network.
Support roaming users by providing access to their documents and system information from multiple computers.
Use Roaming User Profiles to copy desktop settings and documents to a location on the network so that a user's settings and documents are available wherever the user logs on.
Critical functionalities are the functions that you would expect form the system in order to call your project a success - i.e. functions that are critical for the business. These are the functions, without which your system would be useless. This would be the core business functionalities of the application.
For example, a Student Registration is no good if you cannot register students... How good the UI is, etc, would be of no use if you cannot perform the critical functionalities...
The reason they ask for these to be specified is to check if your project is a success... In order to call you project a success, you should implement the critical functionalities, at least.
|"Scope" would include the mentioned "Critical functions" plus certain "Nice-to-have" functions... Not all of the features provided by your system would be critical (I guess)... some of the would be supporting functions. It would be Ok if you couldn't provide some of the "nice-to-haves"... but it is a must to provide critical features!|
For example, in case of the Student Registration system, printing of Student IDs might not be a a critical feature, but still it could be provided by the application. And even reports... some reports are "must-haves" while others would be an added advantage. Of course, what is critical would come from the domain plus the client requirement... Things that seem critical for one client might not be that critical for another client...
Itemized list of deliverables of the system with respect to the functionality of the system (not dissertation, CD, software etc.) user and management reports.
WEB based system module.
Eg - Standalone Payroll and Employee Database module.
System Reports and charts
The products, services, and/or results your project will produce (also referred to as objectives).
|Level||WBS Code||Element Name|
|1||1||Widget Management System|
|3||1.1.1||Evaluation & Recommendations|
|3||1.1.2||Develop Project Charter|
|3||1.1.3||Deliverable: Submit Project Charter|
|3||1.1.4||Project Sponsor Reviews Project Charter|
|3||1.1.5||Project Charter Signed/Approved|
|3||1.2.1||Create Preliminary Scope Statement|
|3||1.2.2||Determine Project Team|
|3||1.2.3||Project Team Kickoff Meeting|
|3||1.2.4||Develop Project Plan|
|3||1.2.5||Submit Project Plan|
|3||1.2.6||Milestone: Project Plan Approval|
|3||1.3.1||Project Kickoff Meeting|
|3||1.3.2||Verify & Validate User Requirements|
|3||1.3.5||Install Development System|
|3||1.3.7||Install Live System|
|3||1.4.2||Project Status Meetings|
|3||1.4.4||Update Project Management Plan|
|3||1.5.2||Document Lessons Learned|
|3||1.5.4||Gain Formal Acceptance|
|Level 1||Level 2||Level 3|
|1 Widget Management System||1.1 Initiation||1.1.1 Evaluation & Recommendations|
1.1.2 Develop Project Charter
1.1.3 Deliverable: Submit Project Charter
1.1.4 Project Sponsor Reviews Project Charter
1.1.5 Project Charter Signed/Approved
|1.2 Planning||1.2.1 Create Preliminary Scope Statement|
1.2.2 Determine Project Team
1.2.3 Project Team Kickoff Meeting
1.2.4 Develop Project Plan
1.2.5 Submit Project Plan
1.2.6 Milestone: Project Plan Approval
|1.3 Execution||1.3.1 Project Kickoff Meeting|
1.3.2 Verify & Validate User Requirements
1.3.3 Design System
1.3.4 Procure Hardware/Software
1.3.5 Install Development System
1.3.6 Testing Phase
1.3.7 Install Live System
1.3.8 User Training
1.3.9 Go Live
|1.4 Control||1.4.1 Project Management|
1.4.2 Project Status Meetings
1.4.3 Risk Management
1.4.4 Update Project Management Plan
|1.5 Closeout||1.5.1 Audit Procurement|
1.5.2 Document Lessons Learned
1.5.3 Update Files/Records
1.5.4 Gain Formal Acceptance
1.5.5 Archive Files/Documents
Tree Structure View
|Level||WBS Code||WBS Code||Definition|
|1||1||Widget Management System||All work to implement a new widget management system.|
|2||1.1||Initiation||The work to initiate the project.|
|3||1.1.1||Evaluation & Recommendations||Working group to evaluate solution sets and make recommendations.|
|3||1.1.2||Develop Project Charter||Project Manager to develop the Project Charter.|
|3||1.1.3||Deliverable: Submit Project Charter||Project Charter is delivered to the Project Sponsor.|
|3||1.1.4||Project Sponsor Reviews Project Charter||Project sponsor reviews the Project Charter.|
|3||1.1.5||Project Charter Signed/Approved||The Project Sponsor signs the Project Charter which authorizes the Project Manager to move to the Planning Process.|
|2||1.2||Planning||The work for the planning process for the project.|
|3||1.2.1||Create Preliminary Scope Statement||Project Manager creates a Preliminary Scope Statement.|
|3||1.2.2||Determine Project Team||The Project Manager determines the project team and requests the resources.|
|3||1.2.3||Project Team Kickoff Meeting||The planning process is officially started with a project kickoff meeting which includes the Project Manager, Project Team and Project Sponsor (optional).|
|3||1.2.4||Develop Project Plan||Under the direction of the Project Manager the team develops the project plan.|
|3||1.2.5||Submit Project Plan||Project Manager submits the project plan for approval.|
|3||1.2.6||Milestone: Project Plan Approval||The project plan is approved and the Project Manager has permission to proceed to execute the project according to the project plan.|
|2||1.3||Execution||Work involved to execute the project.|
|3||1.3.1||Project Kickoff Meeting||Project Manager conducts a formal kick off meeting with the project team, project stakeholders and project sponsor.|
|3||1.3.2||Verify & Validate User Requirements||The original user requirements is reviewed by the project manager and team, then validated with the users/stakeholders. This is where additional clarification may be needed.|
|3||1.3.3||Design System||The technical resources design the new widget management system.|
|3||1.3.4||Procure Hardware/Software||The procurement of all hardware, software and facility needs for the project.|
|3||1.3.5||Install Development System||Team installs a development system for testing and customizations of user interfaces.|
|3||1.3.6||Testing Phase||The system is tested with a select set of users.|
|3||1.3.7||Install Live System||The actual system is installed and configured.|
|3||1.3.8||User Training||All users are provided with a four hours training class. Additionally, managers are provided with an additional two hours class to cover advanced reporting.|
|3||1.3.9||Go Live||System goes live with all users.|
|2||1.4||Control||The work involved for the control process of the project.|
|3||1.4.1||Project Management||Overall project management for the project.|
|3||1.4.2||Project Status Meetings||Weekly team status meetings.|
|3||1.4.3||Risk Management||Risk management efforts as defined in the Risk Management Plan.|
|3||1.4.4||Update Project Management Plan||Project Manager updates the Project Management Plan as the project progresses.|
|2||1.5||Closeout||The work to close-out the project.|
|3||1.5.1||Audit Procurement||An audit of all hardware and software procured for the project, ensures that all procured products are accounted for and in the asset management system.|
|3||1.5.2||Document Lessons Learned||Project Manager along with the project team performs a lessons learned meeting and documents the lessons learned for the project.|
|3||1.5.3||Update Files/Records||All files and records are updated to reflect the widget management system.|
|3||1.5.4||Gain Formal Acceptance||The Project Sponsor formally accepts the project by signing the acceptance document included in the project plan.|
|3||1.5.5||Archive Files/Documents||All project related files and documents are formally archived.|
Project Professional 2013 installation requirements
Computer and Processor
1 GHz or faster x86/x64 processor with SSE2 instruction set
2 GB available
Graphics hardware acceleration requires DirectX10 graphics card
Visual Reports requirements
Proposed way of evaluating the success of your system:
FINAL YEAR PROJECT (IT6104)