Summer Reading Sale
 
 

Recently Viewed clear list


Original Essays | July 22, 2014

Nick Harkaway: IMG The Florist-Assassins



The three men lit up in my mind's eye, with footnotes. They were converging on me — and on the object I was carrying — in a way that had... Continue »
  1. $18.87 Sale Hardcover add to wish list

    Tigerman

    Nick Harkaway 9780385352413

spacer
Qualifying orders ship free.
$109.50
New Trade Paper
Ships in 1 to 3 days
Add to Wishlist
available for shipping or prepaid pickup only
Available for In-store Pickup
in 7 to 12 days
Qty Store Section
2 Remote Warehouse Software Engineering- General

Quality Software Project Management (Software Quality Institute Series)

by

Quality Software Project Management (Software Quality Institute Series) Cover

 

Synopses & Reviews

Publisher Comments:

The practical handbook of software project management-by practitioners, for practitioners!

Quality Software Project Management is the practical, start-to-finish project management resource for every software professional-experienced managers and developers moving into leadership roles. Drawing on best practices identified at The University of Texas at Austin Software Quality Institute's successful Software Project Management Certificate Program, it identifies 34 key competencies every project manager can use to minimize cost, risk, and time-to-market. Written by leading practitioners, it addresses all three pillars of any successful software venture: process, project, and people.

  • Integrates best practices from the fields of quality, software engineering, and project management
  • Shows how to tailor best practices to the unique requirements of your projects
  • Covers the entire project lifecycle: planning, initiation, execution, monitoring/control, and closing
  • Illuminates its techniques with real-world software management case studies
  • Offers a solid foundation for pursuing advanced certifications such as the Project Management Institute's Project Management Professional (PMP(r)) and the American Society for Quality's Certified Software Quality Engineer (CSQE)

Endorsed by the Software Quality Institute (SQI), Quality Software Project Management teaches skills you can use right now to drive maximum business value in any project-large or small.

Contains practical checklists, templates, and forms-all downloadable from the book's companion Web site

Practical checklists, templates, forms—all downloadable from the book's companion Web Site: http://stealthis.athensgroup.com/QSPM

Book News Annotation:

Written for software developers preparing to become project managers, this book presents the product development techniques, project management skills, and people management skills necessary to manage a software project. The authors focus on the concept of the software life cycle to represent the sequence of events that occur in software development, and describe several software life cycle models from which a project manager may choose. Topics include estimating duration and cost, defining the software requirement specification, and selecting the project team.
Annotation c. Book News, Inc., Portland, OR (booknews.com)

Synopsis:

Drawing on best practices identified at the Software Quality Institute and embodied in bodies of knowledge from the Project Management Institute, the American Society of Quality, IEEE, and the Software Engineering Institute, Quality Software Project Management teaches 34 critical skills that allow any manager to minimize costs, risks, and time-to-market. Written by leading practitioners Robert T. Futrell, Donald F. Shafer, and Linda I. Shafer, it addresses the entire project lifecycle, covering process, project, and people. It contains extensive practical resources-including downloadable checklists, templates, and forms.

Synopsis:

The most comprehensive book available on software project management, this book presents the product development techniques, project management skills, and people management skills necessary to manage a software project. With a process-oriented approach that is consistent with the A Guide to the Project Management Body of Knowledge (PMBOK(R) Guide)--2000 Edition, this book focuses on the concept of the software life cycle to represent the sequence of events that occur in software development, and describes several software development, and describes several software life cycle models from which a project manager may choose.

About the Author

ROBERT T. FUTRELL is a consultant for Project Management Systems in Austin, TX, specializing in project management and software quality engineering. He was formerly a software project manager for Texas Instruments, and currently works as a Program Management Master and controller at Motorola in Austin.

DONALD F. SHAFER is co-founder and CTO of Athens Group Inc., a consultingfirm specializing in integrating technology strategy and software solutions.He is also an adjunct professor at Southwest Texas State University and hasworked for Boeing, Los Alamos National Laboratories, and Motorola.

