Managing Software Deliverables (eBook)

A Software Development Management Methodology

John Rittinghouse PhD CISM (Autor)

eBook Download: PDF

2003 | 1. Auflage
320 Seiten
Elsevier Science (Verlag)
978-0-08-051093-4 (ISBN)

Infos

Managing Software Development describes a set of proven processes for establishing an effective Software Program Management Office (SPMO) function in a corporate setting. Every business that has people performing Software Project Management (PM) activities has a need for these processes. In some instances, an organization may already have a PMO chartered with overall responsibility for each project managed in an enterprise. In those cases, this book will either provide validation of their efforts or it will provide some techniques and useful approaches that can be utilized to further improve on their overall implementation of the PMO. In the vast majority of cases in business, however, a PMO is unheard of. Each project managed in the enterprise is unfortunately managed separately from all others (at great cost in both time and money to the enterprise). The book provides a downloadable drop-in web site containing every type of template needed to perform the activities described here.

*Phase Roadmaps clearly depict what is expected by all parties at each phase of effort
*Pre-built Intranet is ready to deploy in a corporate setting and provides immediate use
*Process Methodology adheres to proven best-practices for software development

---

Managing Software Deliverables describes a set of proven processes for establishing an effective Software Program Management Office (SPMO) function in a corporate setting. Every business that has people performing Software Project Management (PM) activities has a need for these processes. In some instances, an organization may already have a PMO chartered with overall responsibility for each project managed in an enterprise. In those cases, this book will either provide validation of their efforts or it will provide some techniques and useful approaches that can be utilized to further improve on their overall implementation of the PMO. In the vast majority of cases in business, however, a PMO is unheard of. Each project managed in the enterprise is unfortunately managed separately from all others (at great cost in both time and money to the enterprise). - Phase Roadmaps clearly depict what is expected by all parties at each phase of effort- Pre-built Intranet is ready to deploy in a corporate setting and provides immediate use- Process Methodology adheres to proven best-practices for software development

Inhalt

