Enciso Information Systems Project Plan

piegazeInternet and Web Development

Dec 7, 2013 (3 years and 8 months ago)

72 views

<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠
1

of



Enciso Information Systems

Project Plan





Revision History

Date

Version

Description

Author

26/03/2010

0.1

First Version

Anshuman Mehta

05/04/2010

0.2

Details added for Iteration Plans

Anshuman
Mehta

07/04/2010

0.3

Review

Anshuman Mehta

01/06/2010

1.1

Updated Iteration Plans

and Objectives

Anshuman Mehta

04/06/2010

1.2

Updated risk
management plan with risk
probability and impact.

Anshuman Mehta



Contribution Control


Name

Dni

Contribution %

Description

Anshuman Mehta


100

































<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠
2

of



CONTENTS

1.

Introduction

4

1.1

Purpose and Scope

4

1.2

Definitions, Acronyms, and Abbreviations

4

1.3

References

4

2.

Project Organization

4

2.1

Organizational Structure

4

2.2

External Interfaces

4

2.3

Roles and Responsibilities

5

3.

Project Schedule

7

3.1

Project Plan

7

3.1.1

Inception ( I1)

7

3.1.2

Elaboration E1

8

3.1.3

El
aboration E2

9

3.1.4

Construction C1

10

3.1.5

Construction C2

11

3.1.6

Transition T1

12

3.1.7

Tr
ansition T2

13

3.2

Gantt charts

14

3.2.1

Inception Iteration I1

14

3.2.2

Elaboration Iteration E1

15

3.2.3

Gantt chart for Elaboration Iteration E2

16

3.2.4

Gantt chart for Construction Iteration C1

17

3.2.5

Gantt chart for Construction Iteration C2

18

3.2.6

Gantt chart for Transition Iteration T1

18

3.2.7

Gantt chart for Transition Iteration T2

19

3.3

Iteration Objectives

20

4.

Project Resourcing

21

5.

Budget

22

5.1

Effort
Estimation

22

5.1.1

Methodology

22

5.1.2

UAW : Unadjusted Actor Weight

22

5.1.3

UUCW : Unadjusted Use Case Weight

23

5.1.4

TCF : Technical Complexity Factor

24

5.1.5

ECF : Environment Complexity Factor

24

5.1.6

Effort Configuration

25

5.
1.7

UCP : Use Case Point

25

5.2

Budget Estimation

26

5.2.1

Industry Resource Costs

26

5.2.2

Iteration Estimate with Resource Utilization Estimate

26

5.2.3

Infrastructure, Deployment and Support

28

6.

Risk Management Plan

29

<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠
3

of





















































<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠
4

of



1.

Introduction

1.1

Purpose and Scope

The purpose of this Software Development Plan is to define the development activities in phases and
iterations in order to implement an Information System for
Encis
o.

The Software Development Plan gives a complete outline and plan that will be used by the
team for
developing the Information System. The details of the iteration are described in the respective Iteration
Plans.

1.2

Definitions, Acronyms, and Abbreviations

Refer to Glossary

1.3

References

0910Q2
-
11
-
I
-
1
-
0.1
-
Vision

0910Q2
-
11
-
I
-
0.1
-
Glossary

0910Q2
-
11
-
I
-
1
-
0.1
-
Use_Case_Model_USED_FOR_SAD


2.

Project Organization

2.1

Organizational Structure







2.2

External Interfaces

The project team will interact with the stakeholders mentioned in the Vision Document to solicit inputs and
review of relevant project deliverables.

<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠
5

of



Th攠m慩n po楮琠tf 捯n瑡捴tfor th攠proj散琠瑥慭 w楬氠i攠Anshum慮 䵥h瑡t th攠Proj散琠t慮慧敲 who und敲
瑨攠gu楤慮捥 and 捯nsu汴lncy of 瑨攠Prof敳eor for 瑨攠subj散琠w楬氠lu楤攠瑨攠瑥tm memb敲s 瑯w慲ds
捯mp汥l楯n 慮d 慣h楥iemen琠tf bo瑨 瑨攠busin敳s 慮d 瑥捨n
i捡氠l楳楯n of th攠produ捴c

2.3

Roles and Responsibilities


Project Team Member

Role

Rational Unified Process Skills

Anshuman Mehta

Project Manager

Project Management

Requirements

Test

Environment

Matteo De Martino

Nick Veenhof

Architect

Business Modelling

Requirements

Analysis and Design

Test

Environment

Andrea Gritti

Tomas Barton

Analyst

Requirements

Analysis and Design

Implementation

Environment


