Your textbook…
Architecture-Centric Software Project Management: A Practical Guide
ISBN-10: 0-201-73409-5
ISBN-13: 978-0-201-73409-6
Published by Addison-Wesley Professional
© 2002
Pub. Date: Dec 27, 2001
Format: Paper
Table of Contents
Preface.
I. MOTIVATION.
1. Motivation.
What is Project Management?
What is Software Architecture?
Core Beliefs.
Project Management Process.
Architecture-Centric Project Management.
Planning.
Organizing.
Implementing.
Measuring.
0 Summary.
II. PLANNING.
2. Architecture-Centered Software Project Planning.
Developing Realistic Schedules.
Approach.
Benefits.
Experience.
Rules of Thumb.
Summary.
3. Global Analysis.
What is Global Analysis?
Global Analysis Activities.
Using GA for Project Planning.
Using GA for Test Planning.
Benefits.
4. Managing Expectations.
When to Plan and When to Commit.
Managing Upward.
Managing Sideways.
Information Flow.
Using the Software Development Plan.
Summary.
III. ORGANIZING. Chapter 5: The Project Organization.
Using Software Architecture to Define the Project Organization.
Architecture Team Roles during Development.
Project Functions that Support Development.
Responsibilities, Roles, Authority, and Ownership.
Summary.
6. Global Development.
Why Global Development?
Architectures for Supporting Global Development.
Development Processes for Global Development.
Multicultural Variables.
Recommendations for Global Development Teams.
Conclusions.
7. Building a Project Culture <38> Team.
Establishing Project Goals.
Characteristics of Good Teams.
Building a Project Culture.
Building Consensus.
Setting the Amount of Direction.
Summary.
8. The Role of the Software Project Manager.
Creating a Vision.
Coaching.
Making Decisions.
Coordinating.
Working with Your Project Team.
Software Project Management as a Career.
Summary.
IV. IMPLEMENTING.
9. Tradeoffs <38> Project Decisions.
Using the Project Goals to Make Decisions.
Managing Creeping Functionality <38> Architecture Drift.
Taking Responsibility.
When to Accept or Reject Changes.
Ethical Decisions of the Project Manager.
Summary.
10. Incremental Development.
Baselining the Software Development Plan.
Build Planning <38> Management.
Getting Everyone Involved.
Tracking Progress.
Incremental Testing.
Release Criteria Meeting.
Tooling.
Summary.
11. Creating Visibility <38> Avoiding Surprises.
Risk Management.
Communicating Status and Issues.
Building Credibility with Management.
Recognizing and Celebrating Success.
Summary.
12. Staying Calm in the Heat of Battle.
Cheerleading, Micro-management, <38> Discipline.
Remaining Optimistic.
Playing the Quality Card.
Providing Support <38> Removing Obstacles.
Handling Problem Employees.
Emotions <38> Avoidance.
Quality of Work Life.
Summary.
V. MEASURING.
13. Measures to Pay Attention To.
Global Metrics for Project Managers.
Phase Metrics for High-Level Design.
Cost-to-Completes.
Engineering Budgets.
Watching the Test Results.
Summary.
14. What is a “Good Job”?
Trading off Schedule, Functionality, <38> Quality.
Defining Project Success.
Measuring Team Member's Contributions.
Rewards.
Staff Turnover.
Summary.
VI. CASE STUDIES.
15. IS2000.
Background.
System Overview.
Project Planning.
Project Management.
Lessons Learned.
16. DPS2000.
Background.
Global Analysis.
Product Line Design Strategies.
DPS2000 Architecture.
Project Planning.
Project Management.
Lessons Learned.
17. Conclusions.
Sharing Best Practices.
Benefits.
Summary.
VII. APPENDIX.
Appendix - Forms.
Glossary.
Bibliography.
Index.
