Successful software depends not only on technical excellence but on how members of the software team work together. Written in easy to understand language by a leading expert in the field, this ground-breaking volume provides an overview of the team culture required to develop quality software. Reflecting the different views on the nature of software quality, the book helps groups in a software team to communicate more effectively and to overcome the conflict created by their different perceptions of quality. You learn the roles and activities of team members (including customers) throughout the life of a software product, from before the software development starts and during the software development lifecycle, to after the software has been deployed and is in use.

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 book examines how and why collaborative quality assurance techniques, particularly pair programming and peer code review, affect group cognition and software quality in agile software development teams. Prior research on these extremely popular but also costly techniques has focused on isolated pairs of developers and ignored the fact that they are typically applied in larger, enduring teams. This book is one of the first studies to investigate how these techniques depend on and influence the joint cognitive accomplishments of entire development teams rather than individuals. It employs theories on transactive memory systems and functional affordances to provide answers based on empirical research. The mixed-methods research presented includes several in-depth case studies and survey results from more than 500 software developers, team leaders, and product managers in 81 software development teams. The book’s findings will advance IS research and have explicit implications for developers of code review tools, information systems development teams, and software development managers.

More software engineers are likely to work in a globally distributed environment, which brings benefits that include quick and better software development, less manpower retention, scalability, and less software development cost and sharing of knowledge from the global pool of employees. However, these work environments also introduce a physical separation between team members and project leaders, which can create problems in communication and ultimately lead to the failure of the project. Human Factors in Global Software Engineering is a collection of innovative research focusing on the challenges, issues, and importance of human factors in global software engineering organizations in order to help these organizations better manage their manpower and provide an appropriate culture and technology in order to make their software development projects successful. While highlighting topics including agile software, knowledge management, and human-computer interaction, this book is ideally designed for project managers, administrators, business professionals, researchers, practitioners, students, and academicians.

Each industry, from robotics to health care, power generation to software, has its own tailored reliability and quality principles, methods, and procedures. This book brings these together so that reliability and quality professionals can more easily learn about each other's work, which may help them, directly or indirectly, to perform their tasks more effectively.

This book constitutes the refereed proceedings of the 8th International Conference on Product Focused Software Process Improvement, PROFES 2007, held in Riga, Latvia in July 2007. The 29 revised full papers presented together with 4 reports on workshops and tutorials and 4 keynote addresses were carefully reviewed and selected from 55 submissions. The papers constitute a balanced mix of academic and industrial aspects; they are organized in topical sections on global software development, software process improvement, software process modeling and evolution, industrial experiences, agile software development, software measurement, simulation and decision support, processes and methods.

Are you an architect? Scrum Master? team leader? project manager? If you are any of these, you will find that leadership, done right, is a very tough job. This book deals with the hard parts. Not with tools, but with people. Here is the manifesto that drives this book: For us as team leaders, the goal and the way we measure our work is the overall growth in skills of self-organization and self-maintenance in each member of our team and the team as a whole. To that end: We accept that the team's needs from us change continuously based on their skills for handling the current reality of work, so we embrace a continuously changing leadership style over a one-style-fits-all leadership approach. We believe in challenging ourselves and our teams to always get better, so: * We create slack time for the team to learn and be challenged. * We embrace taking risks for our team over staying safe. * We embrace fear and discomfort while learning new skills over keeping people within their comfort zone. * We embrace experimentation as a constant practice over maintaining the status quo: * With people * With tools * With processes * With the environment * We believe our core practice is leading people, not wielding machines, so: * We embrace spending more time with our team than in meetings. * We embrace treating software problems as people problems. * We learn people skills and communication techniques. About the notes The second part of this book allows a peek into the minds of some of the best leaders, consultants, and managers as they give advice to a new team leader. Hear from Johanna Rothman, Kevlin Henney, Dan North, Uncle Bob Martin, and many others about the one thing they would like to teach you if you ever become a team leader, Scrum Master, project manager, or architect.

For over 20 years, this has been the best-selling guide to software engineering for students and industry professionals alike. This seventh edition features a new part four on web engineering, which presents a complete engineering approach for the analysis, design and testing of web applications.

This Proceedings contains many research and practical papers dealing with the impact and influence of information technology on the global economy.

This book records the author’s years of experience in the software industry. In his own practices, the author has found that the distributed work pattern has become increasingly popular in more and more work environments, either between vendors and customers or between different teams inside a company. This means that all practitioners in the software industry need to adapt to this new way of communication and collaboration and get skilled enough to meet the greater challenges in integrating the distributed work pattern with agile software delivery. By centering on the difficulties in communication and collaboration between distributed teams, this book digs into the reasons why so many remote delivery projects end up anticlimactic and provides solutions for readers’ reference. It also cites successful cases in promoting agile development in distributed teams, which has been a vexing problem for many software development companies. In addition, readers can find suggestions and measures for building self-managing teams in this book. Remote Delivery: A Guide to Software Delivery through Collaboration between Distributed Teams is a very practical guide for software delivery teams with their members distributed in different places and companies engaged in software customization. Developers, QAs, product managers, and project leaders can also be inspired by this book.