LINDA I. SHAFER is an instructor and the mentor for the Software Quality Institute's Software Project Management Certificate Program at The University of Texas at Austin. She has worked for Motorola, IBM, leading consultancies, and major universities.

Table of Contents

Contents.

Foreword.

Preface.

Using the Guide as a Course Text.

Acknowledgements.

1. Introduction.

Introduction to the 34 Competencies. Surveying the Foundations. Some Other Useful Definitions. Product Development Techniques. Project Management Skills. Summary. Problems for Review. Citations.

2. A Case in Point.

Background Information on the Chinese Railway System. Railroad Building in China. Chinese Business Environment. Project Description. A Final Note: Potential Market for Software. Citations. Web Pages for Further Information.

3. Process Overview.

Key Chapter 3 Points. Where We Are in the Product Development Life Cycle. Chapter 3. Relation to the 34 Competencies. Learning Objectives for Chapter 3. SEI CMM Level 3 Is the Defined Level. IEEE 1074-Process Map for Software Life Cycle Process. Customized Software Development Process. Software Project Management Organization Life Cycle. Summary. Problems for Review. Visit the Case Study. Citations. References. Web Pages for Further Information.

4. Selecting Software Development Life Cycles.

Where We Are in the Product Development Life Cycle. Chapter 4 Relation to the 34 Competencies. Learning Objectives for Chapter 4. What Is a Software Development Life Cycle? Why Are Software Development Life Cycles Important? Selection and Tailoring of Software Development Life Cycles. Is a Quality Objective. The SEI CMM and the Life Cycle. International Organization for Standardization (ISO)/IEC 12207. Software Development Life Cycle Models. Selecting an Appropriate Software Development Life Cycle Model. Customizing the Life Cycle Model. Summary. Problems for Review. Visit the Case Study. Citations. References. Web Pages for Further Information.

5. Managing Domain Processes.

Where We Are in the Product Development Life Cycle. Chapter 5 Relation to the 34 Competencies. Learning Objectives for Chapter 5. Defining the Process Domain. Project Selection Models. Project Portfolio Management. Understanding Financial Processes. Summary. Problems for Review. Visit the Case Study. Citations. Web Pages for Further Information.

6. Selecting a Project Team.

Where We Are in the Product Development Life Cycle. Chapter 6 Relation to the 34 Competencies. Learning Objectives for Chapter 6. Selecting a Project Team. The Whole Is the Sum of the Parts. Parts Need to Work Together. Working Together Requires a Framework. Providing the Total Solution. Summary. Problems for Review. Visit the Case Study. Citations. Suggested Readings. Web Pages for Further Information.

7. Defining the Goal and Scope of the Software Project.

Where We Are in the Product Development Life Cycle. Chapter 7 Relation to the 34 Competencies. Learning Objectives for Chapter 7. Project Planning. What Is “The Goal”? What Is the Scope of Work? Project Charter. The Software Project Management Plan. Summary. Problems for Review. Visit the Case Study. Citations. Suggested Readings. Web Pages for Further Information.

Creating the Work Breakdown Structure.

Where We Are in the Product Development Life Cycle. Chapter 8 Relation to the 34 Competencies. Learning Objectives for Chapter 8. What Is a Work Breakdown Structure? Approaches to Building a WBS. Defining Project Milestones. Creating Work Packages. Building a WBS for Software. Summary. Problems for Review. Visit the Case Study. Suggested Readings. Web Pages for Further Information.

9. Identifying the Tasks and Activities.

Where We Are in the Product Development Life Cycle. Chapter 9 Relation to the 34 Competencies. Learning Objectives for Chapter 9. Characteristics of Tasks and Activities. The Activity ID Process. Summary. Problems for Review. Visit the Case Study. References. Web Pages for Further Information.

10. Software Size and Reuse Estimating.

