Mastering Software Project Management Best Practices, Tools and Techniques

by ;
Format: Hardcover
Pub. Date: 2010-07-01
Publisher(s): J. Ross Publishing
  • Free Shipping Icon

    This Item Qualifies for Free Shipping!*

    *Excludes marketplace orders.

List Price: $63.95

Buy New

Usually Ships in 2-3 Business Days
$63.89

Rent Textbook

Select for Price
There was a problem. Please try again later.

Rent Digital

Rent Digital Options
Online:120 Days access
Downloadable:120 Days
$35.94
Online:180 Days access
Downloadable:180 Days
$41.94
Online:1825 Days access
Downloadable:Lifetime Access
$53.94
*To support the delivery of the digital material to you, a digital delivery fee of $3.99 will be charged on each digital item.
$41.94*

Used Textbook

We're Sorry
Sold Out

How Marketplace Works:

  • This item is offered by an independent seller and not shipped from our warehouse
  • Item details like edition and cover design may differ from our description; see seller's comments before ordering.
  • Sellers much confirm and ship within two business days; otherwise, the order will be cancelled and refunded.
  • Marketplace purchases cannot be returned to eCampus.com. Contact the seller directly for inquiries; if no response within two days, contact customer service.
  • Additional shipping costs apply to Marketplace purchases. Review shipping costs at checkout.

Summary

This unique reference covers the subject of software project management in its entirety, including

Author Biography

Murali Chemuturi is an information technology and software development subject matter expert, hands-on programmer, author, consultant and trainer. He has more than 23 years of information technology and software development experience and several years of academic experience teaching a variety of computer & IT courses. In 2001, he formed his own IT consulting, training and software development firm known as Chemuturi Consultants. Mr. Chemuturi's undergraduate degrees and diplomas are in Electrical and Industrial Engineering and he holds an MBA and a Post Graduate Diploma in Computer Methods & Programming. He is a published author in professional journals, a member of IEEE, a senior member of the Computer Society of India and a Fellow at the Indian Institute of Industrial Engineering. Tom Cagley has over 20 years experience in the software industry. He currently leads the David Consulting Group's IT Performance Improvement, Software Process Improvement and Software Measurement consulting practices. He is also the current president of the International Function Point Users Group and is a Certified Function Point Specialist. Tom is a frequent speaker at metrics, quality and project management conferences. Tom earned his BS from Louisiana State University and has done extensive postgraduate work at Cleveland State University, Case Western Reserve University and Kent State University.

Table of Contents

