Personal Software Process Lecture 11 The Planning Process

Personal Software Process Lecture 11 The Planning Process Jerzy. Nawrocki@put. poznan. pl www. cs. put. poznan. pl/jnawrocki/mse/psp/ J. Nawrocki, PSP, Lecture 11 Copyright, 1999 © Jerzy R. Nawrocki

Introduction Why make plans ? Connection between cost, schedule, and the planning process (an example) Business commitments Commitments plans J. Nawrocki, PSP, Lecture 11

What is a plan The project plan defines the work and how it will be done. It provides: • a definition of each major task, • an estimate of the time and resources required, and • a framework for management review and control. J. Nawrocki, PSP, Lecture 11

What is a plan Plans are used as: • a basis for agreeing on the cost and schedule • an organising structure for doing the work • a framework for obtaining the required resources • a record of what was initially committed J. Nawrocki, PSP, Lecture 11

Contents of a software plan PSP plans have two users You J. Nawrocki, PSP, Lecture 11 Your customer

Contents of a software plan You J. Nawrocki, PSP, Lecture 11 You need from a plan: • job sizing • job structure • job status • assessment (possible improvements)

Contents of a software plan Your customer needs from a plan: • What is the commitment ? (what, when, at what cost) • What is the expected quality ? • How about monitoring the Your customer progress ? • The impact of scope changes J. Nawrocki, PSP, Lecture 11

Planning a software project • Define clearly the planned work • Split it into multiple steps that are clearly defined and measurable • Base your estimates on the historical data • Record your estimates and later compare them with your actual results • Check the plan with the user before you start work • Make periodic progress statements to your customers J. Nawrocki, PSP, Lecture 11

Producing a quality plan A good plan should be: • complete (forms) • accessible (a proper place & format) • clear (readable) • specific (what, when, by whom, at what costs) • precise (unit of time) • accurate (random errors - no problem) J. Nawrocki, PSP, Lecture 11

Project plan overview 1 Introduction 2 Management plan 3 Quality plan 4 Purchasing plan 5 Development plan 6 Test plan 7 Installation and delivery 8 Product management 9 Maintenance 10 The project plan J. Nawrocki, PSP, Lecture 11

Project Plan Document (1) Software Development Studio Faculty of Electrical Engineering Poznan University of Technology Project title. Project Plan Version: SRSver-CDver-1. 0 x/date by manager 1, manager 2 Document status: Draft | Submitted | Under revision | Checked | Accepted | Frozen J. Nawrocki, PSP, Lecture 11

Project Plan Document (2) I have seen this already. . . J. Nawrocki, PSP, Lecture 11 1. Introduction 1. 1 Purpose of the document 1. 2 Scope of the product 1. 3 Definitions, acronyms and abbreviations 1. 4 References 1. 5 Overview of the document 1. 6 History of the document

Project Plan Document (3) 2 Management plan 2. 1 Management 2. 1. 1 Project management 2. 1. 2 Steering committee 2. 2 Status reporting 2. 3 Risk management 2. 4 Provision of facilities 2. 5 Customer-supplied material J. Nawrocki, PSP, Lecture 11

Project Plan Document (4) 2. 6 Skills and resource requirements 2. 6. 1 Skills and resources 2. 6. 2 Training 2. 7 Changes 2. 8 Problems 2. 9 Confidentiality 2. 10 Joint reviews 2. 11 Audit 2. 12 Updating this plan J. Nawrocki, PSP, Lecture 11

Project Plan Document (5) 3. Quality plan 3. 1 Development standards 3. 2 Development environment 3. 3 Inspection, measuring and test equipment 3. 4 Development cycle J. Nawrocki, PSP, Lecture 11

Project Plan Document (6) 3. 5 Products to be developed Requirements specification Conceptual design Project plan User manual Implementation report (DCT) 3. 6 Final inspection 3. 7 Records J. Nawrocki, PSP, Lecture 11

Project Plan Document (7) Buy or not to buy. . J. Nawrocki, PSP, Lecture 11 4 Purchasing plan 4. 1 Purchasing requirements 4. 2 Selection of suppliers / subcontractors 4. 3 Subcontract control 4. 4 Verification of purchased product

Project Plan Document (8) 5 Development plan 5. 1 Project plan 5. 1. 1 Organisation and staffing 5. 1. 2 Project planning 5. 1. 3 Review of project plan 5. 1. 4 Acceptance of project plan 5. 1. 5 Issue of project plan 5. 1. 6 Changing project plan J. Nawrocki, PSP, Lecture 11

Project Plan Document (9) 5. 2 Functional requirements 5. 2. 1 Organisation and staffing 5. 2. 2 Requirements specification 5. 2. 3 Review of RS 5. 2. 4 Acceptance of RS 5. 2. 5 Issue of RS 5. 2. 6 Changing RS J. Nawrocki, PSP, Lecture 11

Project Plan Document (10) 5. 3 Design 5. 3. 1 Organisation and staffing 5. 3. 2 Design input 5. 3. 3 Design 5. 3. 4 Design output 5. 3. 5 Review of design 5. 3. 6 Acceptance of design 5. 3. 7 Issue of design 5. 3. 8 Changing design J. Nawrocki, PSP, Lecture 11

Project Plan Document (11) 5. 4 Programming 5. 4. 1 Organisation and staffing 5. 4. 2 Programming 5. 4. 3 Code reviews 5. 4. 4 Code acceptance 5. 4. 5 Issue of code 5. 4. 6 Changing code J. Nawrocki, PSP, Lecture 11

Project Plan Document (12) 5. 5 Documenting 5. 4. 1 Organisation and staffing 5. 4. 2 Writing documentation 5. 4. 3 Documentation reviews 5. 4. 4 Documentation acceptance 5. 4. 5 Issue of documentation 5. 4. 6 Changing documentation J. Nawrocki, PSP, Lecture 11

Project Plan Document (13) 6 Test plan 6. 1 Facilities and tools 6. 2 Acceptance criteria 6. 3 Unit testing 6. 4 System and integration testing 6. 5 Acceptance testing J. Nawrocki, PSP, Lecture 11

Project Plan Document (14) 7 Installation and delivery 7. 1 Installation 7. 2 Handling, storage, packaging, and delivery 7. 3 Other contractual services J. Nawrocki, PSP, Lecture 11

Project Plan Document (15) Does this version work? J. Nawrocki, PSP, Lecture 11 8 Product management plan 8. 1 Product register 8. 2 Product identification 8. 3 Version control 8. 4 Maintenance of libraries 8. 5 Non-conforming product

Project Plan Document (16) Maintenance is not my business 9 Maintenance plan 9. 1 Warranty and maintenance period 9. 2 Support and help desk 9. 3 Notification of defects and their rectification J. Nawrocki, PSP, Lecture 11

Project Plan Document (17) 10 The project plan 10. 1 Overall project plan I’m good in planning, 10. 2 Functional requirements not in doing. . plan 10. 2. 1 Plan 10. 2. 2 Milestones and payment schedule 10. 2. 3 Actual 10. 3 Conceptual design. . . J. Nawrocki, PSP, Lecture 11

Summary Planning. . • is very important, • and comprises many aspects of a project. J. Nawrocki, PSP, Lecture 11

Further readings M. G. Jenner, Software Quality Management and ISO 9001, John Wiley & Sons, New York. J. Nawrocki, PSP, Lecture 11

Quality assessment 1. What is your general impression ? (1 - 6) 2. Was it too slow or too fast ? 3. Did you learn something important to you ? 4. What to improve and how ? J. Nawrocki, PSP, Lecture 11