Most modern software development projects require teams, and good teamwork largely determines a project’s success. The Team Software Process (TSP), created by Watts S. Humphrey, is a set of engineering practices and team concepts that produce effective teams, thereby helping developers deliver high-quality products on time and within budget. TSP bridges Humphrey’s seminal work on the Capability Maturity Model (CMM), an improvement framework for the entire software organization, and his Personal Software Process (PSP), practices designed to improve the work of individual developers. Typical first-time TSP teams increase productivity by more than 50 percent while greatly increasing the quality of their delivered products. However, TSP teams only continue to improve under the guidance of a capable coach. One industrial-strength team, for example, increased its productivity by an additional 94 percent and reduced test defects by 85 percent through three consecutive TSP quarterly product release cycles. Without competent coaching, teams often do not progress much beyond the initial one-time improvement seen after the introduction of the TSP. Humphrey distinguishes between TSP coaching and TSP leadership, explaining why the skillful performance of both functions is critical. In this practical guide, he shares coaching methods that have repeatedly inspired TSP teams and steered them toward success. With the help of a coach, TSP teams undergo a brief but intense project launch in which they define their own processes, make their own plans, and negotiate their commitments with management, resulting in dramatically enhanced performance. Whether you are considering the TSP or are actively implementing it, TSPSM–Coaching Development Teams provides the invaluable examples, guidelines, and suggestions you need to get started and keep developing as a team coach. It’s meant to complement Humphrey’s other books, TSPSM–Leading a Development Team and PSPSM: A Self-Improvement Process for Software Engineers. Together, the three works offer a rich resource for improving your software development capabilities.

A Lifetime of Invaluable Management Insights from Legendary Software Quality Guru Watts S. Humphrey In 1986, Watts S. Humphrey made an outrageous commitment: a promise to transform software development. As the pioneering innovator behind SEI's Capability Maturity Model (CMM), Personal Software Process (PSP), and Team Software Process (TSP), Humphrey has more than met that promise. But his contributions go beyond methodology: For decades, his deeply personal writings on project management have been admired by software engineers worldwide. Reflections on Management brings together Humphrey's best and most influential essays and articles--sharing insights that will be indispensable for anyone who must achieve superior results in software or any other endeavor. Collected here for the first time, these works offer compelling insights into everything from planning day-to-day work to improving quality, encouraging teamwork to becoming a truly great leader. All of these writings share a powerful vision, grounded by a life in software that has extended across nearly six decades. The vision is this: To succeed, professionals must effectively manage for more than plans, schedules, and code--they must manage teams, bosses, and above all, themselves.

Watts Humphrey, inventor of CMM, PSP, & TSP provides team leaders with a whole new way of leading an effective development team.

Watts Humphrey is the visionary behind the Capability Maturity Model (CMM)(R) and the Personal Software Process (PSP) (sm). The CMM contains a framework for software process improvement at the organizational level. The PSP builds the self-discipline needed for individual programmers to work efficiently and effectively. The author's new Team Software Process (TSP) (sm) details methods to guide the formation of software development teams, to motivate their work, and to enhance their productivity. This book describes an introductory version of TSP, ideal for smaller projects but also useful for learning basic techniques and procedures that apply to other development projects. Methods presented include: how to establish roles; how to conceive, design, and plan a project; how to track and report on progress. The book walks readers through a complete development cycle, illustrating: how best to use the talents at hand; how to formulate well-defined goals; how to coordinate activities for maximum progress; how to promote effective communication; how to alleviate many of the conflicts that undermine teamwork. Team members should not have to expend valuable time and energy reinventing ways to organize and run their team. By following a proven process, the team will more quickly be able to focus on the successful completion of the project itself. To help a team course apply these methods, the book provides two project exercises, with prescribed development goals and team roles.

Every business is a software business, and every business can profit from improved software processes Leadership, Teamwork, and Trust discusses the critical importance of knowledge work to the success of modern organizations. It explains concrete and necessary steps for reshaping the way in which software development, specifically, is conducted. A sequel to Humphrey's influential Winning with Software, this book presents new and copious data to reinforce his widely adopted methods for transforming knowledge work into a significant and sustainable competitive advantage, thereby realizing remarkable returns. Humphrey addresses here the broader business community--executives and senior managers who must recognize that today, every business is a software business.

