pm - chapter 5 - r1 systems development cycle middle & later stages 200413

7/29/2019 PM - Chapter 5 - R1 Systems Development Cycle Middle & Later Stages 200413

1/20

1

PM/Ch5R1/B30/AA/200413 1

Chapter 5 R1Project Management:

Systems Development Cycle Middle and Late Stages

(Project Management for Business & Technology : Principles & Practice

(R1) John Nicholas)


2/20

2

PM/Ch5R1/B30/AA/200413 2

Topics for discussion

5.1: Phase B: Definition

5.2: Phase C: Execution5.3:Production / Build Stage

5.4: Implementation Stage

5.5:Phase D: Operation5.6:Systems development in Industrial &

Service organizations

5.7:Systems development in largeGovernment programs


3/20

3

PM/Ch5R1/B30/AA/200413 3

5.1: Phase B: Definition

User requirements

Ref Fig 5-1 p121

Ref example Userrequirements for Productdevelopment, p122

System objectives


4/20

4

PM/Ch5R1/B30/AA/200413 4

5.1: Phase B: Definition (contd..)

User requirements System Objectives

1.Vehicle acceleration 0 to 60in 10 sec & seat 6 people Vehicle size, weight, Engine HP,

transmission type

2. House should be

spacious for 4

Number & size

/dimensions of rooms

Overall Design review, external surfaceMaterials, usage of existing versus

new components, systems3. Aircraft must be stealthy

4. Space station must operateLife support, manufacturing& experimental equipment

Type & KWH generating capacity,Technology for primary life support

Systems, power back up, wasteDisposal, inventory planning for

Excess durations


5/20

5

PM/Ch5R1/B30/AA/200413 5


System objectives System specifications

Compatibility Ability of subsystems to integrate into whole system

Commonality Interchangeability with existing component of diff type Cost-effectiveness Includes design cost, user cost for setting, operating,

Reliability Ability to function at a level / upto certain time before failing

Maintainability Ease of repair-ability & within certain time

Testability Enabling system testing & measurement of performance

Availability Degree to which a system can operate when needed

Ease of use User friendliness

Robustness Ability of system to withstand/survive a harsh environment

Ease of growth or enhancement Expandable to include newfunctions or to be adapted to new conditions


6/20

6

PM/Ch5R1/B30/AA/200413 6


System specifications reflect & support systemobjectives

System specifications address all project areas /activities: System design, equipment / civildesigns, fabrication, installation, testing, startup, operation, maintenance etc

System specifications will thus guide the entireactual project work

In addition to detailed System specifications,Baseline specifications are also established

Sometimes, Prototype may be built at firststage of Phase B to finalize Systemspecifications for actual Project eg Computersystems, Ref example 2 p126


7/20

7

PM/Ch5R1/B30/AA/200413 7


Team involvement in Definition stage:

- All parties who have a stake in Project-Master Requirements Document includes allBaseline specifications jointly prepared,accepted & committed by all parties

- Similar process for Product DevelopmentProject also

- Quality Function Deployment (QFD) is usedto provide data about critical productelementsto evolve specific technical targets


8/20

8

PM/Ch5R1/B30/AA/200413 8


Detailed Project Planning:

- User requirements, system objectives, systemspecifications

- Work schedules & deadlines

- Budgets, cost accounts & cost control system

- Work Breakdown Structure (WBS) & work packages

- Areas of high risk, uncertainty & contingency plans- Personnel & resource utilization plans

- Quality plans

- Plans for testing systems

- Documentation plans- Change Control & work review plans

- Preliminary Project Implementation Plan


9/20

9

PM/Ch5R1/B30/AA/200413 9


Project Quality: To produce Correct End Item andproduce in the Correct Way

Produce correct item:

- Through well defined User Requirements,

- Through well defined Systems objectives

- Through well defined System specifications

Produce the correct way: The Process

- Through a good Project Quality Plan

- Through the proper work & activities performed in

Phase C: Execution- Through well defined and listed Entry, Process &

Exit Conditions for each work package, stage and /or activity


10/20

10

PM/Ch5R1/B30/AA/200413 10


System defects:

- Represents a non-conformance event /

action- Non-conformity to be immediately identified,

corrected and prevented to recur

- Remember Trade offs between dimensions

of time, cost & user requirements- Sometimes use the concept of Good

enough Quality to solve the immediate riskfactor or quality threat, but take all

customers into confidence and keep thecustomers formally apprised of such Goodenough Quality issues


11/20

11

PM/Ch5R1/B30/AA/200413 11

5.2: Phase C: Execution

Includes following stages:

- Design Stage- Development Stage

- Procurement Stage

- Construction Phase

- Erection / Installation Stage

- Operation Stage

- Production / Manufacturing Stage

Ref Fig 5-3, 5-4, 5-5 p133, p134, p135respectively

12


12/20

12

PM/Ch5R1/B30/AA/200413 12

5.3:Production / Build Stage

System is ready to be fabricated

System fabrication on the basisof design specifications

System testing

Contract administration

Planning for implementation

13


13/20

13

PM/Ch5R1/B30/AA/200413 13

5.4: Implementation Stage

User Training

User Acceptance Testing

System Installation & Conversion Stage

14


14/20

14

PM/Ch5R1/B30/AA/200413 14

5.4: Implementation Stage (contd..)User Training

Teach user how to operate, maintain & service the

system

Could be short, low-cost or long duration &expensive

Training requirements decide training materials

manuals, videos, simulators etc Training requirements decide training techniques-

classroom, simulation, on the job, role plays etc

Training requirements decide training schedules all at once, in phases, periodical, frequency based)

Training provides overview of system objectives,scope, operation, interface with existing elements /systems of organization & environment

15


15/20

15

PM/Ch5R1/B30/AA/200413 15

5.4: Implementation Stage (contd..)User Acceptance Testing (UAT)

To verify & decide on a) adoption or b)installation pending modifications /adjustments or c) total rejection

User tests will be performed by user

departmental personnel, with little orsubstantial assistance / involvement fromproject personnel

Project team steps in case of problems in

UAT Avoid biases / vested interests and solve

problems with technical & objectiveapproach

16


16/20

16

PM/Ch5R1/B30/AA/200413 16

5.4: Implementation Stage (contd..)System installation & conversion stage

Strategy decisions on replacement of old system with

the new system Issues in conversion strategy: Costs, Risks, Logistics

& time

Project manager has to address interpersonal &

organizational adjustments, issue based problemsolving approach, ensure patient & sensitive listeningto systems & users problems

- Parallel installation safest, most expensive (tooperate 2 systems)

- Pilot operation costs & risks are low, but it maynot be total & accurate representation of real system

- Cold turkey / big bang least costly, fastest butthe most risky

17


17/20

17

PM/Ch5R1/B30/AA/200413 17

5.5:Phase D: Operation

System evaluation &Maintenance

Improving the system

18


18/20

18

PM/Ch5R1/B30/AA/200413 18

5.6:Systems development in Industrial &Service organizations

New Product Development

Software Product Development

Relocation of a company division

Overhaul of Human ServicesAdministration

19


19/20

19

PM/Ch5R1/B30/AA/200413 19

5.7:Systems development in largeGovernment programs

Planetary Exploration Programs

Defence Weapons Systems Programs

20


20/20

20

PM/Ch5R1/B30/AA/200413 20

End of Chapter 5 R1

pm - chapter 5 - r1 systems development cycle middle & later stages 200413

Documents