While modern project management systems support teams during planning and development activities, primarily through performance-related process information, the equally relevant human factors are often insufficiently considered for explaining team dynamics (e.g., the affect of moods in teams). However, understanding team behavioral patterns are crucial for the accurate planning and steady execution of development tasks throughout an ongoing project. A computer-aided feedback concept is described, unifying interdisciplinary foundations and methods from the software engineering, data science, organizational, and social psychology fields for disclosing team dynamics in agile software projects. The concept covers the systematic capture of sociotechnical data combined with descriptive, predictive, and exploratory model-based methods that support understanding behavioural changes during the development process. Design science from information systems research is used in academic and industrial case studies to conceptualize and operationalize the feedback methods into a practical Jira plugin. A concluding evaluation through an action research method in two industrial software projects results in quantitative and qualitative findings regarding the feedback utilization and utility during agile development processes (e.g., team communication changes related to accomplished performances). The case studies underscore the practical relevance for systematic feedback and the need to better understand human factors in software projects.

Managing risk is essential for every organization. However, significant opportunities may be lost by concentrating on the negative aspects of risk without bearing in mind the positive attributes. The objective of Project Risk Management: Managing Software Development Risk is to provide a distinct approach to a broad range of risks and rewards associated with the design, development, implementation and deployment of software systems. The traditional perspective of software development risk is to view risk as a negative characteristic associated with the impact of potential threats. The perspective of this book is to explore a more discerning view of software development risks, including the positive aspects of risk associated with potential beneficial opportunities. A balanced approach requires that software project managers approach negative risks with a view to reduce the likelihood and impact on a software project, and approach positive risks with a view to increase the likelihood of exploiting opportunities. Project Risk Management: Managing Software Development Risk explores software development risk both from a technological and business perspective. Issues regarding strategies for software development are discussed and topics including risks related to technical performance, outsourcing, cybersecurity, scheduling, quality, costs, opportunities and competition are presented. Bringing together concepts across the broad spectrum of software engineering with a project management perspective, this volume represents both a professional and scholarly perspective on the topic.

This open access book constitutes the proceedings of the 21st International Conference on Agile Software Development, XP 2020, which was planned to be held during June 8-12, 2020, at the IT University of Copenhagen, Denmark. However, due to the COVID-19 pandemic the conference was postponed until an undetermined date. XP is the premier agile software development conference combining research and practice. It is a hybrid forum where agile researchers, academics, practitioners, thought leaders, coaches, and trainers get together to present and discuss their most recent innovations, research results, experiences, concerns, challenges, and trends. Following this history, for both researchers and seasoned practitioners XP 2020 provided an informal environment to network, share, and discover trends in Agile for the next 20 years. The 14 full and 2 short papers presented in this volume were carefully reviewed and selected from 37 submissions. They were organized in topical sections named: agile adoption; agile practices; large-scale agile; the business of agile; and agile and testing.

Incorporating the latest research throughout, Daniel Levi’s Fifth Edition of Group Dynamics for Teams explains the basic psychological concepts of group dynamics, focusing on their application with teams in the workplace. Grounded in psychology research and a practical focus on organizational behavior issues, this engaging book helps readers understand and more effectively participate in teams.

This book explores the application of agile and lean techniques, originally from the field of software development and manufacturing, to various aspects of education. It covers a broad range of topics, including applying agile teaching and learning techniques in the classroom, incorporating lean thinking in educational workflows, and using team-based approaches to student-centred activities based on agile principles and processes. Demonstrating how agile and lean ideas can concretely be applied to education, the book offers practical guidance on how to apply these ideas in the classroom or lecture hall, as well as new concepts that could spark further research and development.

This book is open access under a CC BY license. The volume constitutes the proceedings of the 18th International Conference on Agile Software Development, XP 2017, held in Cologne, Germany, in May 2017. The 14 full and 6 short papers presented in this volume were carefully reviewed and selected from 46 submissions. They were organized in topical sections named: improving agile processes; agile in organization; and safety critical software. In addition, the volume contains 3 doctoral symposium papers (from 4 papers submitted).

