
Architecture-Centric Software Project Management
A Practical Guide
Résumé
Written for project managers and software architects, Architecture-Centric Software Project Management demonstrates how to draw on software architecture to design schedules, generate estimates, make scope decisions, and manage the team for a successful outcome. The book addresses each cornerstone of effective project management—planning, organizing, implementing, and measuring.
Daniel Paulish provides a wealth of practical, experience-based advice on such topics as:
- Using architecture to define project organization
- Developing realistic schedules
- Using global analysis for project and test planning
- Managing expectations and deciding when to commit
- Building a project culture and an effective team
- Managing tradeoffs and making project decisions
- Risk management and avoiding unpleasant surprises
- Defining project success
- Using architecture for global development
In addition, real-world case studies illuminate all of the book's strategies, approaches, and techniques. These case studies help the reader fully comprehend the challenges and struggles inherent in software development, and demonstrate how common obstacles can be more easily avoided using an architecture-centr
Contents
Preface.
I. MOTIVATION.
1. Motivation.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.
Approach.
Benefits.
Experience.
Rules of Thumb.
Summary.
3. Global Analysis.
Global Analysis Activities.
Using GA for Project Planning.
Using GA for Test Planning.
Benefits.
4. Managing Expectations.
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.
Architectures for SupportingGlobal Development.
Development Processes for Global Development.
Multicultural Variables.
Recommendations for Global Development Teams.
Conclusions.
7. Building a Project Culture <38> Team.
Characteristics of Good Teams.
Building a Project Culture.
Building Consensus.
Setting the Amount of Direction.
Summary.
8. The Role of the Software Project Manager.
Coaching.
Making Decisions.
Coordinating.
Working with Your Project Team.
Software Project Management as a Career.
Summary.
IV. IMPLEMENTING.
9. Tradeoffs <38> Project 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.
Build Planning <38> Management.
Getting Everyone Involved.
Tracking Progress.
Incremental Testing.
Release Criteria Meeting.
Tooling.
Summary.
11. Creating Visibility <38> Avoiding Surprises.
Communicating Status and Issues.
Building Credibility with Management.
Recognizing and Celebrating Success.
Summary.
12. Staying Calm in the Heat of Battle.
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.
Phase Metrics for High-Level Design.
Cost-to-Completes.
Engineering Budgets.
Watching the Test Results.
Summary.
14. What is a “Good Job” ?
Defining Project Success.
Measuring Team Member's Contributions.
Rewards.
Staff Turnover.
Summary.
VI. CASE STUDIES.
15. IS2000.
System Overview.
Project Planning.
Project Management.
Lessons Learned.
16. DPS2000.
Global Analysis.
Product Line Design Strategies.
DPS2000 Architecture.
Project Planning.
Project Management.
Lessons Learned.
17. Conclusions.
Benefits.
Summary.
VII. APPENDIX.
Appendix - Forms.
Glossary.
Bibliography.
Index.
Caractéristiques techniques
PAPIER | |
Éditeur(s) | Addison Wesley |
Auteur(s) | Daniel J. Paulish |
Parution | 01/02/2002 |
Nb. de pages | 282 |
Format | 18,8 x 23,4 |
Couverture | Broché |
Poids | 650g |
Intérieur | Noir et Blanc |
EAN13 | 9780201734096 |
ISBN13 | 978-0-201-73409-6 |
Avantages Eyrolles.com
Nos clients ont également acheté
Consultez aussi
- Les meilleures ventes en Graphisme & Photo
- Les meilleures ventes en Informatique
- Les meilleures ventes en Construction
- Les meilleures ventes en Entreprise & Droit
- Les meilleures ventes en Sciences
- Les meilleures ventes en Littérature
- Les meilleures ventes en Arts & Loisirs
- Les meilleures ventes en Vie pratique
- Les meilleures ventes en Voyage et Tourisme
- Les meilleures ventes en BD et Jeunesse
- Informatique Informatique d'entreprise Gestion de projets
- Informatique Développement d'applications Gestion de projets
- Informatique Développement d'applications Modélisation et génie logiciel Tests et qualité logiciels
- Entreprise & Droit Management : efficacité du manager Manager - Gérer un projet
- Entreprise & Droit Management : efficacité du manager Manager - Animer une équipe
- Entreprise & Droit Management : efficacité du manager Communiquer - Gérer les conflits