This is the digital version of the printed book (Copyright © 1996).
Written in a remarkably clear style, Creating a Software Engineering Culture presents a comprehensive approach to improving the quality and effectiveness of the software development process.
In twenty chapters spread over six parts, Wiegers promotes the tactical changes required to support process improvement and high-quality software development. Throughout the text, Wiegers identifies scores of culture builders and culture killers, and he offers a wealth of references to resources for the software engineer, including seminars, conferences, publications, videos, and on-line information.
With case studies on process improvement and software metrics programs and an entire part on action planning (called “What to Do on Monday”), this practical book guides the reader in applying the concepts to real life.
Topics include software culture concepts, team behaviors, the five dimensions of a software project, recognizing achievements, optimizing customer involvement, the project champion model, tools for sharing the vision, requirements traceability matrices, the capability maturity model, action planning, testing, inspections, metrics-based project estimation, the cost of quality, and much more!
Principles from Part 1
Never let your boss or your customer talk you into doing a bad job.
People need to feel the work they do is appreciated.
Ongoing education is every team member’s responsibility.
Customer involvement is the most critical factor in software quality.
Your greatest challenge is sharing the vision of the final product with the customer.
Continual improvement of your software development process is both possible and essential.
Written software development procedures can help build a shared culture of best practices.
Quality is the top priority; long-term productivity is a natural consequence of high quality.
Strive to have a peer, rather than a customer, find a defect.
A key to software quality is to iterate many times on all development steps except coding: Do this once.
Managing bug reports and change requests is essential to controlling quality and maintenance.
If you measure what you do, you can learn to do it better.
You can’t change everything at once. Identify those changes that will yield the greatest benefits, and begin to implement them next Monday.
Do what makes sense; don’t resort to dogma.
Table of contents
- About This eBook
- Title Page
- Copyright Page
- Also Available from DORSET HOUSE
- Dedication Page
- Permissions Acknowledgments
- Figures and Tables
Part I: A Software Engineering Culture
- Chapter 1. Software Culture Concepts
- Chapter 2. Standing On Principle
- Chapter 3. Recognizing Achievements Great and Small
- Chapter 4. So Much to Learn, So Little Time
Part II: In Search of Excellent Requirements
- Chapter 5. Optimizing Customer Involvement
- Chapter 6. Tools for Sharing the Vision
Part III: Improving Your Processes
- Chapter 7. Process Improvement Fundamentals
- Chapter 8. Process Improvement Case Study
- Chapter 9. Software Process Maturity
- Chapter 10. Software Development Procedures
Part IV: The Bug Stops Here
- Chapter 11. The Quality Culture
- Chapter 12. Improving Quality by Software Inspection
- Chapter 13. Structured Testing
Part V: Methods, Measures, and Tools
- Chapter 14. The CASE for Iteration
Chapter 15. Control Change Before It Controls You
- Benefits of a Problem Tracking System
- A Software Change Management Case Study
- The Software Change Control Board
- How Change Control Can Simplify Your Life
- Learning from Bug Detection Trends
- Proactive Failure Reporting
- Making Change Management Work in Your Culture
- Culture Builders and Killers
- References and Further Reading
- Chapter 16. Taking Measures to Stay on Track
- Chapter 17. Case Study: Measurement in a Small Software Group
- Chapter 18. If It Makes Sense, Do It
- Part VI: What to Do on Monday
- Appendix A. Sources for Continued Software Learning
- Appendix B. Contact Information for Selected Resources
- Author Index
- Subject Index
- Reviewers’ Comments and Praise for CREATING A SOFTWARE ENGINEERING CULTURE by Karl E. Wiegers
- Title: Creating a Software Engineering Culture
- Release date: July 2013
- Publisher(s): Addison-Wesley Professional
- ISBN: 9780133489279
You might also like
Technology Strategy Patterns
Technologists who want their ideas heard, understood, and funded are often told to speak the language …
Inclusive Design for a Digital World: Designing with Accessibility in Mind
What is inclusive design? It is simple. It means that your product has been created with …
Semantic Software Design
With this practical book, architects, CTOs, and CIOs will learn a set of patterns for the …
Managing Humans: Biting and Humorous Tales of a Software Engineering Manager, Third Edition
Read hilarious stories with serious lessons that Michael Lopp extracts from his varied and sometimes bizarre …