project management plan

Project Management Plan

Project Management Plan It is the main guiding( 导向 ) document for the pr

oject, along with project schedule( 时间表 ). Used by three persons

Business Manager Project Leader Programmer

Project Management Plan

Software Management Plan is the key requirement of: Software Project Tracking & Oversight KPA of CMM

level 2 Software Project Planning KPA of CMM level 3 Integrated Software Management KPA of CMM

level 3 Intergroup co-ordination of CMM level 3 Software Quality Management of CMM level 4 Quantitative Process Management KPA of CMM level 4

Project Management Plan at Infosys

Has four sections( 部分 ) Project Summary( 概要 ) Project Planning Project Tracking ( 跟踪 ) Role & responsibility of Team( 队 )

Project Summary ( 概要 ) Provides a high level overview ( 总的看

法 ) of project Start date, End date , Project Objective( 目

标 ). Project leader, contact at customer end. Commitments ( 承担义务 ) to customer, Assu

mptions ( 假定 ) … Major Milestones( 里程标 ). Billing ( 演员次序 ) details, etc..

Project Planning The project planning gives output of exec

uting various project planning procedures. It specifies the life cycle of project It provides visibility ( 可见度 ) into the proj

ect for SEGP & senior management. It also specifies change management plan

Project Planning It provides information about

Estimation of Cost, Schedule & Quality. Development Environment needed Tools employed, other requirement Training required Risk management plan Milestone to be achieved

Project Tracking Involves capturing & resolving problem at

project level. It also specifies the escalation ( 使逐步上

升 ) mechanism at customer & vendor ends. It involves monitoring activities, issues, qu

ality & other aspect.

Team The project team must be properly organized to

achieve optimal performance. The team is headed by project leader(PL) The PL reports to Business Manager(BM) & to cus

tomer representative ( 代表 ) . Under PL, there may be Module Leaders & Develo

pers, Configuration Controllers, DBA A SEPG member is also associated with project

Configuration Management


A software can produce a number of Items during its life cycle: Documents Programs Data Manuals …. Etc

Any of these Items may be changed.


If the changes to the Items is not organized, It is possible to lose control over the project.

Software Configuration Management(SCM) is a systematic way of controlling the changes that occur in project.

SCM is a process to handle & implement changes to various item produced in project.


It satisfies “Software Configuration Management” KPA of CMM level 2

Configuration Management is also part of “Project Management Plan” KPA

Life cycle of item

PrivateReady for

Acceptance testing

Production

Ready forUnit Testing

Baseline

Ready forSystem testing

Defect in AT

Programmer

Satisfied

UT complete

Defect in UT

Defect in ST

ST complete

release

On successful release


From the state diagram we can conclude ( 断定 ) that, the state information has to be maintained to properly manage the evolution ( 发展 ) of the program.

In addition to changes during normal software development, Requirement change could also alter programs.

Functionality requirement of Configuration Management.

To control the change for different items in a organized manner, the configuration Management require the following functionality:

State of the program: This information is needed to decide

when to start testing or when to release the software.

Cont… Version of program:

So that modification can be carried out by the latest version of the program.

Handle concurrent update request Two programmers in response to two

different change request, might change the same program concurrently.

Cont… Undo program Change:

A change done to a program may be requires “UNDO” do to some reason.

Prevent Unauthorized changes or deletion: A programmer may do modification which

may have adverse effect.

Cont… Provide traceability between

Requirement change request and program changes: A mechanism to trace more than one

changes to requirement, so that all changed program has gone through the lifecycle & is in “ready for release state”

Cont… Undo Requirement Change:

A requirement change request that has been implemented by changing many program may be required to be UNDONE.

Show associated Change: Suppose a bug has been found due to

implementation of a requirement change, then this mechanism is used to trace all change made for the request.

Cont… Gather all source, documents, &

other information for the current system. Due to system crash or file

corruption, it may be required to recover all files & documents that represent a system.

Cont… The mechanism commonly used to

provide the necessary functionality are: Naming convention & Organization of files Version control Change request traceability Access Control Reconciliation procedure Modification log in program

Configuration Management at Infosys.

Plan & setup configuration Management

Perform Configuration control Monitor the status of configuration

items.

Plan & setup configuration Management The planning is done by Project Leader

or Configuration Control Board(CCB) The activities include:

Identify configuration items, including customer supplied & purchased items

Define a naming & numbering scheme for the configuration items

Define directory structure needed for CM

Cont… Define access restriction Define change control procedure Identify & define the responsibility &

authority for CC/CCB Define a method for tracking the

status of configuration items Define backup procedure Define reconciliation procedure

Cont… Define a release procedure Define archival procedure Identify points at which the

configuration items will be moved to baseline.