Partial Project Planning

8/2/2019 Partial Project Planning

1/36

Project Management Plan Template

This document is an annotated outline for a Project Management Plan, adapted

from the PMI Project Management Body of Knowledge (PMBOK) and IEEE

Standard for Project Management Plans. The Project Management Plan is

considered to be a Best Practice template by the ETS Enterprise Program

Management Office (EPMO).

The template is designed to address items for all sizes of projects. For small

projects, it may be appropriate to omit sections. For unique projects, you may

need to add sections.

Tailor as appropriate. Where you decide to omit a section, you might keep the

header, but insert a comment saying why you omitted the element. A suggestedmethod is to leave the header and place the comment Not Applicable. This

demonstrates you have thought through the project.

Items in italic redtext should be removed and replaced with your project wording. The

items in italic redare remarks designed to explain and give guidance on what should be

in that section. If you have a document already addressing a section, reference that

document and where that document resides.

Note 1: The Project Management Plan guidelines were derived and developed fromIEEE Standard 1058.1 Standard for Project Management Plans (ANSI) and the PMI

Project Management Body of Knowledge (PMBOK).

Note 2: The ordering of Project Management Plan elements is not meant to imply that

the sections or subsections must be developed or presented in that order. The order of

presentation is intended for ease of use, not as a guide to preparing the various elements

of the Project Management Plan.


2/36


3/36

Project Title here

Project Management Plan

Document History and Distribution

1. Revision History

Revision #

RevisionDate

Description of Change Author

1.0 99/99/9999 Initial Document Author name

2. Distribution

Recipient Name Recipient Organization Distribution Method

3. Plan Approvers

Identify the plan approvers. List the name, signature and date theplan was approved.

Approver Name Approver Signature ApprovalDate

Approval GroupRepresented

Jerian R. Peren


4/36

Project Title here


Approver Name Approver Signature ApprovalDate

Approval GroupRepresented

Group leadersName

Table of ContentsProject Deliverables ......................................................................................................................1

....................................................................................................................................................... 1

Project Management Plan Updates ..............................................................................................3Project Organization .........................................................................................................................4

Organizational Structure ...............................................................................................................4

Organizational Boundaries and Interfaces ...................................................................................4Roles & Responsibilities ..............................................................................................................4

......................................................................................................................................................... 5

PROJECT ROLE ..............................................................................................................................5DESCRIPTION ................................................................................................................................5

Group Resource/ Assigned Member ................................................................................................5

Dependencies ....................................................................................................................................5

.......................................................................................................................................................... 5

.......................................................................................................................................................... 5

Management Process ........................................................................................................................5

Assumptions, Dependencies, and Constraints ............................................................................5Risk Management ........................................................................................................................6

Communication Plan ...................................................................................................................7

Efficient communication means that we are providing the information that is needed, andnothing more. Effective communication means that we are providing information on the right

format, at the right time, and with the right impact.....................................................................7

....................................................................................................................................................... 7Technical Process .............................................................................................................................7

Methods, Tools, and Techniques ................................................................................................7

Architecture Plan ..........................................................................................................................7

Software Documentation .............................................................................................................7Hardware Documentation .............................................................................................................8

Security .........................................................................................................................................8

Project Support Functions ...........................................................................................................8Work Packages, Schedules, and Budget ........................................................................................10

Work Packages ...........................................................................................................................10

Dependencies ..............................................................................................................................11Resource Requirements ..............................................................................................................11

Budget Requirements .................................................................................................................12

Budget and Resource Allocation ................................................................................................12

Schedule ......................................................................................................................................12


5/36

Project Title here


Earned Value Analysis ...............................................................................................................12..................................................................................................................................................... 14

Project Success Criteria ..................................................................................................................14 Network Diagram .......................................................................................................................14Project Milestones ......................................................................................................................14

Data Conversion / Data Migration .................................................................................................14

Test Strategy ...................................................................................................................................14

Unit Testing ................................................................................................................................15Functional Testing ......................................................................................................................15

System Testing ...........................................................................................................................15

User Acceptance Testing ............................................................................................................15Performance / Scalability Testing ..............................................................................................15

Data Verification ........................................................................................................................15

Deployment Plan ............................................................................................................................15System Transition / Rollout Plan ....................................................................................................15

Training Plans .................................................................................................................................15

Procurement Plans ..........................................................................................................................15

