| |
| |
| Foreword | |
| |
| |
| Preface | |
| |
| |
| About the Authors | |
| |
| |
| Web Added Value� | |
| |
| |
| Software Project Basics | |
| |
| |
| Introduction | |
| |
| |
| Types of Software Projects | |
| |
| |
| Classifications of Software Projects | |
| |
| |
| Based on Software Development Life Cycle | |
| |
| |
| Approach Driven | |
| |
| |
| Maintenance | |
| |
| |
| Web Application | |
| |
| |
| Agile Development | |
| |
| |
| Conclusion | |
| |
| |
| Approaches to Software Project Management | |
| |
| |
| Alignment of Software Engineering Methodology with Project Management Methodology | |
| |
| |
| The Ad Hoc Methods-Based Approach | |
| |
| |
| The Process-Driven Approach | |
| |
| |
| So, What is the Right Approach? | |
| |
| |
| The Ad Hoc Approach | |
| |
| |
| The Process-Driven Approach | |
| |
| |
| But Is a Process-Driven Approach the Right Choice? | |
| |
| |
| In a Process-Driven Approach: What Process and How Much? | |
| |
| |
| Software Project Acquisition | |
| |
| |
| From an External Client | |
| |
| |
| The Request for Proposal | |
| |
| |
| The Proposal | |
| |
| |
| Negotiation | |
| |
| |
| Contract Acceptance | |
| |
| |
| From an Internal Client | |
| |
| |
| The Feasibility Study | |
| |
| |
| Preparing the Proposal | |
| |
| |
| Finalizing the Proposal | |
| |
| |
| Reference | |
| |
| |
| Software Project Initiation | |
| |
| |
| Introduction | |
| |
| |
| Initiation Activities | |
| |
| |
| Project Management Office-Level Activities | |
| |
| |
| Identifying the Software Project Manager | |
| |
| |
| Preparing/Handing Over the Project Dossier to the Software Project Manager | |
| |
| |
| Coordinating Allocation of Project Resources | |
| |
| |
| Assisting the Software Project Manager in Obtaining Necessary Service Level Agreements from Departments in the Organization | |
| |
| |
| Assisting the Software Project Manager with the Project Kickoff Meeting | |
| |
| |
| Software Project Manager-Level Activities | |
| |
| |
| Ensuring that Project Specifications Are Complete | |
| |
| |
| Reviewing Estimates and Revisions/Updates of Estimates | |
| |
| |
| Identifying Necessary Resources and Raising Requests | |
| |
| |
| Preparing Project Plans | |
| |
| |
| Setting up the Development Environment | |
| |
| |
| Arranging for Project-Specific Skill Training | |
| |
| |
| Organizing the Project Team | |
| |
| |
| Training the Project Team on the Project Plans | |
| |
| |
| Conducting a Project Kickoff Meeting | |
| |
| |
| Arranging for a Phase-End Audit | |
| |
| |
| Common Pitfalls in Project Initiation | |
| |
| |
| Identifying the Wrong Software Project Manager | |
| |
| |
| Identifying Inappropriate Resources | |
| |
| |
| Incurring Delays in Software Project Initiation Activities | |
| |
| |
| References | |
| |
| |
| Software Project Planning | |
| |
| |
| Introduction | |
| |
| |
| Planning Defined | |
| |
| |
| Plans Prepared in Software Project Management | |
| |
| |
| The Project Management Plan | |
| |
| |
| Resources | |
| |
| |
| Skill Sets | |
| |
| |
| Computer Systems | |
| |
| |
| Project Management Method | |
| |
| |
| The Configuration Management Plan | |
| |
| |
| Naming Conventions | |
| |
| |
| Change Management | |
| |
| |
| The Quality Assurance Plan | |
| |
| |
| The Schedule Plan | |
| |
| |
| The Induction Training Plan | |
| |
| |
| The Risk Management Plan | |
| |
| |
| The Build Plan | |
| |
| |
| The Deployment Plan | |
| |
| |
| The User Training Plan | |
| |
| |
| The Handover Plan | |
| |
| |
| The Software Maintenance Plan | |
| |
| |
| The Documentation Plan | |
| |
| |
| Roles in Planning | |
| |
| |
| The Organization | |
| |
| |
| The Software Project Manager | |
| |
| |
| Pitfalls in Software Project Planning | |
| |
| |
| Best Practices in Software Project Planning | |
| |
| |
| References | |
| |
| |
| Software Project Execution | |
| |
| |
| Introduction | |
| |
| |
| Work Management | |
| |
| |
| Work Registers | |
| |
| |
| De-allocation | |
| |
| |
| Configuration Management | |
| |
| |
| Information Artifacts | |
| |
| |
| Code Artifacts | |
| |
| |
| Configuration Registers | |
| |
| |
| Configuration Management Tools | |
| |
| |
| Quality Management | |
| |
| |
| Verification Techniques | |
| |
| |
| Validation Techniques | |
| |
| |
| Product Testing | |
| |
| |
| Allocation of Quality Assurance Activities | |
| |
| |
| But How Much Quality Assurance? | |
| |
| |
| Testing Tools | |
| |
| |
| Morale Management | |
| |
| |
| Motivation | |
| |
| |
| Conflict | |
| |
| |
| Productivity Management | |
| |
| |
| Stakeholder Expectations Management | |
| |
| |
| Product Integration Management | |
| |
| |
| Pitfalls and Best Practices | |
| |
| |
| Software Project Execution Control | |
| |
| |
| Introduction | |
| |
| |
| Aspects of Control in Project Execution | |
| |
| |
| Scope Control | |
| |
| |
| Cost Control | |
| |
| |
| Schedule/Progress Control | |
| |
| |
| Quality Control | |
| |
| |
| Effort Control | |
| |
| |
| Productivity Monitoring | |
| |
| |
| Control Mechanisms | |
| |
| |
| Progress Assessment: Earned Value Analysis | |
| |
| |
| Change Management in Software Development Projects | |
| |
| |
| Introduction | |
| |
| |
| Origins of Change | |
| |
| |
| The Change Request Register | |
| |
| |
| Change Request Resolution | |
| |
| |
| Change Request Implementation Strategy | |
| |
| |
| The Value of Metrics Derived from a Change Request Register | |
| |
| |
| Scheduling | |
| |
| |
| Introduction | |
| |
| |
| The Initial Work Breakdown Structure | |
| |
| |
| A Work Breakdown Structure with Predecessors Defined | |
| |
| |
| A Work Breakdown Structure with Initial Dates | |
| |
| |
| A Work Breakdown Structure with Resource Allocation | |
| |
| |
| Scheduling in Practice | |
| |
| |
| Graphic Representation of a Schedule | |
| |
| |
| Software Project Closure | |
| |
| |
| Introduction | |
| |
| |
| Identifying Reusable Code Components | |
| |
| |
| Documenting the Best Practices | |
| |
| |
| Documenting the Lessons Learned | |
| |
| |
| Collecting/Deriving and Depositing the Final Project Metrics in the Organizational Knowledge Repository | |
| |
| |
| Conducting Knowledge-Sharing Meetings with Peer Software Project Managers | |
| |
| |
| Depositing Project Records with the Project Management Office | |
| |
| |
| Depositing Code Artifacts in the Code Repository | |
| |
| |
| Conducting the Project Postmortem | |
| |
| |
| Releasing the Software Project Manager | |
| |
| |
| Closing the Project | |
| |
| |
| The Role of the Organization in Project Closure | |
| |
| |
| The Project Management Office | |
| |
| |
| The Configuration Control Board | |
| |
| |
| The Systems Administration Department | |
| |
| |
| Reference | |
| |
| |
| Agile Project Management | |
| |
| |
| Introduction | |
| |
| |
| Project Management Roles | |
| |
| |
| Agile Project Management Characteristics | |
| |
| |
| Metaphor | |
| |
| |
| Teamwork and Collaboration | |
| |
| |
| Guiding Principles | |
| |
| |
| Open Information | |
| |
| |
| Use a Light Touch | |
| |
| |
| Monitoring and Adjustment | |
| |
| |
| The Nuts and Bolts of Agile Project Management | |
| |
| |
| Planning the Work | |
| |
| |
| Controlling the Work | |
| |
| |
| Process Improvement | |
| |
| |
| Reference | |
| |
| |
| Pitfalls and Best Practices in Software Project Management | |
| |
| |
| Introduction | |
| |
| |
| Organizational-Level Pitfalls and Best Practices | |
| |
| |
| Process-Driven Project Management | |
| |
| |
| An Ineffective Project Management Office or No Project Management Office | |
| |
| |
| Poor Project Initiation | |
| |
| |
| Poor Software Estimation | |
| |
| |
| Poor Project Planning | |
| |
| |
| The Wrong Service Level Agreements | |
| |
| |
| Poor Standards and Guidelines for Software Development | |
| |
| |
| Poor Project Oversight | |
| |
| |
| Inadequate Project Management Training | |
| |
| |
| Software Project Manager-Level Pitfalls and Best Practices | |
| |
| |
| Fair Treatment of Project Human Resources | |
| |
| |
| A Balanced Workload | |
| |
| |
| Equitable Rewards | |
| |
| |
| Poor Software Estimation | |
| |
| |
| Poor Project Planning | |
| |
| |
| Informal Issue Resolution | |
| |
| |
| Poor Change Management | |
| |
| |
| Poor Record Keeping | |
| |
| |
| Additional Best Practices for Software Project Management | |
| |
| |
| A Knowledge Repository | |
| |
| |
| Continuous Process Improvement | |
| |
| |
| Project Postmortems | |
| |
| |
| Training in the Soft Skills | |
| |
| |
| Information Sharing | |
| |
| |
| Management Support | |
| |
| |
| Some Closing Words | |
| |
| |
| Management of Software Development Projects | |
| |
| |
| Decision-Making for Software Project Managers | |
| |
| |
| People Management | |
| |
| |
| Productivity Concepts for Software Project Managers | |
| |
| |
| Issue Resolution in Software Project Management | |
| |
| |
| Measurement and Metrics in Software Development Organizations | |
| |
| |
| Measurement and Management of Customer Satisfaction | |
| |
| |
| An Introduction to PERT/CPM | |
| |
| |
| Abbreviations | |
| |
| |
| Templates for Software Project Managers | |
| |
| |
| Index | |