This book aims to give you a head start by providing a detailed down-to-earth account of how one Swedish company implemented Scrum and XP with a team of approximately 40 people and how they continuously improved their process over a year's time. Under the leadership of Henrik Kniberg they experimented with different team sizes, different sprint lengths, different ways of defining "done," different formats for product backlogs and sprint backlogs, different testing strategies, different ways of doing demos, different ways of synchronizing multiple Scrum teams, etc. They also experimented with XP practices - different ways of doing continuous build, pair programming, test driven development, etc, and how to combine this with Scrum. This second edition is an annotated version, a "director's cut" where Henrik reflects upon the content and shares new insights gained since the first version of the book.
This book aims to give you a head start by providing a detailed down-to-earth account of how one Swedish company implemented Scrum and XP with a team of approximately 40 people and how they continuously improved their process over a year's time. Covering: Practical tips and tricks for most Scrum and XP practices. Typical pitfalls and how they were addressed. Diagrams and photos illustrating day-to-day work. Testing and test-driven development. Scaling and coordinating multiple teams. Dealing with resistance from inside and outside the team. Planning and time estimation techniques
From start to finish, readers will see what it takes to develop a successful agile project. Find out how the Swedish police combined XP, Scrum, and Kanban to modernize their department--and learn how to apply those same principles to the workplace.
Scrum and Kanban are two flavours of Agile software development - two deceptively simple but surprisingly powerful approaches to software development. So how do they relate to each other? The purpose of this book is to clear up the fog, so you can figure out how Kanban and Scrum might be useful in your environment. Part I illustrates the similarities and differences between Kanban and Scrum, comparing for understanding, not for judgement. There is no such thing as a good or bad tool - just good or bad decisions about when and how to use which tool. This book includes: - Kanban and Scrum in a nutshell - Comparison of Kanban and Scrum and other Agile methods - Practical examples and pitfalls - Cartoons and diagrams illustrating day-to-day work - Detailed case study of a Kanban implementation within a Scrum organization Part II is a case study illustrating how a Scrum-based development organization implemented Kanban in their operations and support teams.
“We need better approaches to understanding and managing software requirements, and Dean provides them in this book. He draws ideas from three very useful intellectual pools: classical management practices, Agile methods, and lean product development. By combining the strengths of these three approaches, he has produced something that works better than any one in isolation.” –From the Foreword by Don Reinertsen, President of Reinertsen & Associates; author of Managing the Design Factory; and leading expert on rapid product development Effective requirements discovery and analysis is a critical best practice for serious application development. Until now, however, requirements and Agile methods have rarely coexisted peacefully. For many enterprises considering Agile approaches, the absence of effective and scalable Agile requirements processes has been a showstopper for Agile adoption. In Agile Software Requirements, Dean Leffingwell shows exactly how to create effective requirements in Agile environments. Part I presents the “big picture” of Agile requirements in the enterprise, and describes an overall process model for Agile requirements at the project team, program, and portfolio levels Part II describes a simple and lightweight, yet comprehensive model that Agile project teams can use to manage requirements Part III shows how to develop Agile requirements for complex systems that require the cooperation of multiple teams Part IV guides enterprises in developing Agile requirements for ever-larger “systems of systems,” application suites, and product portfolios This book will help you leverage the benefits of Agile without sacrificing the value of effective requirements discovery and analysis. You’ll find proven solutions you can apply right now–whether you’re a software developer or tester, executive, project/program manager, architect, or team leader.
Here is the first comprehensive approach to managing design-in-process inventory from the bestselling author of "Developing Products in Half the Time". Donald Reinertsen reveals a transparent system for tracking, measuring, and managing invisible "design-in-process" inventory to achieve lower costs, higher profits, and better processes. 20 line drawings.
Accountability. Transparency. Responsibility. These are not words that are often applied to software development. In this completely revised introduction to Extreme Programming (XP), Kent Beck describes how to improve your software development by integrating these highly desirable concepts into your daily development process. The first edition of Extreme Programming Explained is a classic. It won awards for its then-radical ideas for improving small-team development, such as having developers write automated tests for their own code and having the whole team plan weekly. Much has changed in five years. This completely rewritten second edition expands the scope of XP to teams of any size by suggesting a program of continuous improvement based on: Five core values consistent with excellence in software development Eleven principles for putting those values into action Thirteen primary and eleven corollary practices to help you push development past its current business and technical limitations Whether you have a small team that is already closely aligned with your customers or a large team in a gigantic or multinational organization, you will find in these pages a wealth of ideas to challenge, inspire, and encourage you and your team members to substantially improve your software development. You will discover how to: Involve the whole team–XP style Increase technical collaboration through pair programming and continuous integration Reduce defects through developer testing Align business and technical decisions through weekly and quarterly planning Improve teamwork by setting up an informative, shared workspace You will also find many other concrete ideas for improvement, all based on a philosophy that emphasizes simultaneously increasing the humanity and effectiveness of software development. Every team can improve. Every team can begin improving today. Improvement is possible–beyond what we can currently imagine. Extreme Programming Explained, Second Edition, offers ideas to fuel your improvement for years to come.
A guide to XP leads the developer, project manager, and team leader through the software development planning process, offering real world examples and tips for reacting to changing environments quickly and efficiently.
Agile teams have been struggling with the concept of continuous improvement since the first Agile frameworks were developed, and still very little has been written about the practice of continuous improvement in Agile environments. Although team retrospectives have been prescribed and some practices have been introduced in order to implement and facilitate them, the truth is that most Agile teams are conducting dull retrospectives that end with a list of things that have been done wrong, just to repeat the same list two weeks later at the next meeting. Instead of listing hundreds of Japanese-labeled tools, this book gives you practical insights into how to spot improvement opportunities, how to plan for improvement and how to engage everyone in your company in the Kaizen process. In addition, it will also provide you with 27 proven practices and 12 bonus activities to introduce into your retrospectives in order to keep them fresh, creative and exciting, so you can promise a team that, in a year’s time, no two retrospectives will be alike. This book helps you as a manager, team leader, change agent or consultant in any type of organization to unleash the real power of Kaizen cultures – no matter what kind of organization, market, product, technology, vision, goal or size. It provides you with the background, tools and practical hints on how to engage your organization in a process of continuous quest for new and better ways of performing.
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
Thoroughly reviewed and eagerly anticipated by the agile community, User Stories Applied offers a requirements process that saves time, eliminates rework, and leads directly to better software. The best way to build software that meets users' needs is to begin with "user stories": simple, clear, brief descriptions of functionality that will be valuable to real users. In User Stories Applied, Mike Cohn provides you with a front-to-back blueprint for writing these user stories and weaving them into your development lifecycle. You'll learn what makes a great user story, and what makes a bad one. You'll discover practical ways to gather user stories, even when you can't speak with your users. Then, once you've compiled your user stories, Cohn shows how to organize them, prioritize them, and use them for planning, management, and testing. User role modeling: understanding what users have in common, and where they differ Gathering stories: user interviewing, questionnaires, observation, and workshops Working with managers, trainers, salespeople and other "proxies" Writing user stories for acceptance testing Using stories to prioritize, set schedules, and estimate release costs Includes end-of-chapter practice questions and exercises User Stories Applied will be invaluable to every software developer, tester, analyst, and manager working with any agile method: XP, Scrum... or even your own home-grown approach.
Kanban is a simple and elegant Agile framework that helps to control and improve development processes. Originating in traditional 20th century manufacturing in Japan, Kanban has a renewed relevance today, being a crucial methodology in the world of software development. This book explores the key features of Kanban, and demonstrates how to put it into practice through exercises that will help you make the most of this unique approach to managing collaboration and production. Designed as a 30 day action plan, this book will help you understand and implement Kanban – and start seeing results – in a month. Analyze your current situation and define your goals and wider strategic aims, and begin developing a plan to help you and your team confidently work towards achieving them. Involve your team to drive cultural change, learn how to prioritize and organize tasks and projects to efficiently use your time and resources. Create your own value stream map to better understand your processes and identify improvement areas, and adapt and use the features tips and examples to overcome challenges you may face when implementing Kanban. Pick up this book and experience the full results of this vital Agile methodology – fast.
Your team is stressed; priorities are unclear. You're not sure what your teammates are working on, and management isn't helping. If your team is struggling with any of these symptoms, these four case studies will guide you to project success. See how Kanban was used to significantly improve time to market and to create a shared focus across marketing, IT, and operations. Each case study comes with illustrations of the Kanban board and diagrams and graphs to help you see behind the scenes. Learn a Lean approach by seeing how Kanban made a difference in four real-world situations. You'll explore how four different teams used Kanban to make paradigm-changing improvements in software development. These teams were struggling with overwork, unclear priorities, and lack of direction. As you discover what worked for them, you'll understand how to make significant changes in real situations. The four case studies in this book explain how to: Improve the full value chain by using Enterprise Kanban Boost engagement, teamwork, and flow in change management and operations Save a derailing project with Kanban Help an office team outside IT keep up with growth using Kanban What seems easy in theory can become tangled in practice. Discover why "improving IT" can make you miss your biggest improvement opportunities, and why you should focus on fixing quality and front-end operations before IT. Discover how to keep long-term focus and improve across department borders while dealing with everyday challenges. Find out what happened when using Kanban to find better ways to do work in a well-established company, including running multi-team development without a project office. You'll inspire your team and engage management to make it easier to develop better products. What You Need: This is a case study book, so there are no software requirements. The book covers the relevant bits of theory before presenting the case studies.
The Power of Scrum tells the inspiring story of Mark Resting, CTO of a software company struggling with a major client and a project with more problems than solutions and a marriage in crisis. But, when he meets Jerry, a West-coast expert in Scrum, light at the end of the tunnel begins to appear, Mark begins to reluctantly hope things will work out. The road is bumpy, but Jerry skillfully brings Mark's developers from a world of project crisis into a revolutionary approach that can save the day. Authors Jeff Sutherland, Rini van Solinger, and Eelco Rustenburg have written a fictional narrative that masterfully weaves a compelling human story around the teaching moments of a software, project management how-to, and in the process tell an engaging story of personal growth and triumph, while demonstrating the power of a revolutionary and mission-critical approach to project management. The Power of Scrum is a must read for project managers, software developers, and product developers, as well as for anyone who loves a great story well told.
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 started PART 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
Liftoff-it's the unexplored, often ignored, Agile project practice. As the first act of flight, a rocket launch requires an entire set of systems to lift the vehicle into orbit-not just the vehicle itself, but all the systems needed for smoothly moving off the ground into space. Likewise, your project needs its entire set of supporting systems in place to begin a successful journey to delivery. Whatever you call it (project kickoff, bootcamp, inception, or jump start), liftoff gives your team its trajectory, and launches your project. This critical practice informs, inspires, and aligns everyone to a singular purpose: the successful delivery of software. This success is in your hands! Agile veterans Diana Larsen and Ainsley Nies teach you how to organize and conduct liftoffs, hold team activities to discover what's most important, and offer a working framework for effective and lightweight agile chartering.
Don't just 'survive' the move to agile: thrive! Discover 42 infinitely practical tips for succeeding with agile, right from the start! * *Paves the road to success with a clear plan for creating and releasing software. *Works with any agile methodology, from XP to Scrum. *Practical, actionable, concrete tips for senior managers, program/project managers, developers, and product owners. *Eliminates 'buyer's remorse' associated with bumpy agile transitions, helping teams quickly build confidence and get results. Adopting agile looks easy - on paper! In reality, though, new agile teams encounter many unforeseen challenges. Some lose confidence in their ability to succeed; others muddle through, struggling to solve problems that others have already solved many times over. In this book Mitch Lacey brings together those solutions, helping new agile developers learn from others' experience quickly and painlessly. This engaging, realistic book systematically removes the pain of agile adoption, and breaks down the barriers to rapid success. The Scrum Field Guide is organized into 42 bite-size, practical tips - each supported with highly relevant real-world examples and case studies. Lacey presents a section of tips that apply to everyone on the agile team, from leaders to customers. Next, he offers sections specific to each role - including tips for management, program/project managers, team members, and product owners. Lacey answers the questions new agile adopters ask most often - including 'can I modify standard agile processes and still be agile?' and 'how on Earth can we release software within a short timeframe if we can't even do it in a long timeframe?' Along the way, he presents proven solutions for a wide variety of common problems - from prioritizing requirements to building release plans, creating workable software iterations to getting buy-in from skeptical executives.
An easy-to-understand primer on Virtual Reality and Augmented Reality Virtual Reality (VR) and Augmented Reality (AR) are driving the next technological revolution. If you want to get in on the action, this book helps you understand what these technologies are, their history, how they’re being used, and how they’ll affect consumers both personally and professionally in the very near future. With VR and AR poised to become mainstream within the next few years, an accessible book to bring users up to speed on the subject is sorely needed—and that’s where this handy reference comes in! Rather than focusing on a specific piece of hardware (HTC Vive, Oculus Rift, iOS ARKit) or software (Unity, Unreal Engine), Virtual & Augmented Reality For Dummies offers a broad look at both VR and AR, giving you a bird’s eye view of what you can expect as they continue to take the world by storm. * Keeps you up-to-date on the pulse of this fast-changing technology * Explores the many ways AR/VR are being used in fields such as healthcare, education, and entertainment * Includes interviews with designers, developers, and technologists currently working in the fields of VR and AR Perfect for both potential content creators and content consumers, this book will change the way you approach and contribute to these emerging technologies.
Written by the former Deputy Counsel and Risk Manager for the Big Dig from 1996 to 2005, Virginia Greiman, this book describes the numerous risks faced by the project manager and the lessons learned that have never before been written about despite the huge volume of news articles and reports that have been published on the Big Dig. New insights based on excerpts of interviews offer new perspective on the challenges and accomplishments of the Big Dig, and separates this book from other texts in the field.