Maintenance & Support Plans ........................................................................................................15........................................................................................................................................................ 17


6/36

Project Title here


Group Name

1. Project Overview

The system we are proposing is about online ordering system of Mille Flower Shop.

This kind of system will help the customers in buying flowers for their loved ones. We are

selling flowers in different occasions like marriage, valentines and funerals. Flowers can be

brought per piece or bouquets.

Scope

This is a new website for the Mille Flower Shop.

We have a log-in account for the users.

Verification of the users password through their E-mail.

It has an Admin Page that connects the admin to the users.

Out of Scope

This system doesnt have connections with the other flower shops.

The payment system will only accept Pesos currency.

Project Deliverables

Below is a list of artifacts to be delivered to the customer

ARTIFACT Yes /

No

Agency Systems Development Life Cycle Methodology

(SDLC)

Yes

Project Management Plan | 15


7/36

Project Title here


Group Name

ARTIFACT Yes /

NoApplication Technical Architecture

Budget

Build vs. Buy Analysis for Software

Business Case

Business Functional Requirements

Change Control Process

Communication Plan YesConfiguration Management Plan

Critical Success Factors

Deliverable Acceptance Criteria

Disaster Recovery / Business Continuity Plan

Hardware Procurement List

Issue Log

Lessons Learned

Maintenance & Support Plan

Organizational Breakdown Structure

Performance / Scalability Test Plan

Practices & Techniques

Project Charter

Project Management Plan Yes

Project Milestones Yes

Project Schedule Yes

Project Success Measurements

Project Test Plan

Quality Assurance Plan Yes



8/36

Project Title here


Group Name

ARTIFACT Yes /

NoRegression Test Plan

Risk Assessment / Profile

Roles & Responsibilities Yes

Security Architecture

Service level Agreements

Software Deployment Plan Yes

Software Procurement List

Software User Documentation

Software Verification & Validation Plan

SOW (Statement of Work)

Staffing Plan

Task Estimates

Training Plan Yes

UAT Test Plan

Unit Test Plan

Work Breakdown Structure (WBS)

Project Management Plan Updates

The Project Management Plan will be created and maintained using

standard version control processes. Page3 of this document outlines theDocument History, Distribution List, and Plan Approvers.



9/36

Project Title here


Group Name

Project OrganizationDescribes the project organizational structure, identifiesorganizational boundaries and interfaces, and definesindividual responsibilities for the various project elements.

Organizational Structure

Describes the internal management structure of theproject. Graphical devices such as hierarchicalorganization charts or matrix diagrams may be used to

depict the lines of authority, responsibility, and lines ofcommunications within the project. Show anorganizational chart for each agency, team, orconsultants involved with the project.

Organizational Boundaries and Interfaces

If your project involves more than one team, anotheragency, or consultants it is important to describe theboundaries of each of those organizations. The

establishment of boundaries early in the project will giveguidance to all teams working on the project andpromote clear communication.

Describe the administrative and managerial boundariesbetween the project and the following entities: theagency, the custom organization, subcontractedorganizations, quality assurance, or any otherorganizational entity interfacing with the project.

Roles & Responsibilities

Briefly describes the responsibilities of project teammembers. A matrix of functions and activities versusresponsible individuals may be used to depict projectresponsibilities. An example of the Roles &Responsibilities template is listed below.



10/36

Project Title here


Group Name

In order to effectively enable each member of the group that will be apart of the overallXXX Project, roles and responsibilities are clearlydefined and are as follows:

PROJECT

ROLE

DESCRIPTION

GroupResource/AssignedMember

Dependencies

Management Process

This section describes project assumptions, dependencies, and

constraints, risk management techniques, monitoring and

control practices, staffing plan, communication plan, and

escalation procedures.

Assumptions, Dependencies, and Constraints

This section will state the assumptions on which the



11/36

Project Title here


Group Name

project is based, the external events the project is

dependent upon, and the constraints under which the

project is to be conducted.

Assumptions

Millefiori Flower Shop makes it easy for you to order and send

you flowers anywhere else in the Philippines using our

website.

Dependencies

Each member has its own roles and responsibilities in order

to successfully accomplish task.

Constraints

Our system has Database as well as security.

Risk Management

There are significant technical difficulties in building a web

site. It will be a risk because one person on our team has much

experience with the relevant tools and technologies. Although the

others will learn, we will certainly, make some mistakes and