Where We Are in the Product Development Life Cycle. Chapter 10 Relation to the 34 Competencies. Learning Objectives for Chapter 10. The SEI CMM and Estimating. Problems and Risks with Estimating Software Size. Getting Started with Software Sizing: Estimating Begins with Planning. The Effects of Reuse on Software Size. Summary. Problems for Review. Visit the Case Study. Citations. Suggested Readings. Web Pages for Further Information.

11. Estimating Duration and Cost.

Where We Are in the Product Development Life Cycle. Chapter 11 Relation to the 34 Competencies. Learning Objectives for Chapter 11. The SEI CMM and Estimating. Effort Measures. The Steps in Estimating. COCOMO: A Regression Model. COCOMO II. SLIM: A Mathematical Model. Summary. Problems for Review. Visit the Case Study. Citations. References. Suggested Readings. Web Pages for Further Information.

12. Assigning Resources.

Where We Are in the Product Development Life Cycle. Chapter 12 Relation to the 34 Competencies. Learning Objectives for Chapter 12. Organizational Planning. Identifying and Documenting the Project Roles and Skills Needed. Assigning Responsibilities to Individuals. Establishing Reporting Relationships. Project Management Resource Activities During Execution. Summary. Problems for Review. Visit the Case Study. Suggested Readings. Web Pages for Further Information.

13. Choosing an Organizational Form.

Where We Are in the Product Development Life Cycle. Chapter 13 Relation to the 34 Competencies. Learning Objectives for Chapter 13. What Is an Organization? Characteristics of an Organization. Organizational Structures. Implementing an Organizational Structure. Summary. Problems for Review. Visit the Case Study. Citations. References. Suggested Readings. Web Pages for Further Information.

14. Considering Dependencies.

Where We Are in the Product Development Life Cycle. Chapter 14 Relation to the 34 Competencies. Learning Objectives for Chapter 14. What Are Dependencies? Types of Software Development Dependencies. Brainstorming Dependencies and Activities. Summary. Problems for Review. Visit the Case Study. Suggested Readings. Web Pages for Further Information.

15. Scheduling the Work.

Where We Are in the Product Development Life Cycle. Chapter 15 Relation to the 34 Competencies. Learning Objectives for Chapter 15. Why Schedule? The Uncertainty of Scheduling the Future. Scheduling Fundamentals. PERT and CPM Scheduling. Leveling Resource Assignments. Map the Schedule to a Real Calendar. Critical Chain Scheduling. Complete Process for Building a Real Schedule. Summary. Problems for Review. Visit the Case Study. Citations. Suggested Readings. Web Pages for Further Information.

16. Eliciting Requirements.

Where We Are in the Product Development Life Cycle. Chapter 16 Relation to the 34 Competencies 506. Learning Objectives for Chapter 16. Background for Requirements Management. Requirements Management and the SEI CMM. Critical Success Factors as Applied to Software Requirements. What Is a Software Requirement? What Makes a “Good” Software Requirement? Requirements Elicitation Methods. Guidelines for Writing Quality Requirements. Challenges in Eliciting Requirements. Requirements and Quality Function Deployment. Summary. Problems for Review. Visit the Case Study. Citations. Suggested Readings. Web Pages for Further Information.

17. Developing the Software Requirements Specification.

Where We Are in the Product Development Life Cycle. Chapter 17 Relation to the 34 Competencies. Learning Objectives for Chapter 17. Questions the SRS Answers for a Project. Benefits of an SRS. Building the SRS. Evaluating the Project SRS. Degree of Stability. Degree of Necessity. Verifiability. Modifiability. Traceability. Some Final Hints. Summary. Problems for Review. Visit the Case Study. Citations. References. Web Pages for Further Information.

18. Determining Project Risks.

Where We Are in the Product Development Life Cycle. Chapter 18 Relation to the 34 Competencies. Learning Objectives for Chapter 18. What Is Risk Management? Risk Management Models. Project Risk and the SEI. Identifying Risks. Analyzing and Quantifying Risks. Developing and Controlling Risks. Risk Categories. Steps in Developing a Risk Management Plan. Summary. Problems for Review. Visit the Case Study. Citations. Web Pages for Further Information. Risk Management Tools. References.

