Organizations pour vast resources into building new products and services. Yet, too many new offerings are poorly conceived, don't delight (or even satisfy) customers, and fail in the marketplace. More effective product ownership and product management can keep that from happening to you. Now, there's an expert guide to world-class agile product development, reflecting deep in-the-trenches experience from two renowned product innovation experts and Scrum consultants. Chris Lukassen and Robbin Schuurman introduce powerful behaviors, tools, concepts, and skills for delivering superior products and services, and avoiding pitfalls that keep you from understanding what customers really need and want. You'll learn how to make crucial decisions based on better insights, not anecdotal or subjective second-hand information; and optimize roles including product owner, customer representative, visionary, experimenter, decision-maker, collaborator, and influencer. The authors teach through a start
Building great software requires outstanding teamwork across multiple disciplines. All teams and participants need to align behind clear goals that deliver real value (outcomes), not just lots of features (output). Sprint Goals are the most powerful tool Scrum/Agile teams have to pursue high-value outcomes, but many Scrum Teams avoid them, misuse them, or struggle to apply them. Succeeding with Sprint Goals covers everything you need to define, create, and execute on Sprint Goals that deliver outstanding value to customers and the business. Leading Scrum practitioner Maarten Dalmijn bridges the gap between theory and practice, offering a fresh, unique, and cohesive perspective on the Scrum framework that will be valuable to every Product Owner, Product Manager, Scrum Master, Agile coach, and technology executive. You will learn why Sprint Goals are so important, how to use them throughout the Sprint and at Review and Retrospective, how to overcome common obstacles to success, and how t
Remote software development work is the "new normal" and that won't change anytime soon. But conventional distributed agile software development attempts to be too "synchronous" to support today's remote teams. Too many meetings, ceremonies, and rituals quickly become unsustainable when teams are spread across multiple time zones. The result: burnout, constant interruptions, poor work-life balance, greater frustration, and workplaces where few people can truly thrive. In The Async-First Playbook, Thoughtworks principal project manager Sumeet Gayathri Moghe addresses the problem head-on, revamping agile to embed remote-native, asynchronous work practices that fit the realities of remote development. Drawing on extensive personal experience leading distributed teams, Moghe addresses both the "nuts and bolts" of specific practices and crucial "softer" elements, such as culture, mindset, and leadership. Short, practical chapters revisit traditional agile rituals such as sprints and pair pr
Learn How to Better Understand Distributed System Design and Solve Common Problems Enterprises today rely on a range of distributed software handling data storage, messaging, system management, and compute capability. Distributed system designs need to be implemented in some programming language, and there are common problems that these implementations need to solve. These problems have common recurring solutions. A patterns approach is very suitable to describe these implementation aspects. Patterns by nature are generic enough to cover a broad range of products from cloud services like Amazon S3 to message brokers like Apache Kafka to infrastructure frameworks like Kubernetes to databases like MongoDB or Actor frameworks like Akka. At the same time the pattern structure is specific enough to be able to show real code. The beauty of this approach is that even if the code structure is shown in one programming language (Java in this case), the structure applies to many other programming
The C++ Core Guidelines can help any C++ developer design and write C++ programs that are exceptionally reliable, robust, and well-performing. But the Guidelines are so jam-packed with excellent advic