suboptimal choices and addressing this risk by scoping the project by

having enough time to train and to review the design and

implementation. The schedule for this project depends on its

development. We will manage this by planning a conservatively



12/36

Project Title here


Group Name

scoped functional core and series of functional enhancements that can

be individually slipped to later releases if needed.

Communication Plan

Efficient communication means that we are providing the information

that is needed, and nothing more. Effective communication

means that we are providing information on the right format, at

the right time, and with the right impact.

Technical Process

Describes the technical methods, tools, and techniques to be used on

the project. In addition, the plan for software documentation shall be

specified, and plans for project support functions such as quality

assurance, configuration management, and verification and validation

shall be identified.

Methods, Tools, and Techniques

The following tools/methods we used for developing the system

are Php with MYSQL(xampp), HTML, CSS , Javascript , JQuery

Plugins , Dreamweaver for checking of errors

Architecture Plan

This figure can be seen on the Appendices section (Figure 4.0)

Software Documentation

The system will run on Windows Xp and newer OS version of



13/36

Project Title here


Group Name

Microsoft Windows . It is suited the needs of the needs and

requirements of the user.

Hardware Documentation

The system needs a computer with minimum specification of

Pentium 4 3.0ghz, 2 gb ddr2 of ram, nvidia 7000/ati 4000 series

up for smooth flash playing and has a internet connection.

Security

Our system has a login page and secured by a password and

only authorized personnel can run the system

Project Support Functions

This Figure can be seen on Appendices section(Figure 5.0)



14/36


15/36

Project Title here


Group Name

Work Packages, Schedules, and Budget

Work Packages

This System has admin for editing products, for viewing the

transactions, customers list and inventory. And users page for

the customers for viewing and purchasing products of thecompany.


Flower Shop Online

Ordering System

Admin Page

Products Page

Users Page

InventoryTransactionCustomers

ListPayment


16/36

Project Title here


Group Name

Dependencies

This system requires user registration for security purpose.

Unregistered users cant buy or pay the products that they want

but they can browse products and view its descriptions. When

the user has already registered and after choosing products it

will be proceed to payment.

Resource Requirements

The development of this system is composed of 8 members

consist of project manager, programmer, and other members.

Computer Unit, Notepad++, Xampp, and etc are the resources

used to this system.



17/36

Project Title here


Group Name

Budget Requirements

The estimated total budget for the completion of the system isnot more than 5,000php. It is for the resources, for the

webhosting and also for the food and travel expenses every

meeting.

Budget and Resource Allocation

Not applicable.

Schedule

Every weekends or free time, we have conducted group

meetings and even online meetings to discuss about our project.

Because of this meetings, we able to accomplish each task and

modules of every member and all of the functionalities and

activities in the project.

Earned Value Analysis

UNG TABLE NG EARNED VALUE ANALYSIS.(pre,palagaynlngsa appendixes)

TASK PLANMINUT

ES

PLANNED VALUE EARD

VAL

E

UNIT COMMULATIVE

PLAN ACTUAL

PLANNING

REQUIREMEN

TSAND

DESIGN

3 5.88% 5.88% Week1 Week1 5.88

SCOPE 90 2.94% 8.82% Week 1 Week 2 2.94

PRODUCT

FEATURES

60 1.96% 10.78% Week 1 Week 2 1.96

USER 60 0.98% 12.74% Week 1 Week 3 0.98



18/36

Project Title here


Group Name

PROFILE

OPERATING

ENVIRONMENT

30 1.96% 13.72% Week 2 Week 3 1.96

DESIGN/IMP.

CONSTRAIN

T

60 1.96% 15.68% Week 2 Week 4 1.96

ASSUMPTIO

NS

60 1.96% 17.64% Week 2 Week 4 1.96

FUNCTIONA

L

REQUIREMENTS

420 13.73

%

31.37% Week 3 Week 5 13.7

UIREQUIREME

NTS

90 2.94% 34.31% Week 3 Week 4 2.94

USE CASES 300 9.80% 44.11% Week 3 Week 5 9.80

ARCHITECT

URALSTRATEGIES

150 4.90% 49.01% Week 4 Week 4 4.90

IMPLEMENTATION

DLDMODULE X

150 4.90% 53.91% Week 4 Week4 4.90

DLDMODULE Y

150 4.90% 58.81% Week 4 Week 5 4.90

DLDMODULE Z