The following table maps the Activities and Responsibilities of the roles defined in Table x.y and the
Ratio
nal Unified Process Artifacts and Process outputs as defined in the current project team.


Activities

Role

Responsibilities

RUP Artifact/ Process

Conceive new Project

Project Manager

Develop Business Case

Identify and Assess Risk

Initiate Project

Business

Case

Define Requirements

Project Manager

Architect

Analyst

Develop Vision

Find Actors and Use
Cases

Develop Supplementary
Specifications

Capture Common
Vocabulary

Prioritize Use Cases

Vision

Use Case Model

Supplementary
Specification

Glossary

Software
Architecture
Document

Plan the Project

Project Manager

Acquire Staff

Assess Iteration

Software Development
Plan

<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠
6

of



Id敮瑩晹 慮d 䅳Aess
R楳ks

P污l Ph慳敳 慮d
I瑥t慴楯ns

䑥D敬ep I瑥t慴楯n P污l

I瑥t慴楯n P污l

I瑥t慴楯n Ass敳ement


Pr数慲攠偲Pj散琠
Env楲onment

Proj散琠t慮慧敲

Arch楴散i

䅮慬yst

Es瑡t汩lh Proj散琠
䵡n慧emen琠tro捥ss

T慩汯r 䑥D敬epm敮琠
Pro捥ss of Proj散t

卥汥捴S 卥S
-
up 慮d
A捱u楲攠Too汳

䵡n慧emen琠tnd
Tr慣k楮g Pro捥ss 慮d
Too汳

䑥D敬epmen琠tro捥ss

Proj散琠剥tos楴iry


























<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠
7

of



3.

Project Schedule


The development of the Enciso Information System will be carried out using a phased approach where
multiple iterations occur within a phase. The phases and iterations in this plan do not overlap.

3.1

Project Plan


A summary of the timeline i
s shown below in days and weeks.

3.1.1

Inception

( I1)








<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠
8

of



3.1.2

Elaboration E1





















<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠
9

of



3.1.3

Elaboration E2



















<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of



3.1.4

Construction

C1














<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of





3.1.5

Construction C
2


























<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of






3.1.6


Transition T1






















<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of



3.1.7


Tra
nsition T2


















<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of



3.2

Gantt chart
s


3.2.1

Inception Iteration I1














<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of



3.2.2

Elaboration Iteration E1



















<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of



3.2.3

Gantt chart for Elaboration Iteration E2



















<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of



3.2.4

Gantt chart for Construction Iteration C1

















<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of



3.2.5

Gantt chart for
Construction Iteration C2





3.2.6

Gantt chart for Transition Iteration T1







<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of



3.2.7

Gantt chart for Transition Iteration T2





















<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of



3.3

Iteration Objectives


The primary Objectives and associated deliverables
for

each
of the
it
erations
are in the table
below


Phase

Iteration

Description

Milestone

Inception Phase

I1

The Inception Phase will develop the
product requirements and establish the
business case for the system. The major
use cases will be identified and a high
level Software Development Plan
developed.

Vision

Software Development
Plan: Business Case, Risk
Li
st, Budgeting, Planning
and Estimation of Phases
and Iterations.

Business Model:
Business Processes and
Business Objects

Use Case Model
Specification.

Glossary

Elaboration Phase

E1

The Elaboration Phase will
refine

the
requirements and
analyze and design
the
most relevant use cases. An outline of a
stable system architecture and test plan
will be created.

Use Cases: Model
Specification and
Storyboards.

Analysis Model and Data
Model.

System Architecture.

Test Plan and Test Cases

E2

Detailed

system architecture will be
presented along with a detailed plan to
build the system. Optionally an
executable system, called architectural
prototype,
will test the feasibility and
performance of the architecture
.

Detailed System
Architecture.

Detailed Te
st Cases.

Design Model of main
use cases.

Prototype Architecture
(optional).

Software Development
Plan updated for
Construction Phase.

Construction Phase

C1

During the

first

Construction Phase,
remaining

key use cases will be
analyzed and
designed
. The
Beta release

will be developed and distributed for
evaluation. The implementation and test
activities to support the

B
1.0
release

will be completed.

Creation of Development
Environment

Implementation and Unit
tests for Prioritized use
cases.

Set up of Inte
grated Test
Suite.

Verification of
Deployment Architecture
<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of



慮d 卡mp汥l䑥D汯ymen琮

卯ftw慲攠䑥v敬epm敮琠
P污l upd慴敤 w楴h for
I瑥t慴楯n 2 of
Cons瑲u捴楯n Ph慳攮



Th攠s散ond Cons瑲u捴楯n Phas攠w楬氠
慮慬y穥 and d敳楧n 慬氠oth敲 r敭慩n楮g
r敱u楲em敮瑳. The