As contrary as it sounds, "planning" -- as we traditionally understand the term--can be the worst thing a company can do. Consider that volatile weather events disrupt trusted supply chains, markets, and promised delivery schedules. Ever-shifting geo-political tensions, as well as internal political upheaval within U.S. and global governments, derail long-planned new ventures. Technology failures block opportunities. Competitors suddenly change their product or release date; your team cannot meet the pace of innovations in your market niche, leaving you sidelined. There are myriad ways in the current business environment for a company's well-considered business plans to go awry. Most business schools continue to prepare managers to be effective in stable and predictable environments, conditions that, if they ever existed at all, are long gone. The Agility Shift shows business leaders exactly how to make the radical mindset and strategy shift necessary to create an agile, entrepreneurial organization that can innovate and thrive in complex, ever-changing contexts. As author Pamela Meyer explains, there is much more involved than a reconfiguration of the org chart and job descriptions. It requires relinquishing the illusion of control at the very foundation of most management training and business practice. Despite most leaders' approaches, "Agility is not simply accelerated planning." Unlike many agility books on the market, The Agility Shift provides specific, actionable strategies and tactics for leaders at all levels of the organization to put into practice immediately to improve agility and achieve results.

Project retrospectives help teams examine what went right and what went wrong on a project. But traditionally, retrospectives (also known as “post-mortems”) are only held at the end of the project—too late to help. You need agile retrospectives that are iterative and incremental. You need to accurately find and fix problems to help the team today. Now Esther and Diana show you the tools, tricks and tips you need to fix the problems you face on a software development project on an on-going basis. You’ll see how to architect retrospectives in general, how to design them specifically for your team and organization, how to run them effectively, how to make the needed changes and how to scale these techniques up. You’ll learn how to deal with problems, and implement solutions effectively throughout the project—not just at the end. This book will help you: Design and run effective retrospectives Learn how to find and fix problems Find and reinforce team strengths Address people issues as well as technological Use tools and recipes proven in the real world With regular tune-ups, your team will hum like a precise, world-class orchestra.

The Go-To Resource for Large-Scale Organizations to Be Agile Rather than asking, “How can we do agile at scale in our big complex organization?” a different and deeper question is, “How can we have the same simple structure that Scrum offers for the organization, and be agile at scale rather than do agile?” This profound insight is at the heart of LeSS (Large-Scale Scrum). In Large-Scale Scrum: More with LeSS, Craig Larman and Bas Vodde have distilled over a decade of experience in large-scale LeSS adoptions towards a simpler organization that delivers more flexibility with less complexity, more value with less waste, and more purpose with less prescription. Targeted to anyone involved in large-scale development, Large-Scale Scrum: More with LeSS, offers straight-to-the-point guides for how to be agile at scale, with LeSS. It will clearly guide you to Adopt LeSS Structure a large development organization for customer value Clarify the role of management and Scrum Master Define what your product is, and why Be a great Product Owner Work with multiple whole-product focused feature teams in one Sprint that produces a shippable product Coordinate and integrate between teams Work with multi-site teams

New for the third edition, chapters on: Complete Exercise of the SE Process, System Science and Analytics and The Value of Systems Engineering The book takes a model-based approach to key systems engineering design activities and introduces methods and models used in the real world. This book is divided into three major parts: (1) Introduction, Overview and Basic Knowledge, (2) Design and Integration Topics, (3) Supplemental Topics. The first part provides an introduction to the issues associated with the engineering of a system. The second part covers the critical material required to understand the major elements needed in the engineering design of any system: requirements, architectures (functional, physical, and allocated), interfaces, and qualification. The final part reviews methods for data, process, and behavior modeling, decision analysis, system science and analytics, and the value of systems engineering. Chapter 1 has been rewritten to integrate the new chapters and updates were made throughout the original chapters. Provides an overview of modeling, modeling methods associated with SysML, and IDEF0 Includes a new Chapter 12 that provides a comprehensive review of the topics discussed in Chapters 6 through 11 via a simple system – an automated soda machine Features a new Chapter 15 that reviews General System Theory, systems science, natural systems, cybernetics, systems thinking, quantitative characterization of systems, system dynamics, constraint theory, and Fermi problems and guesstimation Includes a new Chapter 16 on the value of systems engineering with five primary value propositions: systems as a goal-seeking system, systems engineering as a communications interface, systems engineering to avert showstoppers, systems engineering to find and fix errors, and systems engineering as risk mitigation The Engineering Design of Systems: Models and Methods, Third Edition is designed to be an introductory reference for professionals as well as a textbook for senior undergraduate and graduate students in systems engineering.