+612 9045 4394
 
CHECKOUT
The Software Project Manager's Handbook : Principles That Work at Work - Dwayne Phillips

The Software Project Manager's Handbook

Principles That Work at Work

Paperback

Published: 1st July 2004
Ships: 15 business days
15 business days
RRP $191.95
$160.50
16%
OFF
or 4 easy payments of $40.13 with Learn more

Software project managers and their team members work individually towards a common goal. This book guides both, emphasizing basic principles that work at work. Software at work should be pleasant and productive, not just one or the other.<br> <br> This book emphasizes software project management at work. The author's unique approach concentrates on the concept that success on software projects has more to do with how people think individually and in groups than with programming. He summarizes past successful projects and why others failed. Visibility and communication are more important than SQL and C. The book discusses the technical and people aspects of software and how they relate to one another.<br> <br> The first part of the text discusses four themes: (1) people, process, product, (2) visibility, (3) configuration management, and (4) IEEE Standards. These themes stress thinking, organization, using what others have built, and people. The second part describes the software management principles of process, planning, and risk management. Part three discusses software engineering principles, the technical aspects of software projects. The fourth part examines software practices giving practical meaning to the individual topics covered in the preceding chapters. The final part of this book continues these practical aspects by illustrating a sample project through seven distinctive documents.

..".clearly explains what it takes to be a good softwareproject manager...a first-rate information source for noviceproject managers." (IEEE Software Magazine, November/December 2005)

..".a useful book for the classroom or the workplace...I advisepurchasing this book and applying the author's ideas." (SoftwareQuality Professional, September 2005)

..".a good reference for individuals just starting off as ITproject managers...For those preparing for the CSQE exam, this bookcan be a good reference..." (Software Quality Professional, June-August 2005)

..".helps guide software project managers and their teammembers in working towards common goals." (IEEE ComputerMagazine, October 2004)