120 3.92% 62.73% Week 4 Week 5 3.92

MODULE X 180 5.88% 68.61% Week 5 Week 6 5.88

MODULE Y 180 5.88% 74.49% Week 5 Week 6 5.88

MODULE Z 150 4.90% 79.39% Week 5 Week 6 4.90

TESTING UNIT

TESTING XUNIT

TESTING Y

UNITTESTING Z

240 7.94% 87.33% Week 6 Week 7 7.94

150 4.90% 92.25% Week 6 Week 7 4.90

120 3.92% 96.15% Week 6 Week 7 3.92

INT/SYSTEM 120 3.92% 100% Week 7 Week 7 3.92TOTAL 3060 100% 100%



19/36

Project Title here


Group Name

Project Success CriteriaThis section describes the project milestones and checkpoints,key deliverables, acceptance criteria, and managementapproval process for project and product deliverables.

Network Diagram

This subsection will define the project network diagram,including the critical path. The network diagram may be

included as an Appendix.

Project Milestones

This section will identify the project milestones. Amilestone is a clearly identifiable point in time thatsummarizes the completion of a related or important setof tasks (e.g., design, testing). Milestones are commonlyused as a reference point or summary of importantevents in a project.

Data Conversion / Data MigrationThis section will describe how data will be converted ormigrated to production prior to the application being deployedinto production.

Test StrategyThis section will describe how Unit Testing, Functional Testing,System Testing, User Acceptance Testing, Regression Testing,and Performance / Scalability Testing will be accomplished.The test strategy should also include Data Verification.



20/36

Project Title here


Group Name

Unit Testing

Functional TestingSystem Testing

User Acceptance Testing

Performance / Scalability Testing

Data Verification

Deployment Plan

We have planned to create Online Ordering System (Flower Shop) forthe customers that dont have enough time to go at some flower shopsand buy flowers.

System Transition / Rollout PlanThis section will describe the knowledge transfer needed forsoftware components, hardware components, and transitionknowledge from developer to maintenance support.

Training PlansThis section will describe training plans for the client

Procurement Plans

This section is not applicable in our system.

Maintenance & Support PlansThis system can be maintained by using this program and findingwhat things needs to be revised and as time passes by it can alsobe improved.



21/36

Project Title here


Group Name



22/36

Project Title here


Group Name

A

Acceptance Criteria The list of requirements that must be satisfied prior tothe customer accepting delivery of the product.

Acceptance Test Formal user performed testing performed prior to acceptingthe system (sometimes called client acceptance test or user acceptance test).

Acquisition Generic term for hardware, software, or services acquired froman outside vendor or contractor.

Action Plan - A plan that describes what needs to be done and when it needs to

be completed. Project Management Plans are action plans.

Activity- A specific project task, or group of tasks, that require resources andtime to complete.

Adaptive System Describes software that has flexibility as the primarydesign point.

Application Generic term for a program, or system, that handles a specificbusiness function.

Application Software A complete, self-contained program that can perform

work for a user. This is in contrast to system software such as an operatingsystem, server processes, and libraries that exist in support of applicationsoftware.

Approval Cycle Process of gaining funding and management approval prior toproject initiation.

Architecture Imposes order and makes interconnections possible. Generallydefined as an intermediate step between initial requirements and businessfunctional specifications during which the entire complex of hardware, software,and design considerations are viewed as a whole. Refers to a blueprint forevolving a technical infrastructure.

Assessment A general term for the formal management review of a process.

Audit - A formal and detailed examination of the progress, costs, operations,results, or some other aspect of a project or system performed by anindependent party.



23/36

Project Title here


Group Name

AvailabilityThe portion of time that a system that is scheduled to operateactually can be used as expected.

Glossary of Terms* (continued)

B

Backbone A high-speed computer network designed to interconnect lower-speed networks or clusters of dispersed user devices.

Baseline A specification, or product, that has been formally agreed uponwhich serves as the starting point against which progress will be judged.

Baseline Plan - The initial approved plan to which deviations will be compared

as the project proceeds. A work product that has been formally approved andthat can be changed only through formal change control procedures.

Batch A term describing a method of operating computers. This method takesgroups of transactions, executes them, and returns the results, all withouthuman intervention.

Bench Mark A standard figure of merit which measurements or comparisonsmay be made.

Bridge Devices that connect two separate networks. Once bridging isaccomplished, the bridge makes interconnected networks look like a single