s散ond B整愠r敬敡s攠
w楬氠l攠d敶敬ep敤 慮d d楳瑲楢u瑥t for
敶慬aa瑩tn. Th攠imp汥men瑡瑩tn 慮d 瑥獴
慣瑩t楴楥s 瑯 suppor琠瑨攠B2.0 r敬敡s攠
w楬氠l攠捯mp汥瑥l.

Con瑩nuous In瑥tr慴敤
T敳瑩ng.

Bug 䙩ing

R敬敡s攠C慮d楤慴攬
䑥D汯ymen琠tnd
䙵n捴楯n慬 T敳瑩ng

䡡Hd
汩lg 䑥D汯ymen琠
Issues

Tr慮s楴楯n Ph慳a



Th攠f楲s琠
Tr慮s楴楯n Ph慳攠
w楬i f楸
d敦散瑳 慮d in捯rpor慴攠f敥dba捫. Th攠
produ捴cr敬敡s攠R1.0 wi汬⁴len b攠
p慣k慧敤 慮d d楳瑲楢u瑥t on produ捴楯n
sys瑥ms.

Imp汥men瑩ng 䙥敤b慣k

Con瑩nuous In瑥tr慴敤
T敳瑩ng

R敬敡s攠T敳瑩ng

䑯捵men瑡瑩tn 慮d
Tr慩a楮g 䵡瑥t楡i




Th攠s散ond Tr慮s楴楯n w楬氠fi d敦散瑳
from th攠produ捴cr敬敡s攠R1.0 楮 瑨e T1
ph慳攠慮d in捯rpor慴攠f楮慬afe敤b慣k.
Produ捴cR敬敡s攠R2.0 w楬氠ihen b攠
p慣k慧敤 慮d d楳瑲楢u瑥t. The r敱u楲敤
suppor琠
瑯 敮sur攠愠smoo瑨 ins瑡汬慴楯n
慮d 瑯 go 汩l攠w楬氠i攠prov楤敤.

Imp汥men瑩ng 䙥敤b慣k

Con瑩nuous In瑥tr慴敤
T敳瑩ng

R敬敡s攠T敳瑩ng

䑥D汯ymen琠tn
Produ捴楯n, 却Sg楮g and
Liv攠Env楲onmen瑳

䑯捵men瑡瑩tn 慮d
卵ppor琠t慴敲楡i

Tr慩a楮g



4.

Project Resourcing

A
s highlighted in section in 2.3 the staff already acquired for the project includes a Project Manager and
two Architects and Analysts each.

This project staff is sufficient for the first two Phases of the project

i.e.

the Inception and Elaboration
Phases. In the Construction and Transition Phase
two

programmers and two testers will be
additionally
staffed into the project.

The team will be working on and exploring the next set of web generation technologies (gwt,
drupal etc. )
therefore their previous experience of programming will be used to understand these open
-
source
technology architectures. Also the programmers that will be staffed into the project will need to have the
necessary skill set .


<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of



5.

Budget

5.1

Effort E
stimation

5.1.1

Methodology

The effort estimate for this project has been estimated using Use Case Point (UCP) estimation using Gustav
Karner’s methodology.

UCP analyzes the use case actors, scenarios and various technical and environmental factors and abstract
s
them into an equation.

The equation is composed of four variables:



Technical Complexity Factor (TCF).



Environment Complexity Factor (ECF).



Unadjusted Use Case Points (UUCP).



Productivity Factor (PF).

Each variable is defined and computed separately, usin
g perceived values and various constants. The
complete equation is:

UCP = TCP * ECF * UUCP * PF

Unadjusted Use Case Points
( UUCP)
are computed based on two computations:



The

Unadjusted Use Case Weight

(UUCW) based on the total number of activities (or st
eps)
contained in all the use case Scenarios.



The

Unadjusted Actor Weight

(UAW) based on the combined complexity of all the use cases
Actors.

5.1.2

UAW

: Unadjusted Actor Weight

In order to c
alculate the
UAW the Actors are classified as Simple, Average or Comple
x based on their
interactions (

Simple

if interaction is
via API simple, via known protocol medium , human via gui complex)

Type

Description

Simple

System through API

Medium

System through known protocol ( TCP … )

Complex

Human through GUI


Actors

Type

Weight

Event Organizers

Complex

3

Service Provider

Medium

2

Event
Participants

Medium

2

Event Manager

Medium

2







Simple

0

0

Medium

3

6

Complex

1

3


UAW

9


The above table gives the UAW associated with the actors in our system.

<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of



5.1.3

UUCW