Front Cover 1
Managing Software Deliverables: A Software Development Management Methodology 4
Copyright Page 5
Contents 6
List of Figures 16
Foreword 18
Acknowledgments 22
Introduction 24
i.1 Reasons for Using Software Program Management 25
i.2 Preparing an Organization for Software Program Management 25
i.3 Project Life Cycle in Software Program Management 28
i.4 Overview of This Book 33
Chapter 1. Understanding the SPMO 36
1.1 SPMO Mission Statement 36
1.2 Roles and Responsibilities 36
1.3 Project Resources 39
1.4 SPMO Organizational Structure 39
1.5 Software Program Management Service Areas 40
1.6 Performance Reporting 40
1.7 Issue Management 48
1.8 Quality Management 49
1.9 Change Management 58
1.10 Change Management Plans 59
1.11 Business Requirements Oversight Committee (BROC) 60
1.12 BROC Roles and Responsibilities 62
1.13 The COHEN Bill of 1996 64
1.14 Chapter I Review 65
Chapter 2. SEP Phase I: Initiation 66
2.1 Forming a Core Team 69
2.2 Security Access 69
2.3 Project Framework Rules Document 72
2.4 The Requirements Gathering Process 78
2.5 User Requirements Document (URD) 80
2.6 Project Planning and Documentation Guide (PPDG) 82
2.7 Chapter 2 Review 87
Chapter 3. SEP Phase II: Analysis and Detailed Planning Phase 88
3.1 Project Schedule (PS) 103
3.2 Critical Path (CP) 103
3.3 Chapter 3 Review 110
Chapter 4. SEP Phase III: Detailed Design Phase 112
4.1 Quality Assurance Plan (QAP) 113
4.2 Human Factors Plan (HFP) 113
4.3 Human Factors Report (HFR) 115
4.4 Product Requirements and Specifications (PRSpec) 115
4.5 System Infrastructure Requirements (SIR) 117
4.6 Software Requirements Specification (SRS) 119
4.7 Interface Requirements Specification (IRS) 120
4.8 Performance Requirements Specification (PRS) 121
4.9 Data Development Plan (DDP) 121
4.10 Contracts/Agreements (CA) 122
4.11 Software Development Plan (SDP) 122
4.12 Database Conversion Plan (DCP) 123
4.13 Marketing Communications Plan (MCP) 126
4.14 Marketing Rollout Schedule (MRS) 126
4.15 Marketing Rollout Signoff (MRS) 127
4.16 Project Transition Letter (PTL) 127
4.17 Chapter 4 Review 128
Chapter 5. SEP Phase IV: Construction Phase 130
5.1 Software User Manual (SUM) 131
5.2 Software Installation Manual (SIM) 131
5.3 Training Manual (TM) 132
5.4 Operations and Maintenance Guide (OMG) 132
5.5 Development Process for Test Plans (TP) 133
5.6 SPMO Recommended Test and Certification Plans 137
5.7 Stress Test Plan (SsTP) 138
5.8 Integration Test Plan (ITP) 138
5.9 Product Assurance Test (PAT) 139
5.10 User Acceptance Test (UAT) 140
5.11 MIS/Outside Certification Plan (MISCP) 141
5.12 Product Deliverables 141
5.13 Product Signoff and Certification Letters 141
5.14 Product Assurance Signoff Letter (PASL) 142
5.15 Functional Certification Letter (FCL) 142
5.16 MIS Certification Letter (MISCL) 142
5.17 Data Certification Letter (DCL) 142
5.18 Chapter 5 Review 143
Chapter 6. SEP Phase V: Testing 146
6.1 Review the Test Plan Checklist (TPC) 148
6.2 Test Plan Checklist 148
6.3 Test Logs and Incident Reports 150
6.4 Test Domains 151
6.5 User-Interface Errors 153
6.6 Error Handling 162
6.7 Boundary-Related Errors 163
6.8 Calculation Errors 163
6.9 Control Flow Errors 164
6.10 Errors in Handling or Interpreting Data 164
6.11 Race and Load Conditions 165
6.12 Hardware Errors 166
6.13 Source,Version, and ID Control Errors 166
6.14 Testing Errors 167
6.15 Test Plan Reviews 167
6.16 Chapter 6 Review 168
Chapter 7. SEP Phase VI: Implementation 170
7.1 Review SEP Deliverables Checklist 171
7.2 Develop the User Training Plan 171
7.3 Equipment Installation Plan (EIP) 177
7.4 Develop Installation Rollout Plan 178
7.5 Rollout Plan (ROP) 178
7.6 Rollout Schedule (RS) 179
7.7 Training and Implementation 179
7.8 Rollout Signoff (RSO) 180
7.9 Chapter 7 Review 180
Chapter 8. SEP Phase VII: Support Phase 182
8.1 Software Transition Plan (SWTP) 183
8.2 MIS Hardware and Software Handoff Letter 183
8.3 Hardware Life Cycle Management Plan 183
8.4 Develop Support Plan 184
8.5 Software Configuration Management Plan (SCMP) 184
8.6 Service Level Agreement(s) (SLA) 186
8.7 Components of an SLA 187
8.8 Phase Completion Approval Signoff Completed 190
8.9 Chapter 8 Review 191
Chapter 9. SEP Phase VIII: Project Closeout 192
9.1 Disposition Phase 193
9.2 Disposition Plan 193
9.3 Closeout Actions 194
9.4 Postmortem Meeting Report 195
9.5 Close-out Paperwork (COP) 195
9.6 Archiving the Project 195
9.7 Closeout Ritual 196
9.8 Chapter 9 Review 196
Chapter 10. Project Wizardry 198
10.1 External Factors That Dictate Success 198
10.2 Business Reasons for the Project 198
10.3 Project Customers 200
10.4 Project Objectives 200
10.5 End-State Visions 201
10.6 Making Success a Team Effort 201
10.7 Building Customer Confidence 202
10.8 Choosing a Development Strategy 203
10.9 Software Development Life Cycle (SDLC) Models 203
10.10 Setting Expectations: Staged Deliveries 204
10.11 Rapid Application Development (RAD) 204
10.12 Alternative SDLC Work Patterns 205
10.13 Other Alternative Work Patterns 205
10.14 Alternative Work Pattern Selection 207
10.15 Alternative Work Pattern Descriptions 208
10.16 Matching Resources to Business Need 212
10.17 Developing an Effective Approach to Software Projects 213
10.18 Having" Just Enough" Process 213
10.19 Optimizing Time, Cost, Function, and Quality 213
10.20 Building Realistic Project Plans 214
10.21 A Step-by-Step Process Using SEP 215
10.22 Identifying Tasks, Milestones, and Phases 215
10.23 Building a Project Plan Using the Template 217
10.24 Project Work Breakdown Structure 220
10.25 Pert Charts 222
10.26 Gantt Charts 222
10.27 Performing Reality Checks and "Fit for Purpose" 223
10.28 Assessing Project Risk Factors 223
10.29 Risk Identification List 225
10.30 Building Confidence in the Plan and Selling It Internally 227
10.31 Managing for Success: Day-to-Day Project Management Insights 228
10.32 Daily Tracking and Management 230
10.33 Measuring Progress with Milestones 231
10.34 Pressures to Expect at Each Stage 231
10.35 Managing Conflict Effectively 232
10.36 Estimating for Reality 233
10.37 Creating an Initial Estimate and Revising Estimates 236
10.38 Handling Deadlines 236
10.39 Knowing When and How to "Give and Take" 237
Chapter 11. Some Software Best Practices t o Consider 240
11.1 Project Integrity 241
11.2 Construction Integrity 249
11.3 Product Stability and Integrity 258
Chapter 12. Putting It All Together 264
12.1 Beyond SEP Methodology: Making It All Work 265
12.2 SPMO Implementation Thoughts 265
12.3 People Issues Revisited 267
12.4 Project Management Tools 268
12.5 Study Design and Background Facts 270
12.6 Next Steps 272
12.7 Additional Resources for Managing Software Projects 272
Glossary 274
Common SPMO Acronyms and Abbreviations 296
A. Roadmaps 300
B. Answers 320
B.1 Chapter 1 Review 320
B.2 Chapter 2 Review 322
B.3 Chapter 3 Review 324
B.4 Chapter 4 Review 325
B.5 Chapter 5 Review 327
B.6 Chapter 6 Review 329
B.7 Chapter 7 Review 330
B.8 Chapter 8 Review 332
B.9 Chapter 9 Review 334
C. Software Notes 336
C.1 Installing the Intranet-Based Software 336
References 338
Index 340

Produkt-Details

• Erscheint lt. Verlag: 24.12.2003
• Sprache: englisch
• Themenwelt: Informatik ► Grafik / Design ► Digitale Bildverarbeitung
• Themenwelt: Mathematik / Informatik ► Informatik ► Programmiersprachen / -werkzeuge
• Themenwelt: Mathematik / Informatik ► Informatik ► Software Entwicklung
• ISBN-10: 0-08-051093-0 / 0080510930
• ISBN-13: 978-0-08-051093-4 / 9780080510934