network.

Budget A planned sequence of expenditures over time with costs assigned tospecific tasks and activities.

C

CASE Computer Aided Software Engineering - Systems that attempt toautomate some or all of the tasks involved in managing, designing, developing,and maintaining software systems.

Change Management The formal process of recording, analyzing,

estimating, tracking and reporting of changes to the project baseline businessfunctional requirements.

Checkpoint A point in the development process at which project state, status,and results are checked, recorded, and measured.



24/36

Project Title here


Group Name

Client/Server System Primarily a relationship between processes running onseparate machines. A client initiates the dialog by sending requests to theserver asking for information or action.

Confidence Level- A level of confidence, stated as a percentage, for a budgetor schedule estimate. The higher the confidence level, the lower the risk.

Configuration Management Methodical storage and recording of allsoftware components and deliverables during development.

Connectivity Refers to the ability to send and receive information betweenlocations, devices, and business services.


Contingency Plan - An alternative for action if the project does not proceedaccording to plan or if the expected results are not achieved.

Control- A process for assuring that reality, or actual performance, meetsexpectations or plans.

Cooperative Processing Computing that requires two or more distinctprocessors to complete a single transaction.

Cost / Benefit Analysis A formal study in which the development, execution,and maintenance costs for a project are matched against the anticipated valueof the product.

Critical Activity- A task, activity, or event that, if delayed, will delay anotherimportant event - probably the completion of the project or a major milestone inthe project.

Critical Path Derived from the PERT method, this term implies the set ofactivities that must be completed in sequence and on time if the entire project isto be completed on time. A missed task on the critical path will cause a productdelivery delay. This is the longest time for the project from beginning to end.

Critical Path Method (CPM) - One of the two most common forms ofnetworking systems. CPM uses a one-time estimate for creating a projectschedule.

Customer- The individual or organization that specifies and accepts the projectdeliverables.



25/36

Project Title here


Group Name

D

Data Describes the numbers, text, graphics, images, and voice stored in aform that can be used by a computer.

Data Warehouse Where you consolidate and store data from many sources.

Deliverable A tangible, physical object that is the output of a softwaredevelopment task.

Dependency Diagram - Another name for a network or precedence diagramthat shows the dependencies among tasks.

Design The tasks associated with specifying and sketching the features andfunctions of a new application prior to coding.

Development Project The sum of all tasks and activities necessary to build asoftware product.

Document of Understanding A formal agreement between two parties. Acontract that is sometimes referred to as a Statement of Work (SOW).


Documentation The printed and displayed materials that explain an

application to a user.

Duration - The period of time over which a task takes place. Durationestablishes the schedule for a project.

E

Effectiveness - A measure of the quality of attainment in meeting objectives.

Efficiency- A measure of the volume of output received for the input used.

Effort - The amount of work or labor (in hours or workdays) required to

complete a task.

Environment The set of tools and physical surroundings in which software isdeveloped.

EPMO EnterpriseProject Management Office.



26/36

Project Title here


Group Name

Estimate A predicted total of expenditures required to complete a task,activity, or project.

Exit Criteria The set of conditions that must be met prior to completing aproject phase or application.

F

Feasibility Project A project designed to prove, or disprove, theappropriateness of the technology solution under existing constraints(sometimes called proof-of-concept project).

Float- The amount of time for a task to be freely scheduled without affectingother tasks in the project.

Function - An activity that spans the entire duration of a software project (e.g.,status reporting, quality assurance, verification and validation).

G

Gantt Chart A method of displaying overlapped and partially concurrentactivities by using horizontal lines to reflect the time required by each activity.

The chart, named for Henry Lawrence Gantt, consists of a table of project taskinformation and a bar chart that graphically displays the project schedule to beused in planning and tracking.

Gateway Hardware or software that translates between two dissimilarprotocols.

Granular Describes the art of writing small modules of code and / or objects.

Graphical User Interface (GUI) A manner of presentation that makes use ofwindows, icons, menus, pointers, and scroll bards.


H

Hardcode An informal term that describes a programming technique wheredata or procedures are specifically written into the program instructions.

Hardware Physical equipment used to process, store, or transmit computerprogram data.



27/36

Project Title here


Group Name

I

Independent Review A formal examination of a project conducted by anorganization other than the development organization.

Information The meaningful interpretation of data.

IRMC Information Resource Management Commission.