: Unadjusted Use Case Weight

The UUCW is calculated from assigning a weight to the use cases and summing them with their associate
weights.



Direct


Indirect



Use Cases

Type (direct set)

Weight

Nº Transanctions

Type

Weight

Registration (client)

Complex

15

1

Simple

5

Feedback Rating (client)

Medium

10

1

Simple

5

Feedback Comments (client)

Medium

10

1

Simple

5

Payment (client)

Complex

15

2

Simple

5

Request a Proposal (client)

Complex

15

1

Simple

5

Modify a proposal (client)

Medium

10

2

Simple

5

Cancel a proposal (client)

Simple

5

1

Simple

5

Reservation

Complex

15

2

Simple

5

Manage Event

Complex

15

1

Simple

5

Invite People

Medium

10

1

Simple

5

Add Marketing Website

Medium

10

1

Simple

5

Apply to be a provider (provider)

Simple

5

1

Simple

5

Add service (provider)

Simple

5

1

Simple

5

Remove service (provider)

Simple

5

2

Simple

5

Modify service (provider)

Simple

5

1

Simple

5

Add service data (provider)

Complex

15

2

Simple

5

Remove service data (provider)

Simple

5

2

Simple

5

Verify providers (manager)

Medium

10

1

Simple

5

Verify service (manager)

Medium

10

1

Simple

5

Manage users

Medium

10

2

Simple

5

Manage pages and categories

Simple

5

1

Simple

5

Manage events

Medium

10

1

Simple

5

Financial reports

Complex

15

1

Simple

5





?

1

Simple

5





?

3

Simple

5

Total











Simple

7

35

Simple

25

125

Medium

9

90

Medium

0

0

Complex

7

105

Complex

0

0


UUCW

230


UUCW

125


UUCP

239


UUCP

134







<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of



5.1.4

TCF : Technical Complexity Factor


F
or each project, the technical
factors are evaluated by the development team and assigned a value from 0
to 5 according to their perceived complexity
.


Technical Factors





Factor

Description

Weight

Points (0 to 5)

TFi

T1

Distributed System

2

3

6

T2

Response Adjectives

1

4

4

T3

End

User Efficiency

1

3

3

T4

Complex Processing

1

3

3

T5

Code Must be Reusable

1

4

4

T6

Easy To Install

0.5

5

2.5

T7

Easy To Use

0.5

5

2.5

T9

Portable

2

3

6

T9

Easy To Change

1

3

3

T10

Concurrent

1

3

3

T11

Security Features

1

3

3

T12

Acces for third
parties

1

4

4

T13

Special user training facilities

1

1

1




TFactor

45




TCF

1.05



5.1.5

ECF : Environment Complexity Factor

Environmental Complexity estimates the impact on productivity that various environmental factors have on
an application. Each
environmental factor is evaluated and weighted according to its perceived impact and
assigned a value between 0 and 5. A rating of 0 means the environmental factor is irrelevant for this project;
3 is average; 5 means it has strong influence.


Environmenta
l Factors





Factor

Description

Weight

Points (0 to 5)

EFi

E1

Familiar with RUP

1.5

1

1.5

E2

Application Experience

0.5

3

1.5

E3

Object Oriented Experience

1

3

3

E4

Lead Analyst Capability

0.5

4

2

E5

Motivation

1

5

5

E6

Stable Requirements

2

4

8

E7

Part
-
time Workers

-
1

1

-
1

E8

Difficult programing language

-
1

4

-
4




EFactor

16




EF

0.92


<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of



5.1.6

Effort Configuration

We then adjust the following factors for our calculation using the suggested value by Gustav for
staffHours*UCPoints.


Effort Cfg


staffHours x
UCPoints

20

hours x working day

4

working days x
month

20

Actor Weight Cfg


Simple

1

Medium

2

Complex

3

Use Case Weight
Cfg


Simple

5

Medium

10

Complex

15

direct(yes,no)

Yes





5.1.7

UCP : Use Case Point


This gives us the following
effort estimation for the project.


Estimation

Value

UCP

230.874

Man.Hours

4617.48

Man.Day

1154.37

Man.Month

57.7185






<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of



5.2

Budget Estimation

5.2.1

Industry Resource Costs

In order to calculate the associated cost with above estimated effort, we take into
account the following
industry standard prices for our calculations and also propose the offshore advantage costs.



(all figures in
Euros)

Role

Quote

Offshore

Project
Manager

60



Architect

45



Analyst

45



Programmer

30

20

Tester

25

15


5.2.2

Iteration

Estimate with Resource Utilization Estimate

In order to estimate the price for the project we undertake the following methodology



