1

Chapter 5 R1
Project Management: Systems Development Cycle Middle and Late Stages
(Project Management for Business & Technology : Principles & Practice

(R1) John Nicholas)

PM/Ch5R1/B30/AA/200413

Topics for discussion

5.1: Phase B: Definition 5.2: Phase C: Execution

5.3:Production / Build Stage

5.4: Implementation Stage 5.5:Phase D: Operation

5.6:Systems development in Industrial & Service organizations

5.7:Systems development in large Government programs

PM/Ch5R1/B30/AA/200413

5.1: Phase B: Definition

User requirements Ref Fig 5-1 p121 Ref example User requirements for Product development, p122 System objectives
PM/Ch5R1/B30/AA/200413 3

5.1: Phase B: Definition (contd..)

User requirements
1.Vehicle acceleration 0 to 60 in 10 sec & seat 6 people

System Objectives
Vehicle size, weight, Engine HP, transmission type Number & size /dimensions of rooms

2. House should be spacious for 4

Overall Design review, external surface 3. Aircraft must be stealthy Materials, usage of existing versus new components, systems Type & KWH generating capacity, 4. Space station must operateTechnology for primary life support Systems, power back up, waste Life support, manufacturing Disposal, inventory planning for & experimental equipment Excess durations
PM/Ch5R1/B30/AA/200413 4

5.1: Phase B: Definition (contd..)

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 new
functions or to be adapted to new conditions

PM/Ch5R1/B30/AA/200413

5.1: Phase B: Definition (contd..)

System specifications reflect & support system objectives System specifications address all project areas / activities: System design, equipment / civil designs, fabrication, installation, testing, start up, operation, maintenance etc System specifications will thus guide the entire actual project work In addition to detailed System specifications, Baseline specifications are also established Sometimes, Prototype may be built at first stage of Phase B to finalize System specifications for actual Project eg Computer systems, Ref example 2 p126
PM/Ch5R1/B30/AA/200413 6

5.1: Phase B: Definition (contd..) Team involvement in Definition stage:

- All parties who have a stake in Project - Master Requirements Document includes all Baseline specifications jointly prepared, accepted & committed by all parties - Similar process for Product Development Project also - Quality Function Deployment (QFD) is used to provide data about critical product elements to evolve specific technical targets

PM/Ch5R1/B30/AA/200413

5.1: Phase B: Definition (contd..)

Detailed Project Planning:
- User requirements, system objectives, system specifications - 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

PM/Ch5R1/B30/AA/200413

5.1: Phase B: Definition (contd..)

Project Quality: To produce Correct End Item and produce 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
PM/Ch5R1/B30/AA/200413 9

5.1: Phase B: Definition (contd..)

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 risk factor or quality threat, but take all customers into confidence and keep the customers formally apprised of such Good enough Quality issues
PM/Ch5R1/B30/AA/200413 10

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, p135 respectively

PM/Ch5R1/B30/AA/200413 11

5.3:Production / Build Stage System is ready to be fabricated

12

System fabrication on the basis of design specifications

System testing Contract administration Planning for implementation
PM/Ch5R1/B30/AA/200413 12

5.4: Implementation Stage User Training User Acceptance Testing System Installation & Conversion Stage

13

PM/Ch5R1/B30/AA/200413

13

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 techniquesclassroom, 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
PM/Ch5R1/B30/AA/200413 14

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 or substantial assistance / involvement from project personnel Project team steps in case of problems in UAT Avoid biases / vested interests and solve problems with technical & objective approach
PM/Ch5R1/B30/AA/200413 15

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 problem solving approach, ensure patient & sensitive listening to systems & users problems - Parallel installation safest, most expensive (to operate 2 systems) - Pilot operation costs & risks are low, but it may not be total & accurate representation of real system - Cold turkey / big bang least costly, fastest but the most risky
PM/Ch5R1/B30/AA/200413 16

16

5.5:Phase D: Operation

17

System evaluation & Maintenance

Improving the system

PM/Ch5R1/B30/AA/200413

17

5.6:Systems development in Industrial & Service organizations

New Product Development

18

Software Product Development

Relocation of a company division Overhaul of Human Services Administration

PM/Ch5R1/B30/AA/200413

18

5.7:Systems development in large Government programs

Planetary Exploration Programs

19

Defence Weapons Systems Programs

PM/Ch5R1/B30/AA/200413

19

20

End of Chapter 5 R1

PM/Ch5R1/B30/AA/200413

20