Integration Describes the work, or device, required to connect two differentsystems that were not originally designed to work together.

Integration Test Testing in which software components, hardwarecomponents, or both are combined and tested to evaluate the interactionbetween them.

Interface A connection between two devices or systems.

Interoperability The ability to have applications and computers fromdifferent vendors work together on a network.

Intranet An Internet network behind a firewall.

Issue A problem to be solved or a decision that has not been made.

J

Joint Application Design (JAD) -The combined effort of client, program, anddevelopment staff to define and elicit requirements for a system (JAR)or design a system (JAD).

KL

Lag - The amount of time after one task is started or finished before the nexttask may be started or finished.

Lead- The amount of time that precedes the start of work on another task.

Local Area Network (LAN) A communications system confined to a limitedarea, typically a building, occasionally a group, and linking computers togethervia cable.




28/36

Project Title here


Group Name

M

Maintenance Refers to the ongoing activity that keeps software functioning ina technical and business environment (production).

Methodology A set of formal protocols followed when performing a task.

Middleware Software that hides the complexity of the networked computingenvironment from the users and application programmers.

Milestone A major checkpoint in the activities involved in a project. A clearlydefined point in a project that summarized the completion of a related set oftasks.

Model- A way of looking at reality, usually for the purpose of abstracting andsimplifying it to make it understandable in a particular context.

Modular Programming Programming that has as its fundamentalassumption that a large piece of software should be separated into itsconstituent parts or modules thereby making for easier and faster developmentand maintainability. Modules were traditionally called subroutines or functionsand now are often called objects.

N

Network Describes the physical hardware and software connections between

computers allowing information to be shared and electronic communications totake place.

Network Diagram - The logical representation of tasks that defines thesequence of work in a project.

N-tier Architecture Describes a method for dividing an application into aseries of distinct layers to provide for ease of maintenance and flexibility.

O

Operating System System software that controls data storage, input and

output to and from the keyboard, and the execution of applications written for it.It performs base services: prioritizing work, scheduling, memory management,etc.

P

Package Acquisition The purchase, or lease, of software from an outsidesource.



29/36

Project Title here


Group Name

Padding - A standard project management tactic used to add extra time ormoney to estimates to cover for the uncertainty and risk of predicting futureproject activities.

Path - A sequence of lines and nodes in a project network.


PERT Project Evaluation and Review Technique - The PERT method usesthe concepts of milestones, activities, and slack time to calculate the criticalpath. The chart, which resembles a flow chart, depicts a box to represent eachproject task and a line connecting two boxes to represent the relationshipbetween tasks.

Phases The divisions of a software development life cycle into discrete stages(e.g., requirements, design, code, test, etc.).

Planning Project A project intended to gather, or predict, the sequence ofactivities and resources needed to complete a work effort.

Platform The hardware and support software with which a program isintended to operate.

Precedence - When one task must be completed before another task can bestarted, the first task is said to have precedence over the other.

Process The step-by-step sequence of activities (systematic approach) thatmust be carried out to complete a project.

Programming The art of writing, in a computer understandable language, aset of instructions that produces software.

Project The combined resources (people, machines, materials), processes,and activities that are dedicated to building and delivering a product to acustomer.

Project Duration - The time it takes to complete the entire project.

Project Management- The combination of systems, techniques, and peoplerequired to successfully complete a project on time and within budget.

Project Manager The senior person responsible for the entire project.



30/36

Project Title here


Group Name

Project Management Plan A formal document that describes the technicaland management approach to be followed for a project.

Project Sponsor The department customer who will authorize projectinitiation, and who will receive, accept, and use the software product or service.

Protocol A set of rules and specifications that describes how a piece ofsoftware will behave and how other pieces of software must behave in order towork with the first piece of software.

Q

Quality(Product) - Conformance to business functional requirements withdefect-free products. Quality reflects both the completeness of software or

system features and functions, and error-free operation.Glossary of Terms* (continued)

Quality(Process) Verification and validation to established policies, standards,procedures and guidelines for software development.

Quality Assurance Within the State of North Carolina, the process trackingand oversight function for monitoring project performance, adherence tocommitments, and budget requirements. Performed under the control of theOffice of Information Technology Services (ITS), Enterprise TechnologyStrategies (ETS) staff.

R

Regression Test Selective re-testing to detect errors or faults introducedduring modification of a system.

