July 2013
Intermediate to advanced
384 pages
10h 56m
English
Overview
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.
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.