19. Introduction to Software Engineering.

Where We Are in the Product Development Life Cycle. Chapter 19 Relation to the 34 Competencies. Learning Objectives for Chapter 19. Software, Engineering, and Software Engineering. Software Engineering Body of Knowledge. SWEBOK and the SEI CMM. SWEBOK and the 34 Software Project Management Competencies. SWEBOK and Quality Software Project Management. Summary. Problems for Review. Visit the Case Study. Citations. Web Pages for Further Information. Suggested Readings.

20. Reliability.

Where We Are in the Product Development Life Cycle. Chapter 20 Relation to the 34 Competencies. Learning Objectives for Chapter 20. Software Reliability Terminology. Fault Forecasting. Fault Prevention. Fault Removal. Fault Tolerance. Reliability Tools. Software Reliability Plan. Summary. Problems for Review. Visit the Case Study. Citations. Standards. Web Pages for Further Information. Tools. Suggested Readings.

21. Software Metrics.

Where We Are in the Software Life Cycle. Chapter 21 Relation to the 34 Competencies. Learning Objectives for Chapter 21. What Is a Metric? The Importance of Metrics to Software Projects. Metrics and the SEI CMM. SEI CMM Level 2: Repeatable. SEI CMM Level 3: Defined. SEI CMM Level 4: Managed. Useful Metrics. The Basili Goal/Question/Metric Paradigm. A "Basic Metrics" Starter Set. Measuring Aspects of Software Quality. The Metrics Plan. Summary. Problems for Review. Visit the Case Study. Citations. Suggested Readings. Web Pages for Further Information.

22. Analysis and Design Methods.

Where We Are in the Product Development Life Cycle. Chapter 22 Relation to the 34 Competencies. Learning Objectives for Chapter 22. Analysis and Design and the SEI CMM. Structured Analysis/Structured Design (SA/SD). Object-Oriented Analysis/Object-Oriented Design (OOA/OOD). Summary. Problems for Review. Visit the Case Study. Citations. Suggested Readings. Web Pages for Further Information.

23. Validation and Verification.

Reviews, Inspections, and Walkthroughs. Testing. Where We Are in the Product Development Life Cycle. Chapter 23 Relation to the 34 Competencies. Learning Objectives for Chapter 23. Static Testing: Reviews. Dynamic Testing. Directed Flow Graph: McCabe Cyclomatic Complexity Analysis. User Acceptance and Usability Testing. The Ideal Test Coverage. Dynamic Testing: Measurement, Reporting, and Decision Making. Object-Oriented Testing. Summary of Dynamic Testing. Summary. Problems for Review. Visit the Case Study. Citations. Suggested Readings. Web Pages for Further Information.

24. Use of Tools.

Where We Are in the Product Development Life Cycle. Learning Objectives for Chapter 24. Software Requirements Tools. Software Design Tools. Software Construction Tools. Software Testing Tools. Software Maintenance Tools. Software Configuration Management Tools-CMM Level 2 and Above. Software Engineering Life Cycle Process Tools. Software Engineering Process Tools. Software Quality Tools. Software Engineering Management Tools. Infrastructure Support Tools. Miscellaneous Tools Issues. Minimal Tool Sets. Summary. Problems for Review. Visit the Case Study. Citations. Tools. Web Pages for Further Information. References.

25. Project Tracking and Control.

Where We Are in the Product Development Life Cycle. Chapter 25 Relation to the 34 Competencies. Learning Objectives for Chapter 25. Control Systems. Scope Management. Schedule Management. Cost Management. Quality Management. Progress Management. Risk Management. Summary. Problems for Review. Visit the Case Study. Suggested Readings. Web Pages for Further Information.

26. Continuous Process Improvement.

Where We Are in the Product Development Life Cycle. Chapter 26 Relation to the 34 Competencies. Learning Objectives for Chapter 26. Maturity Level Process Characteristics. Waste in the Software Development Organization. Six-Step Software Development Process Improvement Model. Applying the Software Development Process Improvement Model. Summary. Problems for Review. Visit the Case Study. Citations. Tools. Web Pages for Further Information. Suggested Readings.

