
Building Software Teams
Ten Best Practices for Effective Software Development
O'Reilly Media · Print & ebook · January 17, 2017
Why does poor software quality continue to plague enterprises of all sizes in all industries?
We earn from qualifying purchases.
- Who it’s for
- Ten practices connect team process adjustments with measurable goals, testing, automation, and maintainable workflows.
- Themes
- Software development process improvement, Software quality and team practices, Development metrics and automation
- Genres
- Software Project Management, Testing & QA, Project Management
Nearest books
Matched by what the books are about, then ordered by what their readers also loved.
Clean CodeRobert C. Martin61% match
Lean Software DevelopmentMary Poppendieck, Tom Poppendieck68% matchShares Software Project Management and Project Management
Effective Software TestingMauricio Aniche67% matchShares Testing & QA
The Nature of Software DevelopmentRon Jeffries66% matchShares Software Project Management and Project Management
Release It!Michael Nygard, Michael T. Nygard65% matchShares Testing & QA
The Art of Agile DevelopmentJames Shore, Shane Warden65% matchShares Software Project Management and Testing & QA
Practice of System and Network Administration, theThomas A. Limoncelli, Christina J. Hogan65% match
Implementing Lean Software DevelopmentMary Poppendieck, Tom Poppendieck64% matchShares Software Project Management and Project Management
Start with three books, and this one can be the first.
Members get a new edition every morning: a route out from their books to essays, research and talks, with the reason for each.
Start with this bookAbout this book
Why does poor software quality continue to plague enterprises of all sizes in all industries? Part of the problem lies with the process, rather than individual developers. This practical guide provides ten best practices to help team leaders create an effective working environment through key adjustments to their process.
Continue reading
As a follow-up to their popular book, Building Maintainable Software, consultants with the Software Improvement Group (SIG) offer critical lessons based on their assessment of development processes used by hundreds of software teams. Each practice includes examples of goalsetting to help you choose the right metrics for your team. - Achieve development goals by determining meaningful metrics with the Goal-Question-Metric approach - Translate those goals to a verifiable Definition of Done - Manage code versions for consistent and predictable modification - Control separate environments for each stage in the development pipeline - Automate tests as much as possible and steer their guidelines and expectations - Let the Continuous Integration server do much of the hard work for you - Automate the process of pushing code through the pipeline - Define development process standards to improve consistency and simplicity - Manage dependencies on third party code to keep your software consistent and up to date - Document only the most necessary and current knowledge
Software Team Practices
Ten practices connect team process adjustments with measurable goals, testing, automation, and maintainable workflows.
Come here for
- Goal-Question-Metric goal setting for meaningful team metrics
- A verifiable Definition of Done
Expect
- Separate environments across development pipeline stages
- Automated testing and Continuous Integration support
Where it sits
| Software Project Management | 80% |
|---|---|
| Testing & QA | 60% |
| Project Management | 49% |
Percentages are BookFrontier’s reading of the book.
Publisher categories
- Software Development
- Testing & QA
- Software Project Management
- Authors
- Joost Visser, Sylvan Rigal, Gijs Wijnholds
- Publisher
- O'Reilly Media
- Published
- January 17, 2017
- Format
- Print & ebook
- Theme
- Software development process improvement · Software quality and team practices · Development metrics and automation
- Reading lane
- Software Development