Forewordp. ix
Prefacep. xiii
About the Authorsp. xv
Web Added ValueƖp. xvii
Software Project Basicsp. 1
Introductionp. 1
Types of Software Projectsp. 5
Classifications of Software Projectsp. 6
Based on Software Development Life Cyclep. 7
Approach Drivenp. 9
Maintenancep. 12
Web Applicationp. 16
Agile Developmentp. 17
Conclusionp. 17
Approaches to Software Project Managementp. 19
Alignment of Software Engineering Methodology with Project Management Methodologyp. 19
The Ad Hoc Methods-Based Approachp. 21
The Process-Driven Approachp. 22
So, What is the Right Approach?p. 23
The Ad Hoc Approachp. 24
The Process-Driven Approachp. 24
But Is a Process-Driven Approach the Right Choice?p. 24
In a Process-Driven Approach: What Process and How Much?p. 26
Software Project Acquisitionp. 31
From an External Clientp. 31
The Request for Proposalp. 32
The Proposalp. 34
Negotiationp. 42
Contract Acceptancep. 43
From an Internal Clientp. 44
The Feasibility Studyp. 45
Preparing the Proposalp. 47
Finalizing the Proposalp. 47
Referencep. 48
Software Project Initiationp. 49
Introductionp. 49
Initiation Activitiesp. 49
Project Management Office-Level Activitiesp. 52
Identifying the Software Project Managerp. 52
Preparing/Handing Over the Project Dossier to the Software Project Managerp. 52
Coordinating Allocation of Project Resourcesp. 53
Assisting the Software Project Manager in Obtaining Necessary Service Level Agreements from Departments in the Organizationp. 55
Assisting the Software Project Manager with the Project Kickoff Meetingp. 55
Software Project Manager-Level Activitiesp. 55
Ensuring that Project Specifications Are Completep. 57
Reviewing Estimates and Revisions/Updates of Estimatesp. 57
Identifying Necessary Resources and Raising Requestsp. 59
Preparing Project Plansp. 62
Setting up the Development Environmentp. 63
Arranging for Project-Specific Skill Trainingp. 63
Organizing the Project Teamp. 64
Training the Project Team on the Project Plansp. 64
Conducting a Project Kickoff Meetingp. 65
Arranging for a Phase-End Auditp. 65
Common Pitfalls in Project Initiationp. 66
Identifying the Wrong Software Project Managerp. 66
Identifying Inappropriate Resourcesp. 66
Incurring Delays in Software Project Initiation Activitiesp. 67
Referencesp. 67
Software Project Planningp. 69
Introductionp. 69
Planning Definedp. 71
Plans Prepared in Software Project Managementp. 73
The Project Management Planp. 77
Resourcesp. 77
Skill Setsp. 77
Computer Systemsp. 79
Project Management Methodp. 79
The Configuration Management Planp. 80
Naming Conventionsp. 83
Change Managementp. 84
The Quality Assurance Planp. 85
The Schedule Planp. 86
The Induction Training Planp. 86
The Risk Management Planp. 87
The Build Planp. 88
The Deployment Planp. 88
The User Training Planp. 89
The Handover Planp. 90
The Software Maintenance Planp. 90
The Documentation Planp. 90
Roles in Planningp. 91
The Organizationp. 91
The Software Project Managerp. 92
Pitfalls in Software Project Planningp. 93
Best Practices in Software Project Planningp. 95
Referencesp. 96
Software Project Executionp. 97
Introductionp. 97
Work Managementp. 98
Work Registersp. 100
De-allocationp. 102
Configuration Managementp. 104
Information Artifactsp. 104
Code Artifactsp. 106
Configuration Registersp. 111
Configuration Management Toolsp. 115
Quality Managementp. 117
Verification Techniquesp. 119
Validation Techniquesp. 120
Product Testingp. 121
Allocation of Quality Assurance Activitiesp. 124
But How Much Quality Assurance?p. 124
Testing Toolsp. 125
Morale Managementp. 126
Motivationp. 126
Conflictp. 130
Productivity Managementp. 131
Stakeholder Expectations Managementp. 133
Product Integration Managementp. 138
Pitfalls and Best Practicesp. 140
Software Project Execution Controlp. 143
Introductionp. 143
Aspects of Control in Project Executionp. 144
Scope Controlp. 145
Cost Controlp. 146
Schedule/Progress Controlp. 147
Quality Controlp. 148
Effort Controlp. 148
Productivity Monitoringp. 148
Control Mechanismsp. 149
Progress Assessment: Earned Value Analysisp. 153
Change Management in Software Development Projectsp. 157
Introductionp. 157
Origins of Changep. 158
The Change Request Registerp. 160
Change Request Resolutionp. 162
Change Request Implementation Strategyp. 163
The Value of Metrics Derived from a Change Request Registerp. 167
Schedulingp. 171
Introductionp. 171
The Initial Work Breakdown Structurep. 172
A Work Breakdown Structure with Predecessors Definedp. 172
A Work Breakdown Structure with Initial Datesp. 176
A Work Breakdown Structure with Resource Allocationp. 178
Scheduling in Practicep. 181
Graphic Representation of a Schedulep. 181
Software Project Closurep. 183
Introductionp. 183
Identifying Reusable Code Componentsp. 185
Documenting the Best Practicesp. 186
Documenting the Lessons Learnedp. 187
Collecting/Deriving and Depositing the Final Project Metrics in the Organizational Knowledge Repositoryp. 188
Conducting Knowledge-Sharing Meetings with Peer Software Project Managersp. 188
Depositing Project Records with the Project Management Officep. 189
Depositing Code Artifacts in the Code Repositoryp. 190
Conducting the Project Postmortemp. 190
Releasing the Software Project Managerp. 191
Closing the Projectp. 192
The Role of the Organization in Project Closurep. 192
The Project Management Officep. 192
The Configuration Control Boardp. 193
The Systems Administration Departmentp. 194
Referencep. 194
Agile Project Managementp. 195
Introductionp. 195
Project Management Rolesp. 195
Agile Project Management Characteristicsp. 196
Metaphorp. 197
Teamwork and Collaborationp. 197
Guiding Principlesp. 198
Open Informationp. 198
Use a Light Touchp. 199
Monitoring and Adjustmentp. 199
The Nuts and Bolts of Agile Project Managementp. 200
Planning the Workp. 200
Controlling the Workp. 202
Process Improvementp. 205
Referencep. 206
Pitfalls and Best Practices in Software Project Managementp. 207
Introductionp. 207
Organizational-Level Pitfalls and Best Practicesp. 208
Process-Driven Project Managementp. 208
An Ineffective Project Management Office or No Project Management Officep. 208
Poor Project Initiationp. 210
Poor Software Estimationp. 211
Poor Project Planningp. 211
The Wrong Service Level Agreementsp. 212
Poor Standards and Guidelines for Software Developmentp. 213
Poor Project Oversightp. 214
Inadequate Project Management Trainingp. 214
Software Project Manager-Level Pitfalls and Best Practicesp. 215
Fair Treatment of Project Human Resourcesp. 216
A Balanced Workloadp. 216
Equitable Rewardsp. 217
Poor Software Estimationp. 217
Poor Project Planningp. 217
Informal Issue Resolutionp. 217
Poor Change Managementp. 218
Poor Record Keepingp. 218
Additional Best Practices for Software Project Managementp. 219
A Knowledge Repositoryp. 219
Continuous Process Improvementp. 219
Project Postmortemsp. 219
Training in the Soft Skillsp. 220
Information Sharingp. 220
Management Supportp. 220
Some Closing Wordsp. 221
Management of Software Development Projectsp. 223
Decision-Making for Software Project Managersp. 237
People Managementp. 251
Productivity Concepts for Software Project Managersp. 271
Issue Resolution in Software Project Managementp. 287
Measurement and Metrics in Software Development Organizationsp. 295
Measurement and Management of Customer Satisfactionp. 315
An Introduction to PERT/CPMp. 327
Abbreviationsp. 347
Templates for Software Project Managersp. 351
Indexp. 373
Table of Contents provided by Ingram. All Rights Reserved.

An electronic version of this book is available through VitalSource.

This book is viewable on PC, Mac, iPhone, iPad, iPod Touch, and most smartphones.

By purchasing, you will be able to view this book online, as well as download it, for the chosen number of days.

Digital License

You are licensing a digital product for a set duration. Durations are set forth in the product description, with "Lifetime" typically meaning five (5) years of online access and permanent download to a supported device. All licenses are non-transferable.

More details can be found here.

A downloadable version of this book is available through the eCampus Reader or compatible Adobe readers.

Applications are available on iOS, Android, PC, Mac, and Windows Mobile platforms.

Please view the compatibility matrix prior to purchase.