Define the effort percentage for each of the four phases within the project and using this effort
percentage estimate
,

fetch

the effort in man hours from the total estimated effort.



For each phase then estimate the utilization of each of the proposed resources.



Using the estimated utilization of each resource and estimated effort for the phase we can fetch the
costs
for each resource
asso
ciated per phase using
5.2.1

and multiplying the effort estimate for
each resource.



We also adjust in the last two phases the costs for the offshore advantage.

















<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of



Gustav Karner Effort Estimation

4617.48

man hours


















in Euros





Iteration

Effort%

ManHours

Resource

Utilization%

Costs



Offshore
Advantage

















Inception

13

600.2724

PM

30

10804.903











Architect

35

9454.2903











Analyst

35

9454.2903











Programmer

0

0











Tester

0

0











Cost for Inception Stage

29713.4838



















Elaboration

22

1015.8456

PM

15

9142.6104











Architect

30

13713.916











Analyst

55

25142.179











Programmer

0

0











Tester

0

0











Cost for Elaboration Stage

47998.7046



















Construction

35

1616.118

PM

5

4848.354











Architect

5

3636.2655











Analyst

5

3636.2655











Programmer

65

31514.301



21009.534







Tester

20

8080.59



4848.354







Cost for Construction Stage

51715.776

37978.773

















Transition

30

1385.244

PM

5

4155.732











Architect

5

3116.799











Analyst

0

0











Programmer

55

22856.526



15237.684







Tester

35

12120.885



11428.263







Cost for Transition Stage

42249.942

33938.478





















4617.48







171677.9064

149629.4394






























<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of



5.2.3

Infrastructure, Deployment and Support


We then add the additional costs for the project i.e the office
infrastructure and deployment costs.

Also the optional support costs associated are included in the budget estimate.



(all figures in Euros)

Onshore

Offshore

Application
Development Costs



171678

149630

















Google Apps
Premier Edition

@

50 USD per user
per year ( @ 10
people in enciso )



374.5

374.5























Amazon EC2
deployment

Standard Reserved
Linux Instances

One Time payment
per year ( @ 227.5
USD per year )



170.5

170.5



















Free Support upto
2
months after
Deployment.

Addition support
@50 euro per
consultant per hour

@600 euros per
month and @ 6000
euro per year

optional

6000

6000

























172223

150175











support

178223

156175



This gives us the final estimate of

the Project with and without support and with and without the Offshore
advantage costs.

The Project cost without support on
-
shore is 172,223 Euros.







<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of




6.

Risk Management Plan


Project risk is evaluated at least once per iteration and documented in this
table. The risks of the greatest
magnitude are listed first in the table.

The values use for the Probability and Impact use a scale of 1 to 5, where 1 indicates low probability and
low impact and 5 represent high probability and high impact. Multiplying th
e probability value by the
impact value for each risk provides a Risk Magnitude which is then applied for prioritizing the risks.

Risk Description
& Impact

Probability

Impact

Risk
Magnitude

Type

Mitigation Strategy /
Contingency Plan

Iteration does not
complete on time

3

4

12

Time
Management

Renegotiation with the
client and adjustment of
the planning of the project.
Corrective and remedial
measure to ensure that it
does not happen again.

Product does not
satisfy the client.

2

5

10

Requirement
Gathering,
Architecture
analysis and
assessment.

Accept Feedback and
reassess project feasibility.
If possible implement
feedback and freeze on
deadlock.

Development
Environment not
setup

3

3

9

Technology

Prioritize and finish. Find
out the problem and
reassess planning.

System
Requirements
Modification

2

4

8

Technology

Project will have to be re
-
planned according to new
requirements.

Integrated Test
suite not set up

2

4

8

Technology

Prioritize and get test suite
running. Find out problem
and reassess
test plan.

Communication
problem between
clients and team
members.

2

3

6

Management

A tracking process or
communication channel in
the form of track updates,
status updates or
conference calls will be set
up.

Unanticipated
technology
requirements.

2

3

6

Technology

Required technological
skills will have to be learnt
quickly and adapted to the
system architecture.

Deployment
architecture does
not work

1

5

5

Technology

Assess failure of
architecture. Prioritize and
find alternative solutions.

Team
member’s
motivation and
commitment to
project is low.

1

4

4

Management

Find out grievance cause
and if cannot be
addressed replace with
new resource.

Increase in Costs
for acquisition of
Cloud licenses and
Office suite.

1

4

4

Technology

Re
-
negotiation in
the costs
and licenses with the
client.

<Project Name>



Project Plan


Date: 07/04/10


Confidential


㱃<mp慮y 乡m放

㈰ㄳ

P慧攠


of