This volume constitutes the refereed proceedings of the 24th EuroSPI conference, held in Ostrava, Czech Republic, in September 2017.The 56 revised full papers presented were carefully reviewed and selected from 97 submissions. They are organized in topical sections on SPI and VSEs, SPI and process models, SPI and safety, SPI and project management, SPI and implementation, SPI issues, SPI and automotive, selected key notes and workshop papers, GamifySPI, SPI in Industry 4.0, best practices in implementing traceability, good and bad practices in improvement, safety and security, experiences with agile and lean, standards and assessment models, team skills and diversity strategies.

This volume constitutes the refereed proceedings of the 23rd EuroSPI conference, held in Graz, Austria, in September 2016.The 15 revised full papers presented together with 14 selected key notes and workshop papers were carefully reviewed and selected from 51 submissions. They are organized in topical sections on SPI and the ISO/IEC 29110 standard; communication and team issues in SPI; SPI and assessment; SPI in secure and safety critical environments; SPI initiatives; GamifySPI; functional safety; supporting innovation and improvement.

“I’m an enthusiastic supporter of the CERT Secure Coding Initiative. Programmers have lots of sources of advice on correctness, clarity, maintainability, performance, and even safety. Advice on how specific language features affect security has been missing. The CERT ® C Secure Coding Standard fills this need.” –Randy Meyers, Chairman of ANSI C “For years we have relied upon the CERT/CC to publish advisories documenting an endless stream of security problems. Now CERT has embodied the advice of leading technical experts to give programmers and managers the practical guidance needed to avoid those problems in new applications and to help secure legacy systems. Well done!” –Dr. Thomas Plum, founder of Plum Hall, Inc. “Connectivity has sharply increased the need for secure, hacker-safe applications. By combining this CERT standard with other safety guidelines, customers gain all-round protection and approach the goal of zero-defect software.” –Chris Tapp, Field Applications Engineer, LDRA Ltd. “I’ve found this standard to be an indispensable collection of expert information on exactly how modern software systems fail in practice. It is the perfect place to start for establishing internal secure coding guidelines. You won’t find this information elsewhere, and, when it comes to software security, what you don’t know is often exactly what hurts you.” –John McDonald, coauthor of The Art of Software Security Assessment Software security has major implications for the operations and assets of organizations, as well as for the welfare of individuals. To create secure software, developers must know where the dangers lie. Secure programming in C can be more difficult than even many experienced programmers believe. This book is an essential desktop reference documenting the first official release of The CERT® C Secure Coding Standard. The standard itemizes those coding errors that are the root causes of software vulnerabilities in C and prioritizes them by severity, likelihood of exploitation, and remediation costs. Each guideline provides examples of insecure code as well as secure, alternative implementations. If uniformly applied, these guidelines will eliminate the critical coding errors that lead to buffer overflows, format string vulnerabilities, integer overflow, and other common software vulnerabilities.

Delivering successful projects means the ability to produce high quality software within budget and on time-consistently, but when one mentions quality to software engineers or project managers, they talk about how impossible it is to eliminate defects from software. This assumption is passed on and on until it becomes accepted wisdom, with the power of a self-fulfilling prophecy. And when a project fails to arrive on time or up to standards, team members will turn on each other. The project got delayed because the engineers did a poor job in development or too much was promised upfront for this short of a timeline. In Delivering Successful Projects with TSPSM and Six Sigma: A Practical Guide to Implementing Team Software ProcessSM, you will learn how to effectively manage the development of a software project and deliver it in line with customer expectations. This refreshing volume - Offers real-world case studies about the author's experience at Microsoft successfully implementing TSP to achieve higher quality software Empowers software developers to take responsibility for project management Explains how Six Sigma and TSP combined can dramatically reduce software defects By applying these principles put forth by one of the most respected names in software development, your software team will learn how to function as a team and turn out products where zero defects and on-time delivery are the norm.

An indispensable addition to any project manager, software engineering or computer science bookshelf, this book presents the only broad-ranging economic analysis of major international SPI methods and the first large-scale economic analysis of mandatory U.S. government standards.