SCRUM IN ACTION: AGILE SOFTWARE PROJECT MANAGEMENT AND DEVELOPMENT is a practical how-to guide for software project teams on how to successfully deploy an Agile software framework with Scrum. It is clearly and concisely written and is the first practical guide with real world situations written by corporate practitioners. This book describes many good project management techniques on how to get the most from project teams and bridges the gaps between many Scrum and project management books by addressing how to communicate with executives using financial terms, how to use an objective estimation technique, and where software architecture fits into Scrum.

Summary Agile Metrics in Action is a rich resource for agile teams that aim to use metrics to objectively measure performance. You'll learn how to gather data that really counts, along with how to effectively analyze and act upon the results. Purchase of the print book includes a free eBook in PDF, Kindle, and ePub formats from Manning Publications. About the Book The iterative nature of agile development is perfect for experience-based, continuous improvement. Tracking systems, test and build tools, source control, continuous integration, and other built-in parts of a project lifecycle throw off a wealth of data you can use to improve your products, processes, and teams. The question is, how to do it? Agile Metrics in Action teaches you how. This practical book is a rich resource for an agile team that aims to use metrics to objectively measure performance. You'll learn how to gather the data that really count, along with how to effectively analyze and act upon the results. Along the way, you'll discover techniques all team members can use for better individual accountability and team performance. Practices in this book will work with any development process or tool stack. For code-based examples, this book uses Groovy, Grails, and MongoDB. What's Inside Use the data you generate every day from CI and Scrum Improve communication, productivity, transparency, and morale Objectively measure performance Make metrics a natural byproduct of your development process About the Author Christopher Davis has been a software engineer and team leader for over 15 years. He has led numerous teams to successful delivery using agile methodologies. Table of Contents PART 1 MEASURING AGILE TEAMS Measuring agile performance Observing a live project PART 2 COLLECTING AND ANALYZING YOUR TEAM'S DATA Trends and data from project-tracking systems Trends and data from source control Trends and data from CI and deployment servers Data from your production systems PART 3 APPLYING METRICS TO YOUR TEAMS, PROCESSES, AND SOFTWARE Working with the data you're collecting: the sum of the parts Measuring the technical quality of your software Publishing metrics Measuring your team against the agile principles

Summary Kanban in Action is a down-to-earth, no-frills, get-to-know-the-ropes introduction to kanban. It's based on the real-world experience and observations from two kanban coaches who have introduced this process to dozens of teams. You'll learn the principles of why kanban works, as well as nitty-gritty details like how to use different color stickies on a kanban board to help you organize and track your work items. About the Book Too much work and too little time? If this is daily life for your team, you need kanban, a lean knowledge-management method designed to involve all team members in continuous improvement of your process. Kanban in Action is a practical introduction to kanban. Written by two kanban coaches who have taught the method to dozens of teams, the book covers techniques for planning and forecasting, establishing meaningful metrics, visualizing queues and bottlenecks, and constructing and using a kanban board. Written for all members of the development team, including leaders, coders, and business stakeholders. No experience with kanban is required. Purchase of the print book includes a free eBook in PDF, Kindle, and ePub formats from Manning Publications. What's Inside How to focus on work in process and finish faster Examples of successful implementations How team members can make informed decisions About the Authors Marcus Hammarberg is a kanban coach and software developer with experience in BDD, TDD, Specification by Example, Scrum, and XP. Joakim Sundén is an agile coach at Spotify who cofounded the first kanban user groups in Europe. Table of Contents PART 1 LEARNING KANBAN Team Kanbaneros gets startedPART 2 UNDERSTANDING KANBAN Kanban principles Visualizing your work Work items Work in process Limiting work in process Managing flow PART 3 ADVANCED KANBAN Classes of service Planning and estimating Process improvement Using metrics to guide improvements Kanban pitfalls Teaching kanban through games

Building a successful product usually involves teams of people, and many choose the Scrum approach to aid in creating products that deliver the highest possible value. Implementing Scrum gives teams a collection of powerful ideas they can assemble to fit their needs and meet their goals. The ninety-four patterns contained within are elaborated nuggets of insight into Scrum’s building blocks, how they work, and how to use them. They offer novices a roadmap for starting from scratch, yet they help intermediate practitioners fine-tune or fortify their Scrum implementations. Experienced practitioners can use the patterns and supporting explanations to get a better understanding of how the parts of Scrum complement each other to solve common problems in product development. The patterns are written in the well-known Alexandrian form, whose roots in architecture and design have enjoyed broad application in the software world. The form organizes each pattern so you can navigate directly to organizational design tradeoffs or jump to the solution or rationale that makes the solution work. The patterns flow together naturally through the context sections at their beginning and end. Learn everything you need to know to master and implement Scrum one step at a time—the agile way.

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 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!

Originally created for agile software development, scrum provides project managers with the flexibility needed to meet ever-changing consumer demands. Presenting a modified version of the agile software development framework, Scrum Project Management introduces Scrum basics and explains how to apply this adaptive technique to effectively manage a w