- Home
- Computers
- Software Development & Engineering
- Building Software Teams (Ten Best Practices for Effective Software Development)
Building Software Teams (Ten Best Practices for Effective Software Development)
- Availability: Confirm prior to ordering
- Branding: minimum 50 pieces (add’l costs below)
- Check Freight Rates (branded products only)
Branding Options (v), Availability & Lead Times
- 1-Color Imprint: $2.00 ea.
- Promo-Page Insert: $2.50 ea. (full-color printed, single-sided page)
- Belly-Band Wrap: $2.50 ea. (full-color printed)
- Set-Up Charge: $45 per decoration
- Availability: Product availability changes daily, so please confirm your quantity is available prior to placing an order.
- Branded Products: allow 10 business days from proof approval for production. Branding options may be limited or unavailable based on product design or cover artwork.
- Unbranded Products: allow 3-5 business days for shipping. All Unbranded items receive FREE ground shipping in the US. Inquire for international shipping.
- RETURNS/CANCELLATIONS: All orders, branded or unbranded, are NON-CANCELLABLE and NON-RETURNABLE once a purchase order has been received.
Product Details
Overview
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.
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








