Ken Schwaber

Mike Beedle

Agile Software Development with SCRUM

Agile Project Management with Scrum (Microsoft Professional)

The rules and practices for Scrum—a simple process for managing complex projects—are few, straightforward, and easy to learn. But Scrum’s simplicity itself—its lack of prescription—can be disarming, and new practitioners often find themselves reverting to old project management habits and tools and yielding lesser results. In this illuminating series of case studies, Scrum co-creator and evangelist Ken Schwaber identifies the real-world lessons—the successes and failures—culled from his years of experience coaching companies in agile project management. Through them, you’ll understand how to use Scrum to solve complex problems and drive better results—delivering more valuable software faster. Gain the foundation in Scrum theory—and practice—you need to: Rein in even the most complex, unwieldy projects Effectively manage unknown or changing product requirements Simplify the chain of command with self-managing development teams Receive clearer specifications—and feedback—from customers Greatly reduce project planning time and required tools Build—and release—products in 30-day cycles so clients get deliverables earlier Avoid missteps by regularly inspecting, reporting on, and fine-tuning projects Support multiple teams working on a large-scale project from many geographic locations Maximize return on investment!

Agile Project Management with Scrum

Scrum Guide

Jeff Sutherland

Summarizes the Agile and Scrum software development method, which allows creation of software in just 30 days.

How Agile Managers Beat the Odds, Delight Their Customers, and Leave Competitors in the Dust

Software in 30 Days

Using real-world examples, discusses how to manage the change involved when businesses adopt the Scrum model.

The Enterprise and Scrum

A deceptively simple process called Scrum, a new approach to systems development projects, is described here. Application development managers will learn how to simplify the implementation of Agile processes with Scrum, how to simplify XP implementation through a Scrum wrapper, how to understand the theoretical underpinnings of Agile processes, and why Agile processes work and how to manage them. Material is of interest to the software development community at large. Schwaber is president of a software development consultancy. Annotation copyrighted by Book News Inc., Portland, OR.

Agile Software Development with Scrum

Diana Larsen

Esther Derby

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.

Making Good Teams Great

Agile Retrospectives

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 helpful 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, Derby and Larsen 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. With regular tune-ups, your team will hum like a precise, world-class orchestra.

Mit Scrum lässt sich bei der Softwareentwicklung flexibel auf veränderte Marktbedingungen reagieren. Noch während der Entwicklung können neue Erkenntnisse in die weitere Planung integriert werden. Dieses Buch beschreibt die Scrum-Entwicklungsmethode und zeigt auf, wie Software in kleinen Inkrementen von maximal 30 Tagen entwickelt wird, sodass nach jedem Inkrement die Richtung der Entwicklung geändert werden kann. Es wendet sich an Führungskräfte und IT-Manager, die Scrum im Unternehmen einführen möchten, um mehr Produktivität, Qualität, Wertschöpfung, Kontrollierbarkeit, Vorhersagbarkeit und Zufriedenheit in der Softwareentwicklung zu gewinnen. Sie erfahren auch, wie Sie mit Scrum Risiken im Projekt meistern und das Team dabei unterstützen können, erfolgreich zu sein. Aus dem Inhalt: • Warum jedes Unternehmen der Welt in 30 Tagen Software herstellen kann • Wie man Software in 30 Tagen herstellt • Mit Scrum starten • Scrum auf Projektebene • Scrum-Fähigkeiten entwickeln • Unternehmensumstellung: tiefgreifende und nachhaltige Veränderung • Scrumming Scrum Im Anhang befinden sich unter anderem ein Glossar, der "Scrum Guide" sowie ein detaillierter Plan für die Unternehmensentwicklung, um Agilität zu erreichen.

Wie Manager mit Scrum Wettbewerbsvorteile für ihr Unternehmen schaffen

Software in 30 Tagen

It’s time to extend the benefits of Scrum—greater agility, higher-quality products, and lower costs—from individual teams to your entire enterprise. However, with Scrum’s lack of prescribed rules, the friction of change can be challenging as people struggle to break from old project management habits. In this book, agile-process revolution leader Ken Schwaber takes you through change management—for your organizational and interpersonal processes—explaining how to successfully adopt Scrum across your entire organization. A cofounder of Scrum, Ken draws from decades of experience, answering your questions through case studies of proven practices and processes. With them, you’ll learn how to adopt—and adapt—Scrum in the enterprise. And gain profound levels of transparency into your development processes. Discover how to: Evaluate the benefits of adopting Scrum in any size organization Initiate an enterprise transition project Implement a single, prioritized Product Backlog Organize effective Scrum teams using a top-down approach Adapt and apply solutions for integrating engineering practices across multiple teams Shorten release times by managing high-value increments Refine your Scrum practices and help reduce the length of Sprints

Ken Schwaber

About

Books

Join the club