One of the least discussed and most challenging roles in the Scrum Agile Methodology is that of Product Owner. Quite often Product Owners are selected from the ranks of Product Managers or Business Analysts and simply "thrown" into the role. While these backgrounds can lead to successful product ownership, often there are fundamental understanding and large skills gaps that need to be crossed in order to be truly successful. This book takes a unique look at the role of Scrum Product Owner with a focus on how the role needs to interact with their Scrum team first--thus the "inside out." We review all of the nuance and requisite habits that allow the Scrum Product Owner to drive their teams towards creating high quality products that provide great customer value.
When it was first published in 2009, Scrum Product Ownership was the first book to address the Product Owner role in detail. It was a breakthrough guide in how to drive high quality and customer value, while maintaining a singular focus on agile delivery principles. Fast forward to 2013 and much has changed. Scrum and the other agile methods are dominating the mainstream and new success stories seem to be forthcoming daily. However, there are still challenges and many surround the Product Owner role: scaling Scrum, sustaining quality, delivering and measuring value, providing team leadership, being a part of organizational transformation, and simple survival are all still in play. In other words, the role is still just plain HARD. The Second Edition of Scrum Product Ownership is being delivered to help with today's challenges. It has more practical advice, real-world tactics, and more stories. It provides a framework of ideas to help today's Product Owners and their teams to better "Deliver the Goods." However, it remains true to its heritage of guiding you towards becoming a GREAT Product Owner...from the Inside Out.
Author: Gunther Verheyen
Publisher: Van Haren
Release Date: 2013-11-04
This pocket guide is the one book to read for everyone who wants to learn about Scrum. The book covers all roles, rules and the main principles underpinning Scrum, and is based on the Scrum Guide Edition 2013. A broader context to this fundamental description of Scrum is given by describing the past and the future of Scrum. The author, Gunther Verheyen, has created a concise, yet complete and passionate reference about Scrum. The book demonstrates his core view that Scrum is about a journey, a journey of discovery and fun. He designed the book to be a helpful guide on that journey. Ken Schwaber, Scrum co-creator says that this book currently is the best available description of Scrum around. The book combines some rare characteristics: • It describes Scrum in its entirety, yet places it in a broader context (of past and future). • The author focuses on the subject, Scrum, in a way that it truly supports the reader. The book has a language and style in line with the philosophy of Scrum. • The book shows the playfulness of Scrum. David Starr and Ralph Jocham, Professional Scrum trainers and early agile adopters, say that this is the ultimate book to be advised as follow-up book to the students they teach Scrum to and to teams and managers of organizations that they coach Scrum to.
Author: Roman Pichler
Publisher: Addison-Wesley Professional
Release Date: 2010-03-11
The First Guide to Scrum-Based Agile Product Management In Agile Product Management with Scrum, leading Scrum consultant Roman Pichler uses real-world examples to demonstrate how product owners can create successful products with Scrum. He describes a broad range of agile product management practices, including making agile product discovery work, taking advantage of emergent requirements, creating the minimal marketable product, leveraging early customer feedback, and working closely with the development team. Benefitting from Pichler’s extensive experience, you’ll learn how Scrum product ownership differs from traditional product management and how to avoid and overcome the common challenges that Scrum product owners face. Coverage includes Understanding the product owner’s role: what product owners do, how they do it, and the surprising implications Envisioning the product: creating a compelling product vision to galvanize and guide the team and stakeholders Grooming the product backlog: managing the product backlog effectively even for the most complex products Planning the release: bringing clarity to scheduling, budgeting, and functionality decisions Collaborating in sprint meetings: understanding the product owner’s role in sprint meetings, including the dos and don’ts Transitioning into product ownership: succeeding as a product owner and establishing the role in the enterprise This book is an indispensable resource for anyone who works as a product owner, or expects to do so, as well as executives and coaches interested in establishing agile product management.
Author: Greg Cohen
Publisher: Happy About
Release Date: 2010
Genre: Business & Economics
"Agile Excellence for Product Managers" is a plain-speaking guide on how to work with Agile development teams to achieve phenomenal product success. It covers the why and how of agile development (including Scrum, XP, and Lean, ) the role of product management, release planning, and more.
Author: Stephen Denning
Publisher: John Wiley & Sons
Release Date: 2010-09-14
Genre: Business & Economics
A radical new management model for twenty-first century leaders Organizations today face a crisis. The crisis is of long standing and its signs are widespread. Most proposals for improving management address one element of the crisis at the expense of the others. The principles described by award-winning author Stephen Denning simultaneously inspire high productivity, continuous innovation, deep job satisfaction and client delight. Denning puts forward a fundamentally different approach to management, with seven inter-locking principles of continuous innovation: focusing the entire organization on delighting clients; working in self-organizing teams; operating in client-driven iterations; delivering value to clients with each iteration; fostering radical transparency; nurturing continuous self-improvement and communicating interactively. In sum, the principles comprise a new mental model of management. Author outlines the basic seven principles of continuous innovation The book describes more than seventy supporting practices Denning offers a rethinking of management from first principles This book is written by the author of The Secret Language of Leadership—a Financial Times Selection in Best Books of 2007.
Agile Reflections began as a collection of blog posts from several series I've written from 2009 to 2012. As I looked back on the content, I saw some very compelling stories that, if updated and integrated into a cohesive volume, might add even more value to agile teams trying to increase their maturity and effectiveness. There are five sections to the book: 1.Beginnings- the art of the start; how to effectively begin your agile teams and projects 2.Execution- where the rubber meets the road I suppose...guidance around effectively iterating 3.Customer- the why and what behind agile teams; who drives the value and who you deliver to 4.Mindset- you can easily 'say' you're agile, but are you really? 5.Leadership- yes, we need 'stinkin' leadership. I think more so in agile teams than many believe I hope you find some value in the pages (physical or virtual) of this book. I want to think it will help you to become Seriously Agile.
When software development teams move to agile methods, experienced project managers often struggle—doubtful about the new approach and uncertain about their new roles and responsibilities. In this book, two long-time certified Project Management Professionals (PMPRs) and Scrum trainers have built a bridge to this dynamic new paradigm. They show experienced project managers how to successfully transition to agile by refocusing on facilitation and collaboration, not “command and control.” The authors begin by explaining how agile works: how it differs from traditional “plan-driven” methodologies, the benefits it promises, and the real-world results it delivers. Next, they systematically map the Project Management Institute’s classic, methodology-independent techniques and terminology to agile practices. They cover both process and project lifecycles and carefully address vital issues ranging from scope and time to cost management and stakeholder communication. Finally, drawing on their own extensive personal experience, they put a human face on your personal transition to agile--covering the emotional challenges, personal values, and key leadership traits you’ll need to succeed. Coverage includes Relating the PMBOKR Guide ideals to agile practices: similarities, overlaps, and differences Understanding the role and value of agile techniques such as iteration/release planning and retrospectives Using agile techniques to systematically and continually reduce risk Implementing quality assurance (QA) where it belongs: in analysis, design, defect prevention, and continuous improvement Learning to trust your teams and listen for their discoveries Procuring, purchasing, and contracting for software in agile, collaborative environments Avoiding the common mistakes software teams make in transitioning to agile Coordinating with project management offices and non-agile teams “Selling” agile within your teams and throughout your organization For every project manager who wants to become more agile. Part I An Agile Overview 7 Chapter 1 What is "Agile"? 9 Chapter 2 Mapping from the PMBOKR Guide to Agile 25 Chapter 3 The Agile Project Lifecycle in Detail 37 Part II The Bridge: Relating PMBOKR Guide Practices to Agile Practices 49 Chapter 4 Integration Management 51 Chapter 5 Scope Management 67 Chapter 6 Time Management 83 Chapter 7 Cost Management 111 Chapter 8 Quality Management 129 Chapter 9 Human Resources Management 143 Chapter 10 Communications Management 159 Chapter 11 Risk Management 177 Chapter 12 Procurement Management 197 Part III Crossing the Bridge to Agile 215 Chapter 13 How Will My Responsibilities Change? 217 Chapter 14 How Will I Work with Other Teams Who Aren't Agile? 233 Chapter 15 How Can a Project Management Office Support Agile? 249 Chapter 16 Selling the Benefits of Agile 265 Chapter 17 Common Mistakes 285 Appendix A Agile Methodologies 295 Appendix B Agile Artifacts 301 Glossary 321 Bibliography 327 Index 333
This manual contains the slides for a two-day Product Owner and User Story course which covers the key components of Scrum and addresses the role of the Product Owner on Scrum teams and how to effectively create and manage User Stories. The Product Owner role is critical to maximizing Return on Investment (ROI) from agile projects and is one of the most challenging and rewarding agile roles. Many Product Owners come from business areas of the organization and have limited familiarity with elements of software development, project management and agile methods that are critical to success in the Product Owner role. For these reasons, it is vitally important that Product Owners gain a solid understanding of their role and responsibilities as well as the knowledge, skills and tools to work effectively with Scrum teams. Please read this description before purchasing this guide and use the "Look Inside" feature from Amazon. These manuals which are part of the Agile Education Series developed by Dan Tousignant are the participant guides used in his public, onsite and virtual training classes worldwide. They are intended for those readers who are aspiring Agile trainers, Scrum practitioners, or those interested in previewing the courses. These guides are not stand-alone training materials, but are for those people interested in reviewing a well-designed, comprehensive Agile curriculum. These courses have taken hundreds of hours to develop and are constantly being improved upon and republished. Recently, the guides have been republished to include the exercise handouts and have also been published in color format to be seen on a Kindle Fire or iPad. If you are interested in purchasing the slides and exercises for this course, contact us at [email protected]
Author: Mike Cohn
Publisher: Addison-Wesley Professional
Release Date: 2004-03-01
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.
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.
Author: Kenneth S. Rubin
Publisher: Addison-Wesley Professional
Release Date: 2012
Genre: Business & Economics
The must-have practitioner's guide and manager's reference to Scrum, today's #1 agile process: fast-track knowledge for every decision-maker * *An ideal quick-start guide for technically savvy professionals and managers with no Scrum/Agile experience: serves a vital need and fills a major market void. *Exceptionally accessible: designed to be read cover-to-cover on one cross-country flight. *Two color format, packed with illustrations and margin notes that draw instant attention to key issues, techniques, pitfalls, and solutions. This easy-to-read, easy-to-use book brings together all the non-technical information managers and practitioners need to evaluate and get started with Scrum, today's #1 Agile process. Filling a major gap in the marketplace, it demystifies Scrum and Agile with simple, fast-paced explanations, more than 100 easy-to-follow illustrations, and quick paragraph summaries that deliver instant insights on key issues, techniques, pitfalls, and solutions. Kenny Rubin draws on more than a decade of experience implementing Scrum and training more than 3,000 Scrum practitioners at all levels. He delivers fasttrack familiarity with all aspects for Scrum for every technically savvy practitioner and manager who hasn't worked with agile methods before. Coverage includes: * *Why so many organizations are adopting Scrum, and how it has evolved. *Essential Scrum/Agile concepts and roles. *How to start a Scrum project or product. *How to manage product backlogs. *Sprints, sprint meetings, and Scrum 'by the numbers' *Scaling and distributing Scrum. *Using Scrum on diverse types of development projects. *Choosing the right Scrum tools The book also includes a detailed glossary that can help every new Scrum participant 'get on the same page' with Scrum's terminology, as well as an up to-date bibliography for further exploration.
“For software developers of all experience levels looking to improve their results, and design and implement domain-driven enterprise applications consistently with the best current state of professional practice, Implementing Domain-Driven Design will impart a treasure trove of knowledge hard won within the DDD and enterprise application architecture communities over the last couple decades.” –Randy Stafford, Architect At-Large, Oracle Coherence Product Development “This book is a must-read for anybody looking to put DDD into practice.” –Udi Dahan, Founder of NServiceBus Implementing Domain-Driven Design presents a top-down approach to understanding domain-driven design (DDD) in a way that fluently connects strategic patterns to fundamental tactical programming tools. Vaughn Vernon couples guided approaches to implementation with modern architectures, highlighting the importance and value of focusing on the business domain while balancing technical considerations. Building on Eric Evans’ seminal book, Domain-Driven Design, the author presents practical DDD techniques through examples from familiar domains. Each principle is backed up by realistic Java examples–all applicable to C# developers–and all content is tied together by a single case study: the delivery of a large-scale Scrum-based SaaS system for a multitenant environment. The author takes you far beyond “DDD-lite” approaches that embrace DDD solely as a technical toolset, and shows you how to fully leverage DDD’s “strategic design patterns” using Bounded Context, Context Maps, and the Ubiquitous Language. Using these techniques and examples, you can reduce time to market and improve quality, as you build software that is more flexible, more scalable, and more tightly aligned to business goals. Coverage includes Getting started the right way with DDD, so you can rapidly gain value from it Using DDD within diverse architectures, including Hexagonal, SOA, REST, CQRS, Event-Driven, and Fabric/Grid-Based Appropriately designing and applying Entities–and learning when to use Value Objects instead Mastering DDD’s powerful new Domain Events technique Designing Repositories for ORM, NoSQL, and other databases
Author: Ken Schwaber
Publisher: Microsoft Press
Release Date: 2004-02-11
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!
The overwhelming majority of a software system’s lifespan is spent in use, not in design or implementation. So, why does conventional wisdom insist that software engineers focus primarily on the design and development of large-scale computing systems? In this collection of essays and articles, key members of Google’s Site Reliability Team explain how and why their commitment to the entire lifecycle has enabled the company to successfully build, deploy, monitor, and maintain some of the largest software systems in the world. You’ll learn the principles and practices that enable Google engineers to make systems more scalable, reliable, and efficient—lessons directly applicable to your organization. This book is divided into four sections: Introduction—Learn what site reliability engineering is and why it differs from conventional IT industry practices Principles—Examine the patterns, behaviors, and areas of concern that influence the work of a site reliability engineer (SRE) Practices—Understand the theory and practice of an SRE’s day-to-day work: building and operating large distributed computing systems Management—Explore Google's best practices for training, communication, and meetings that your organization can use