Relational Database A collection of data that is organized into tables so thatrelationships between and among data can be established.

Resource Leveling - The process of shifting resources to even out theworkload of team members.

RFP - Request for Proposal- Formal statement by a department that they are

soliciting enterprises to bid on a contract for a program, system or service .

Requirements The statement of needs by a user that triggers thedevelopment of a program, system, or project. May be called business functionalrequirements or requirement specifications.



31/36

Project Title here


Group Name

Research and Development Project A definition of a project typeessentially exploring options for developing new systems or work products.

Risk The probability that a project will experience undesirable events, whichmay create, cost overruns, schedule delays, or project cancellation. Theidentification, mitigation, tracking, and management of those elements creatingthe risk situation.

Risk Analysis - An evaluation of the feasibility or probability that the outcomeof a project will be the desired outcome.

S

Scalable A term describing an architecture or software that can handleexpansion in the use as the need arises without adversely impacting systemsmanagement and operations.

Scope - The magnitude of the effort required to complete a project.

Server A computer on a network that makes applications, print services, data,and communications available.


Slack- see float.

Software Computer programs, systems, and the associated documentationthat describes them.

SDLC - Software Development Life Cycle The period of time that beginswith the decision to develop a software product and ends when the software isdelivered.

Software Development Process The process by which user needs aretranslated into a software product.

Project Management Plan - The controlling document for managing asoftware project. The PP defines the technical and managerial project functions,activities, and tasks necessary to satisfy the requirements of a software project.



32/36

Project Title here


Group Name

Specifications General term for the wide variety of paper-based descriptionsof a program or system.

Stakeholders - People who have a personal or agency interest in the endresults of a project.

Standalone Describes a computer workstation where the computer is notconnected to any other computer on a network.

Statement of Work (SOW) - An integrated set of task descriptions, goaldescriptions, risks, and assumptions that accompany the evolving masterProject Management Plan during development.

Strategic Plan The long-range plan where the horizon is usually three to fiveyears time span.

Subcontract - Delegating tasks or sub-projects to contractors or otherorganizations.

System A linked collection of programs, or components, that perform ageneric business or technical function.

System Test The final stage of testing on a completed project (prior to clientacceptance test) when all hardware and software components are put togetherand tested as a whole.

SDLC - System Development Life Cycle - The complex of tasks anddeliverables that are organized toward developing software systems.



33/36

Project Title here


Group Name


T

Tactical Plan Specific improvements, or changes, that will be carried out in afairly short time span (usually twelve (12) months).

Task- A cohesive unit of work on a project (usually 40 to 80 hours of effort).

Task Description - A description that defines all the work required to completea project task or activity including input, output, expected results, and qualityspecifications.

Test Plan A document that describes the scope, approach, resources, and

schedule of intended test activities.

Testing The set of defect removal tasks that include execution of all, or part,of an application on a computer.

Topology The map or plan of a network.

U

Unit Test - The testing carried out personally by individual programmers ontheir own code.

V

W

Wide Area Network (WAN) A network where the computers are separatedby significant distances and telecommunications links are implemented.

Work Breakdown Structure (WBS) A formal analysis of the activities, tasks,and sub-tasks that must be accomplished to build a software project. A product

or activity oriented hierarchy tree depicting the elements of work that need tobe accomplished in order to deliver a product.

Work Package - A specification for the work to be accomplished in completingan activity or task.



34/36

Project Title here


Group Name

Work Product- Any tangible item that results from a project function, activity,or task.

Workstation Any machine with all of its installed storage, processing, andcommunications that can be either standalone or networked.



35/36

Project Title here


Group Name


X

Y

Z

* Definitions were extracted from Assessment and Control of SoftwareRisks by Capers Jones (1994); Managing Software Development Projects(Second edition) by Neal Whitten (1995); IEEE Standards Collection:Software Engineering (1997 Edition); Best Practices in IT ArchitecturePlanning and Implementation by Larry DeBoever; Essential Client/ServerSurvival Guide by Robert Orfali; and TheComplete Idiot's Guide to ProjectManagement by Sunny and Kim Baker.



36/36

Project Title here


Group Name

10. APPENDICESAppendices may be included, either directly or by reference, to

provide supporting details that could aid in the understanding of theProject Management Plan.

Appendix AMinutes of Meeting

Appendix BIssue Log Template

Appendix CWeekly Project Status Report

Documents

Partial Project Planning