Anda di halaman 1dari 6

Preliminary Project Scope Statement Template

Preliminary Project Scope Statement


[Proyek Belaja MPTI C]
06-10-2016

[Company Name]
Address
City, State Zip

Contents
1.

Project Description............................................................................................ 3

2.

Project Purpose................................................................................................. 3

3.

Project Objectives............................................................................................. 3

4.

Project Requirements........................................................................................ 3

5.

Project Assumptions.......................................................................................... 3

6.

Project Constraints............................................................................................ 4

7.

Project Boundaries............................................................................................ 4

8.

Project Risks...................................................................................................... 4

9.

Project Deliverables.......................................................................................... 4

10.

Project Milestones.......................................................................................... 5

11.

Project High Level Work Breakdown Structure (WBS)....................................5

12.

Rough Order of Magnitude (ROM) Estimate...................................................5

13.

Authorization................................................................................................. 6

Note: Select all (ctrl + A) and hit the "F9" key to update all document references and the table of
contents

Preliminary Project Scope Statement Template


http://www.pmdocuments.com

1. Project Description
Proyek ini merupakan proyek pembelajaran mata kuliah manajemen proyek tekologi informasi kelas A
tahun pembelajaran 2016/2017 yang ada di jurusan Sistem Infromasi, Fakultas Teknologi Informasi ITS.
Proyek ini dapat dicapai ketika sudah melewati milestone yang ada. Proyek belajar MPTI ini dibuat
dengan latar belakang perlunya manajemen proyek dalam belajar MPTI, serta menjadi bahan ajar untuk
kita memahami bagaimana membuat dokumen dokumen proyek dengan secara langsung mengalami
proyek tersebut.

2. Project Purpose
Tujuan utama dari proyek ini adalah membuat mahasiswa dapat lulus dan memahami mata kuliah MPTI
terkait perencanaan,pelaksanaan dan pengendalian suatu proyek TI. Selain itu tujuan adanya proyek ini
juga, mahasiswa menjadi lebih aware dan siap dalam memahami mata kuliah MPTI dengan cara
menyusun strategi dan dengan fasilitas kerangka best practice dan tools yang ada.

3. Project Objectives

Dapat lulus mata kuliah MPTI ini degan nilai yang baik (minimal AB)
Memahami dan mendapat pengalaman dalam mengelola proyek dengan diukur daru nilai tiap
quiz baik (diatas 7.00) serta pengumpulan dokumen pembelajaran.
Menguasai tools dan metode kerangka kerja lewat presentasi dan praktek.

4. Project Requirements
Agar tujuan proyek diatas dapat tercpai, terdapat beberapa kebutuhan kebutuhan yang harus dipenuhi
yaitu:

Adanya materi dalam tiap pertemuan


Terdapat fasilitas sarana dan prasarana seperti proyektor, papan tulis, spidol dll dalam proses
belajar mengajar.
Membutuhkan media pengumpulan dan sharing materi serta laptop dalam pengerjaan tugas yang
mendukung peningkatan pemahaman mahasiswa.
Adanya stakeholder seperti dosen, teman kelas dll untuk diskusi dan pemahaman materi.
Adanya peer review untuk menambah pemahaman siswa, sharing ilmu agar kualitas output
product nya semakin baik.

5. Project Assumptions
Asumsi disini adalah kondisi pada awal proyek yang harus diperhatikan, yaitu:

Proyek dimulai saat memulai melakukan frs di semester 5 dan akan berjalan hingg 16 minggu
perkuliahan
Asumsi jika anggaran proyek didapatkan dari uang bulanan yang bukan untuk konsumsi sehhari
hari.
Anggaran yang dikeluarkan sebesar maksimal Rp 250.000 selama satu semester (16 minggu)
3

Preliminary Project Scope Statement Template

http://www.pmdocuments.com
Assumptions are conditions at the start of the project that must be considered. For example,
when developing the new software system that is going to take 3 years to fully complete, an
assumption could be that the project budget is approved each year for three years so that the
project scope is not impacted.

6. Project Constraints
Constraints are situations or events on the ground that must be considered and accounted, for which the
project has no control over. For example, a constraint can be a hard deadline or completion date. Other
constraints could be resources, tools or hardware -- so that if the project has no budget for additional
servers, then the project must find a way to develop the new system using the hardware already in place.
This could mean juggling servers to fit specific development environment needs while ensuring that the
production environment stays up.

7. Project Boundaries
If the product or system boundary is known, describe it here. For example, if a system requires access to
multiple external systems (e.g., a system of systems), then it might make sense to break the scope of work
into multiple phases so that the scope of the first phase of development would be to only develop the core
functionality. A later phase would integrate the remaining functions. In this scenario, you essentially
could have two projects. Therefore, clearly defining the project boundaries helps set the scope of work
that is to be accomplished.
An example of a system boundary concept is:

The online store will integrate with the shopping cart and credit card purchasing modules for the
initial release. The second release will contain social media integration modules.

Dont be afraid to use architecture diagrams here if it helps visually clarify a system boundary. The figure
below is one of a multitude of types of system diagrams.

8. Project Risks
State the known risks. These risks are generally at a high level since not much is known about the details
of the project yet. If a Benefit-Cost Analysis was performed, then risks identified during the Benefit Cost
Analysis should be placed here. For example, if the project is going to span 5 years and touch multiple
third party systems, then integration and technology change would be risks to consider here. For
examples on how to write a risk statement, visit http://www.pmdocuments.com/category/riskmanagement/

Preliminary Project Scope Statement Template


http://www.pmdocuments.com

9. Project Deliverables

Dokumen pembelajaran tiap minggu sebagai bentuk pemahama materi sebelum kuliah.
Dokumen dokumen dari 10 knowledge Area yaitu Project Integration Management
Plan, Scope Management Plan, Time Management Plan, Quality
Management Plan, Human Resource Management Plan, Communication
Management Plan, Risk Management Plan, Procurement Management
Plan, dan Stakeholder Management Plan
Review dokumen 10 kowledge area tersebut.
Laporan Final

10.

Project Milestones

Identify the project milestones.


Milestone Date
[Jan 1]

Milestone Name
System Requirements
Complete

[June 1]

Development Complete

[Dec 1]

Deployed to Production

11.

Milestone Description
System requirements version 1.0 are approved and
baselined so that the project can begin design and
development.
Software development is complete and ready for
integration testing
System passes integration and end-user acceptance
testing and is deployed to production

Project High Level Work Breakdown Structure (WBS)

If you have decomposed the high level work that needs to be done, then provide the high level work
breakdown structure (WBS) here. A high level WBS is sometimes referred to as a Rough Order of
Magnitude WBS, or ROM WBS. (For more information on WBS development, visit
http://www.pmdocuments.com)

12.

Rough Order of Magnitude (ROM) Estimate

Provide ROM estimate information here. If the work has been decomposed and a ROM estimate
calculated, then provide the information here. (For more information on ROM estimate development, visit
http://www.pmdocuments.com)
Activity
Define Requirements and Design
Develop Product
Test Product
Deploy Product

Estimated Time
100-150 Resource Hours
200-400 Resource Hours
100-150 Resource Hours
100-150 Resource Hours
5

Preliminary Project Scope Statement Template


http://www.pmdocuments.com

13.

Authorization

If approval is required, provide the names of those business sponsors that must sign the Preliminary
Project Scope Statement.

Approved by the Project Sponsor:


___________________________________________
[Project Sponsor]

Date:____________________

[Project Sponsor Title], [Project Sponsor Organization or Division]

Note: Add other signatories as needed