27. Project Termination.

Where We Are in the Product Development Life Cycle. Chapter 27 Relation to the 34 Competencies. Learning Objectives for Chapter 27. Why Terminate? Types of Termination. What to Do upon Project Termination. Termination Process. Summary. Problems for Review. Visit the Case Study. Citations. Suggested Readings. Web Pages for Further Information.

28. Post-Performance Analysis.

Where We Are in the Product Development Life Cycle.

Chapter 28 Relation to the 34 Competencies. Learning Objectives for Chapter 28. What's in a Name? How to Conduct a PPA. Summary. Problems for Review. Visit the Case Study. Citations. Suggested Readings. Web Pages for Further Information.

29. Reporting and Communicating.

Where We Are in the Product Development Life Cycle. Chapter 29 Relation to the 34 Competencies. Learning Objectives for Chapter 29. Effective Communication. Communication Techniques. Communicating with Teams. Communication and Motivation Skills of a Software Project Manager. Behavioral Theory and Motivation. Project Manager Behavior That Motivates. Communicating in Meetings. Communicating via Negotiation. Negotiating and Culture. Communicating via Visual Expression of Information. Reporting Project Status. Communications Management Plan Template. Baseline Plans. Project Reporting. Summary. Problems for Review. Visit the Case Study. Citations. Suggested Readings. Web Pages for Further Information.

30. Software Quality Assurance.

Where We Are in the Product Development Life Cycle. Chapter 30 Relation to the 34 Competencies. Learning Objectives for Chapter 30. Building the Software Quality Assurance Plan. Ensuring the SQAP. Summary. Problems for Review. Visit the Case Study. References. Web Pages for Further Information.

31. Software Configuration Management.

What Is Software Configuration Management? Why Is SCM Important? Who Is Involved in SCM? How Can Software Configuration Be Implemented in Your Organization? Where We Are in the Product Development Life Cycle. Chapter 31 Relation to the 34 Competencies. Learning Objectives for Chapter 31. SCM Principles. The Four Basic Requirements for an SCM System. Planning and Organizing for SCM. SCM Tools. Benefits of SCM Process and Tools. Some Problems with Software. Summary. Problems for Review. Visit the Case Study. Citations. References. Web Pages for Further Information.

32. Legal Issues in Software.

Where We Are in the Product Development Life Cycle. Chapter 32 Relation to the 34 Competencies. Learning Objectives for Chapter 32. Product Development Techniques. Project Management Skills. People Management Skills. Legal Risk Issues. Summary. Problems for Review. Visit the Case Study. Web Pages for Further Information. Suggested Readings.

Summary.

Product Development Techniques. Project Management Skills. People Management Skills. Visit the Case Study.

Supporting Organizations. Appendix A Relation to the 34 Competencies. Key Appendix A Points. Organizations Supporting Software Development. Project Management. State and Local Quality Organizations and Awards. Visit the Case Study. Web Pages for Further Information.

Real World Projects.

Case 1: Managing a Portfolio of Client Projects. Hardware Tester Company Projects. Case 2: COTS Software Selection for Information Technology Systems. Case 3: Legacy Software Re-engineering. Problems for Review. Visit the Case Study.

Creating the Business Plan.

The Technology Business Plan as the Company's Meta-Plan. What Is the Technology Business Plan? Why Build a Technology Business Plan? Technology Business Plan Contents. Making the Business Case Cost Benefit Analysis in a Technology Business Plan. Problems for Review. Visit the Case Study. Web Pages for Further Information.

Understanding Systems Engineering.

Where We Are in the Project Management Life Cycle. Learning Objectives for Appendix D. Classical Systems Engineering Model. Requirements Engineering. Types of Product Systems. Problems for Review. Visit the Case Study. References. Web Pages for Further Information. Tools.

Distance Project Management.