Prefacep. xiii
What Makes a Good Software Manager?p. 3
People Perspectivep. 3
Business Perspectivep. 6
Process Perspectivep. 7
Successful Process Techniquesp. 8
Best Practicesp. 9
Management "Secrets"p. 10
Key Thoughts in This Chapterp. 11
Referencesp. 11
Four Basics That Workp. 13
People, Process, and Productp. 13
Peoplep. 14
Processp. 14
Productp. 15
Balancing the 3Psp. 17
Visibilityp. 18
Basic Visibility Techniquesp. 20
Using the Techniquesp. 24
Configuration Managementp. 25
The CM Planp. 25
Basic Baselinesp. 26
Activitiesp. 28
CM Peoplep. 31
CM Sketchp. 33
Standardsp. 35
Key Thoughts in This Chapterp. 36
Referencesp. 36
What Doesn't Work and Whyp. 39
When the 3Ps Are Out of Balancep. 39
When There's Not Enough Visibilityp. 40
When Configuration Management is Missing or Abusedp. 41
When Standards are Dismissedp. 44
Key Thoughts in This Chapterp. 45
Referencep. 46
Managing a Project Day by Dayp. 47
Balancing the 3Ps to Create a Good Environmentp. 48
Emotional Safetyp. 48
Emphasis on Team Empowermentp. 49
High Degree of Personal Interactionp. 49
Good Balance of Work and Restp. 49
Structure that Promotes Successp. 50
Visibility: Project Control in a Simple Equationp. 52
Collecting Statusp. 52
Collection Guidelinesp. 53
Making Status Visible and Undistortedp. 62
Analyzing the Situationp. 81
Taking Actionp. 82
Making and Communicating Decisionsp. 83
Making a Decision Visiblep. 84
Keeping the Environment Goodp. 86
Managing an External Supplierp. 88
CM: Managing Baselines with Milestonesp. 89
Looking to Standards for Helpp. 90
Key Thoughts in This Chapterp. 91
Referencesp. 92
Requirementsp. 97
Balancing the 3Ps: Requirements Analysis, Documentation, and Managementp. 98
Selecting the Requirements Engineerp. 99
Interviewing Customersp. 100
Conducting Group Meetingsp. 103
Diffusing Tense Situationsp. 104
Evolving Requirementsp. 106
Requirements Versus Designp. 107
Requirements Managementp. 108
Visibility: Making Requirements Knownp. 110
An Overview of Techniquesp. 111
Facilitated Meetings--JADp. 113
Design by Walking Aroundp. 115
System Storyboarding Techniquep. 117
Concept of Operationsp. 118
Mind Mapsp. 119
Gilb Chartsp. 120
Diagram of Effectsp. 121
Rapid Prototypingp. 123
Software Diagramsp. 123
The Software Requirements Specificationp. 133
Database Supportp. 143
Using CMp. 143
Using Standardsp. 145
Key Thoughts in this Chapterp. 148
Referencesp. 151
Planningp. 155
Elements of a Good Planp. 156
Balancing the 3Ps: Selecting the Processp. 161
Are Software Problems Unique?p. 162
Prototypingp. 164
Rapid Application Developmentp. 165
Microsoft Processp. 166
Spiral Processp. 168
Agile Development Methodsp. 172
Process Improvement Mechanismsp. 179
Making the Project Visible: Planning Techniquesp. 196
Project Contextp. 196
Creating a Task Networkp. 198
The Critical Pathp. 203
The Critical Chainp. 204
Cards on the Wall Planningp. 207
Making the Project Visible: Estimating Techniquesp. 208
Rayleigh Modelp. 209
PSP's Probep. 215
A Technique for Simple Estimationp. 220
Judging an Estimatep. 221
Tailoring Techniques to the Process Modelp. 222
Configuration Managementp. 226
Standardsp. 227
All-in-One Military and Commercial Standardsp. 227
Documenting the Planp. 231
Key Thoughts in this Chapterp. 233
Referencesp. 234
Risk Managementp. 237
A Task Overviewp. 239
Balancing The 3Ps: Uncertainty and Choicep. 239
Risk Identificationp. 240
Risk Planningp. 245
Risk Controlp. 246
Risk Monitoringp. 247
Risk Directing and Staffingp. 248
Making Risk Visiblep. 248
Risk Estimatingp. 248
Risk Evaluationp. 249
Risk Analysis Productsp. 250
Other Ways to Manage Riskp. 252
Testingp. 253
Scenario Planningp. 253
Whiteboard Risk Managementp. 254
Configuration Managementp. 254
Using Standardsp. 255
Key Thoughts in this Chapterp. 255
Referencesp. 256
Designp. 259
The Challenge of the 3Psp. 260
Managing Creativityp. 260
Reducing Design Frustrationp. 262
Evaluating and Selecting from Design Alternativesp. 268
Visibility--Expressing the Designp. 273
Wordsp. 273
Picturesp. 274
Design in the Codep. 275
Design and Processp. 277
Designing with COTSp. 278
Configuration Managementp. 280
Configuration Control Boardsp. 281
Design Documentsp. 281
The CM Planp. 282
Tracing Requirementsp. 283
Standards: Writing the SDDp. 284
Contentsp. 284
Organizationp. 286
Key Thoughts in this Chapterp. 287
Referencesp. 289
Integration and Testingp. 291
Some I&T Mythsp. 292
Managing the 3Ps: Peoplep. 294
Managing the 3Ps: Processp. 296
Common Testing Problemsp. 296
IDEAp. 297
Verification and Validationp. 299
Visibility: Testing Techniques and Detailsp. 299
Elements of Effective Testingp. 300
Black Box Testingp. 301
White Box Testingp. 304
Combining White Box and Black Box Testingp. 304
Integration Testingp. 305
Acceptance Testingp. 308
Regression Testingp. 309
Cleanroom Testingp. 309
Test-Driven Developmentp. 313
Configuration Managementp. 314
How Testing Relates to Other Activitiesp. 314
Controlling Test Artifactsp. 316
Using the Requirements Verification Traceability Matrixp. 317
Standards: Documenting the Test Planp. 318
Key Thoughts in this Chapterp. 320
Referencesp. 321
Software Maintenancep. 323
What is Maintenancep. 324
Maintenance or Development?p. 324
Maintenance Activitiesp. 324
Why Use Configuration Management?p. 325
Why Is It So Expensive and Difficult?p. 325
Why We Should Not Neglect Maintenancep. 326
Balancing the 3Ps: Managing the Maintainersp. 327
Balancing the 3Ps: Managing the Processp. 328
Balancing the 3Ps: Making the Most of the Productp. 329
Visibility: Understanding the Maintenance Stagesp. 331
Identification and Classificationp. 331
Analysisp. 333
Designp. 335
Implementationp. 335
System Testp. 336
Acceptance Testp. 336
Deliveryp. 336
Configuration Managementp. 337
Keeping Baselines Straightp. 338
Managing Releasesp. 338
Pacing the Processp. 339
Using Standardsp. 340
Key Thoughts in this Chapterp. 340
Referencesp. 341
Cookbookp. 345
Essentialsp. 347
Use Journals and Decision Recordsp. 347
Perform All CM Activitiesp. 348
Manage Day by Dayp. 348
Use Standardsp. 348
Conduct a Retrospectivep. 348
Opt: A Waterfall Projectp. 349
Contextp. 349
Project Detailsp. 349
System Upgrade: An Evolutionary Projectp. 362
Contextp. 362
Project Detailsp. 362
CTRAN: A Spiral Projectp. 376
Contextp. 376
Risksp. 377
Project Detailsp. 378
Quadrants of the Spiralp. 383
Cycles of the Spiralp. 385
Other Software Projectsp. 389
My Little Spreadsheetp. 389
Let's Make a Web Pagep. 391
An Agile Methods Projectp. 393
Key Thoughts in this Chapterp. 395
Referencesp. 397
Documents for the OPT Projectp. 397
OPT Executive Sponsor Memorandump. 397
OPT Project Context Documentp. 398
OPT Configuration Management Planp. 400
OPT Concept of Operationsp. 407
OPT Software Requirements Specificationp. 410
OPT Software Project Management Planp. 419
OPT Software Design Descriptionp. 431
Configuration Managementp. 439
Will The Real CM Please Stand Up?p. 439
The Main Ingredientsp. 440
Baselinesp. 441
Basicsp. 441
Applying Baselines in a Waterfall Projectp. 442
Applying Baselines in a Nonwaterfall Projectp. 444
Documenting Baselinesp. 445
Baseline Contentsp. 445
Interface Control Documentsp. 446
CM Activitiesp. 448
Identificationp. 448
Controlp. 448
Auditingp. 450
Status Accountingp. 451
CM Peoplep. 451
Configuration Control Boardsp. 451
CM Staffp. 452
Project Managerp. 452
CM Planp. 453
A CM Sketchp. 454
Summaryp. 456
Referencesp. 457
Structured Analysis and Designp. 459
Structured Analysisp. 460
Environmental Modelp. 460
Preliminary Behavioral Modelp. 461
Final Behavioral Modelp. 463
Finished Essential Modelp. 465
Structured Designp. 466
User Implementation Modelp. 466
Systems Implementation Modelp. 467
Program Implementation Modelp. 469
Referencesp. 470
Annotated Bibliographyp. 471
Processp. 471
Visibilityp. 472
Peoplep. 473
Journalsp. 474
Indexp. 475
About the Authorp. 485
Table of Contents provided by Rittenhouse. All Rights Reserved.

ISBN: 9780471674207
ISBN-10: 0471674206
Series: Practitioners
Audience: General
Format: Paperback
Language: English
Number Of Pages: 485
Published: 1st July 2004
Publisher: John Wiley and Sons Ltd
Country of Publication: US
Dimensions (cm): 23.37 x 15.8  x 2.46
Weight (kg): 0.72
Edition Number: 2
Edition Type: Revised