Where We Are in the Product Development Life Cycle. Learning Objectives for Appendix E. Managing Distance Projects-Communications. Managing Distance Projects-Remote Teambuilding. Managing Distance Projects-Tools. A Case in Point-Quorus(tm). Ten Commandments of Managing a Remote Project Team. Problems for Review. Visit the Case Study. Citations. Web Pages for Further Information.

Project Artifact Templates.

Where We Are in the Product Development Life Cycle. Learning Objectives for Appendix F. Software Project Management Plan (SPMP). Software Requirements Specification (SRS). Project Risk Management Plan. Software Test Plan. Software Configuration Management Plan (SCMP). References. Web Pages for Further Information.

Joint Application Design in Use.

What the Team Did Right. What the Team Would Change Next Time. JAD Team Documents. Final JAD Documents.

Glossary.

Quality Engineering Glossaries. Software Engineering Glossaries. Project Management Glossaries. Quality Software Project Management. Practitioner's Glossary.

Bibliography.

Print Bibliography. Web Pages for Further Information.

Index.

Product Details

ISBN:
9780130912978
Author:
Futrell, Robert T.
Author:
Shafer, Donald F.
Author:
Shafer, Linda Isabell
Author:
Shafer, Linda I.
Publisher:
Prentice Hall
Location:
Upper Saddle River, NJ
Subject:
Management
Subject:
Programming Languages - General
Subject:
Programming - General
Subject:
Programming - Software Development
Subject:
Computer software
Subject:
Software Development & Engineering - General
Subject:
Computer software -- Development -- Management.
Subject:
Software Engineering-General
Copyright:
Edition Description:
Trade paper
Series:
Software Quality Institute series
Series Volume:
7130
Publication Date:
January 2002
Binding:
TRADE PAPER
Grade Level:
Professional and scholarly
Language:
English
Illustrations:
Yes
Pages:
1680
Dimensions:
9.5 x 7.1 x 1.96 in 2270 gr

Other books you might like

  1. Peopleware: Productive Projects & Teams Used Trade Paper $18.95
  2. Software Requirements: Practical...
    Used Trade Paper $27.50
  3. Code Complete 2ND Edition
    Used Trade Paper $35.00
  4. Built to Last: Successful Habits of...
    Used Trade Paper $8.95
  5. Something in This Book is True Used Trade Paper $7.95
  6. You Are a Spiritual Being Having a... Used Trade Paper $9.50

Related Subjects

Computers and Internet » Computers Reference » General
Computers and Internet » Software Engineering » General
Computers and Internet » Software Engineering » Software Management
Engineering » Industrial and Control Engineering » General

Quality Software Project Management (Software Quality Institute Series) New Trade Paper
0 stars - 0 reviews
$109.50 In Stock
Product details 1680 pages Prentice Hall PTR - English 9780130912978 Reviews:
"Synopsis" by , Drawing on best practices identified at the Software Quality Institute and embodied in bodies of knowledge from the Project Management Institute, the American Society of Quality, IEEE, and the Software Engineering Institute, Quality Software Project Management teaches 34 critical skills that allow any manager to minimize costs, risks, and time-to-market. Written by leading practitioners Robert T. Futrell, Donald F. Shafer, and Linda I. Shafer, it addresses the entire project lifecycle, covering process, project, and people. It contains extensive practical resources-including downloadable checklists, templates, and forms.
"Synopsis" by , The most comprehensive book available on software project management, this book presents the product development techniques, project management skills, and people management skills necessary to manage a software project. With a process-oriented approach that is consistent with the A Guide to the Project Management Body of Knowledge (PMBOK(R) Guide)--2000 Edition, this book focuses on the concept of the software life cycle to represent the sequence of events that occur in software development, and describes several software development, and describes several software life cycle models from which a project manager may choose.

spacer
spacer
  • back to top
Follow us on...




Powell's City of Books is an independent bookstore in Portland, Oregon, that fills a whole city block with more than a million new, used, and out of print books. Shop those shelves — plus literally millions more books, DVDs, and gifts — here at Powells.com.