The Scrum Guide documents the Scrum framework and is maintained by Scrum’s creators, Ken Schwaber and Jeff Sutherland.

    This practical guide shows you how to design these types of products for users seeking to take action and achieve specific goals.Stephen Wendel, HelloWallet’s head researcher, takes you step-by-step through the process of applying behavioral economics and psychology to the practical problems of product design and development. Using a combination of lean and agile development methods, you’ll learn a simple iterative approach for identifying target users and behaviors, building the product, and gauging its effectiveness. Discover how to create easy-to-use products to help people make positive changes.Learn the three main strategies to help people change behaviorIdentify your target audience and the behaviors they seek to changeExtract user stories and identify obstacles to behavior changeDevelop effective interface designs that are enjoyable to useMeasure your product’s impact and learn ways to improve itUse practical examples from products like Nest, Fitbit, and Opower

    But twenty years into this movement, breakthrough innovations are still rare, and most companies find that 50 to 90 percent of their innovation initiatives flop. The cost of these failures to U.S. companies alone is estimated to be well over $100 billion annually.In a book that challenges everything you have learned about being customer driven, internationally acclaimed innovation leader Anthony Ulwick reveals the secret weapon behind some of the most successful companies of recent years. Known as outcome-driven innovation, this revolutionary approach to new product and service creation transforms innovation from a nebulous art into a rigorous science from which randomness and uncertainty are eliminated.Based on more than 200 studies spanning more than seventy companies and twenty-five industries, Ulwick contends that, when it comes to innovation, the traditional methods companies use to communicate with customers are the root cause of chronic waste and missed opportunity. In What Customers Want, Ulwick demonstrates that all popular qualitative research methods yield well-intentioned but unfitting and dreadfully misleading information that serves to derail the innovation process. Rather than accepting customer inputs such as needs, benefits, specifications, and solutions, Ulwick argues that researchers should silence the literal voice of the customer and focus on the metrics that customers use to measure success when executing the jobs, tasks or activities they are trying to get done. Using these customer desired outcomes as inputs into the innovation process eliminates much of the chaos and variability that typically derails innovation initiatives.With the same profound insight, simplicity, and uncommon sense that propelled The Innovator's Solution to worldwide acclaim, this paradigm-changing book details an eight-step approach that uses outcome-driven thinking to dramatically improve every aspect of the innovation process--from segmenting markets and identifying opportunities to creating, evaluating, and positioning breakthrough concepts. Using case studies from Microsoft, Johnson & Johnson, AIG, Pfizer, and other leading companies, What Customers Want shows companies how to:Obtain unique customer inputs that make predictable innovation possibleRecognize opportunities for disruption, new market creation, and core market growth--well before competitors doIdentify which ideas, technologies, and acquisitions have the greatest potential for creating customer valueSystematically define breakthrough products and services conceptsInnovation is fundamental to success and business growth. Offering a proven alternative to failed customer-driven thinking, this landmark book arms you with the tools to unleash innovation, lower costs, and reduce failure rates--and create the products and services customers really want.

    And yet the day-to-day work of product management remains largely misunderstood. In theory, product management is about building products that people love. The real-world practice of product management is often about difficult conversations, practical compromises, and hard-won incremental gains.In this book, author Matt LeMay focuses on the CORE connective skills-- communication, organization, research, execution--that can build a successful product management practice across industries, organizations, teams, andtoolsets.For current and aspiring product managers, this book explores: ? On-the-ground tactics for facilitating collaboration and communication? How to talk to users and work with executives? The importance of setting clear and actionable goals? Using roadmaps to connect and align your team? A values-first approach to implementing Agile practices? Common behavioral traps that turn good product managers bad

    It is written in a conversational tone, doesn't take itself too seriously, and avoids extraneous fluff."- Eric Ries, Author & Creator of the Lean Startup methodology"Get the CustDev book to dive deep into customer interviews and understand how your product can be developed to meet your customers' needs."- Dan Martell, Founder of Flowtown, angel investorCustomer Development is a four-step framework for helping startups discover and validate their customers, product, and go-to-market strategy, developed by Steve Blank and an integral part of Eric Ries' Lean Startup methodology. Focused on the Customer Discovery step, The Entrepreneur's Guide to Customer Development is an easy to follow guide for finding early adopters, building a Minimum Viable Product, finding Product-Market fit, and establishing a sales and marketing roadmap.Deemed a "must-read" by Steve Blank and Eric Ries, inside you will find detailed customer development and lean startup concept definitions, a step-by-step approach to best practices, a business model analysis guide, case studies, rich graphics, as well as worksheets and exercises. No matter the stage of your business, you will return often to this guide to learn how to build a product people want;"get out of the building;" foster strong customer relationships; test business model risk; reach out to early adopters; conduct startup marketing; create a customer funnel based on buyers' process; and prepare your startup to scale up.The Entrepreneur's Guide to Customer Development: A Cheat Sheet to The Four Steps to the Epiphany, affectionately known as the "CustDev book," serves as course text for classes at Stanford University, University of Chicago, Boston University, DePaul University, University of Minnesota and University of Norway."Our UCL (University College London) students love The Entrepreneur's Guide to Customer Development. Thanks to Brant & Patrick for writing this helpful book. "- Dave Chapman, Deputy Head of the Department of Management Science and Innovation at UCL (University College London)"Love it! Required reading for all NYU entrepreneurs."- Frank Rimalovski, Managing Director of NYU Innovation Venture FundThis book is both an introduction for those unfamiliar with lean concepts and highly actionable for lean practitioners. It is a user friendly guide, written to be accessible to marketing professionals, Engineers startup founders and entrepreneurs, VCs, angels, and anyone else involved in building scalable startups.Existing companies will benefit to from applying Customer Development principles described in detail herein: for example, startups struggling to achieve market traction, or well established companies seeking to spark new innovation.This is a business book for startups like no other. No fluff, but rather sound principles and concrete steps to take to build your business. Get up to speed on Customer Development now.

    Find out how the Swedish police combined XP, Scrum, and Kanban in a 60-person project. From start to finish, you'll see how to deliver a successful product using Lean principles. We start with an organization in desperate need of a new way of doing things and finish with a group of sixty, all working in sync to develop a scalable, complex system. You'll walk through the project step by step, from customer engagement, to the daily "cocktail party," version control, bug tracking, and release. In this honest look at what works--and what doesn't--you'll find out how to: Make quality everyone's business, not just the testers. Keep everyone moving in the same direction without micromanagement. Use simple and powerful metrics to aid in planning and process improvement. Balance between low-level feature focus and high-level system focus. You'll be ready to jump into the trenches and streamline your own development process.ContentsForewordPrefacePART I: HOW WE WORK1. About the Project1.1 Timeline 51.2 How We Sliced the Elephant 61.3 How We Involved the Customer 72. Structuring the Teams3. Attending the Daily Cocktail Party3.1 First Tier: Feature Team Daily Stand-up3.2 Second Tier: Sync Meetings per Specialty3.3 Third Tier: Project Sync Meeting4. The Project Board4.1 Our Cadences4.2 How We Handle Urgent Issues and Impediments5. Scaling the Kanban Boards6. Tracking the High-Level Goal7. Defining Ready and Done7.1 Ready for Development7.2 Ready for System Test7.3 How This Improved Collaboration 8. Handling Tech Stories8.1 Example 1: System Test Bottleneck8.2 Example 2: Day Before the Release8.3 Example 3: The 7-Meter Class9. Handling Bugs9.1 Continuous System Test9.2 Fix the Bugs Immediately9.3 Why We Limit the Number of Bugs in the Bug Tracker9.4 Visualizing Bugs9.5 Preventing Recurring Bugs10. Continuously Improving the Process10.1 Team Retrospectives10.2 Process Improvement Workshops10.3 Managing the Rate of Change11. Managing Work in Progress11.1 Using WIP Limits11.2 Why WIP Limits Apply Only to Features12. Capturing and Using Process Metrics12.1 Velocity (Features per Week)12.2 Why We Don’t Use Story Points12.3 Cycle Time (Weeks per Feature)12.4 Cumulative Flow12.5 Process Cycle Efficiency13. Planning the Sprint and Release13.1 Backlog Grooming13.2 Selecting the Top Ten Features13.3 Why We Moved Backlog Grooming Out of the Sprint Planning Meeting13.4 Planning the Release14. How We Do Version Control14.1 No Junk on the Trunk14.2 Team Branches14.3 System Test Branch15. Why We Use Only Physical Kanban Boards16. What We Learned16.1 Know Your Goal16.2 Experiment16.3 Embrace Failure16.4 Solve Real Problems16.5 Have Dedicated Change Agents16.6 Involve PeoplePART II: A CLOSER LOOK AT THE TECHNIQUES 17. Agile and Lean in a Nutshell17.1 Agile in a Nutshell17.2 Lean in a Nutshell17.3 Scrum in a Nutshell17.4 XP in a Nutshell17.5 Kanban in a Nutshell18. Reducing the Test Automation Backlog18.1 What to Do About It18.2 How to Improve Test Coverage a Little Bit Each Iteration18.3 Step 1: List Your Test Cases18.4 Step 2: Classify Each Test18.5 Step 3: Sort the List in Priority Order18.6 Step 4: Automate a Few Tests Each Iteration18.7 Does This Solve the Problem?19. Sizing the Backlog with Planning Poker19.1 Estimating Without Planning Poker19.2 Estimating with Planning Poker19.3 Special Cards20. Cause-Effect Diagrams20.1 Solve Problems, Not Symptoms20.2 The Lean Problem-Solving Approach: A3 Thinking20.3 How to Use Cause-Effect Diagrams20.4 Example 1: Long Release Cycle20.5 Example 2: Defects Released to Production20.6 Example 3: Lack of Pair Programming20.7 Example 4: Lots of Problems20.8 Practical Issues: How to Create and Maintain the Diagrams20.9 Pitfalls20.10 Why Use Cause-Effect Diagrams?21. Final WordsA1. Glossary: How We Avoid Buzzword BingoIndex

    Hadoop allowed small and medium sized companies to store huge amounts of data on cheap commodity servers in racks. The introduction of Big Data has allowed businesses to make decisions based on quantifiable analysis. Hadoop is now implemented in major organizations such as Amazon, IBM, Cloudera, and Dell to name a few. This book introduces you to Hadoop and to concepts such as ‘MapReduce’, ‘Rack Awareness’, ‘Yarn’ and ‘HDFS Federation’, which will help you get acquainted with the technology.

    Rose Randall is the archetypical reluctant project manager. Following a painful project failure years ago, Rose s life is cast into chaos when she is once again thrown into the role against her wishes. Faced with a struggling project, help comes from an unexpected source guiding Rose in the direction of Real Options.When you have read Commitment , you:* understand what the Real Options model is;* can apply the Real Options model to manage project risks successfully;* understand why much of your life involves options that you currently are treating as commitments;* see the world through a different filter opening up many new possibilities;* understand the difference between Commitments and Options.Because the book will:* provide specific examples of how a project can manage its risks using the Real Options model;* outline a simple technique for making decisions;* make you aware of all the decisions you make every day;* build your confidence in your ability to decide when to commit and when to leave options open.In short, this book is indispensable for new and experienced project managers plus anyone else who is interested in knowing more about managing large projects.

    In this book, Agile Alliance cofounder Mike Cohn discusses the philosophy of agile estimating and planning and shows you exactly how to get the job done, with real-world examples and case studies.Concepts are clearly illustrated and readers are guided, step by step, toward how to answer the following questions: What will we build? How big will it be? When must it be done? How much can I really complete by then? You will first learn what makes a good plan-and then what makes it agile.Using the techniques in Agile Estimating and Planning , you can stay agile from start to finish, saving time, conserving resources, and accomplishing more. Highlights include:Why conventional prescriptive planning fails and why agile planning works How to estimate feature size using story points and ideal days--and when to use each How and when to re-estimate How to prioritize features using both financial and nonfinancial approaches How to split large features into smaller, more manageable ones How to plan iterations and predict your team's initial rate of progress How to schedule projects that have unusually high uncertainty or schedule-related risk How to estimate projects that will be worked on by multiple teams Agile Estimating and Planning supports any agile, semiagile, or iterative process, including Scrum, XP, Feature-Driven Development, Crystal, Adaptive Software Development, DSDM, Unified Process, and many more. It will be an indispensable resource for every development manager, team leader, and team member.

    Reveals how to run an online business profitably in spite of the Internet's inherently free culture, disseminating the principles of a ''priceless economy'' in six categories that pertain to advertising, labor exchange, and advanced-version fees.

    Two leaders in the requirements community have teamed up to deliver a contemporary set of practices covering the full range of requirements development and management activities on software projects. Describes practical, effective, field-tested techniques for managing the requirements engineering process from end to end. Provides examples demonstrating how requirements "good practices" can lead to fewer change requests, higher customer satisfaction, and lower development costs. Fully updated with contemporary examples and many new practices and techniques. Describes how to apply effective requirements practices to agile projects and numerous other special project situations. Targeted to business analysts, developers, project managers, and other software project stakeholders who have a general understanding of the software development process. Shares the insights gleaned from the authors' extensive experience delivering hundreds of software-requirements training courses, presentations, and webinars.New chapters are included on specifying data requirements, writing high-quality functional requirements, and requirements reuse. Considerable depth has been added on business requirements, elicitation techniques, and nonfunctional requirements. In addition, new chapters recommend effective requirements practices for various special project situations, including enhancement and replacement, packaged solutions, outsourced, business process automation, analytics and reporting, and embedded and other real-time systems projects.

     ­Written by successful product manager Marc Abraham, My Product Management Toolkit is a comprehensive guide to developing a physical or digital product that consumers love. Here’s a sample of what you’ll find within these pages: Strategies for determining what customers want—even when they don’t know themselves Clear suggestions for developing both physical and digital products Effective methods to constantly iterate a product or feature Containing wisdom from Abraham’s popular blog, this book explores product management from every angle, including consumer analysis, personnel management, and product evolution. Whether you’re developing a product for a small start-up or a multinational corporation, this book will prove invaluable.

    More and more frequently, ScrumMasters and project managers are being asked to coach agile teams. But it's a challenging role. It requires new skills--as well as a subtle understanding of when to step in and when to step back. Migrating from "command and control" to agile coaching requires a whole new mind-set. In Coaching Agile Teams, Lyssa Adkins gives agile coaches the insights they need to adopt this new mind-set and to guide teams to extraordinary performance in a re-energized work environment. You'll gain a deep view into the role of the agile coach, discover what works and what doesn't, and learn how to adapt powerful skills from many allied disciplines, including the fields of professional coaching and mentoring. Coverage includes Understanding what it takes to be a great agile coach Mastering all of the agile coach's roles: teacher, mentor, problem solver, conflict navigator, and performance coach Creating an environment where self-organized, high-performance teams can emerge Coaching teams past cooperation and into full collaboration Evolving your leadership style as your team grows and changes Staying actively engaged without dominating your team and stunting its growth Recognizing failure, recovery, and success modes in your coaching Getting the most out of your own personal agile coaching journey Whether you're an agile coach, leader, trainer, mentor, facilitator, ScrumMaster, project manager, product owner, or team member, this book will help you become skilled at helping others become truly great. What could possibly be more rewarding?

    Now, they build on their message with a bold, iconoclastic strategy for creating the ideal company culture—what they call "the calm company." Their approach directly attack the chaos, anxiety, and stress that plagues millions of workplaces and hampers billions of workers every day.Long hours, an excessive workload, and a lack of sleep have become a badge of honor for modern professionals. But it should be a mark of stupidity, the authors argue. Sadly, this isn’t just a problem for large organizations—individuals, contractors, and solopreneurs are burning themselves out the same way. The answer to better productivity isn’t more hours—it’s less waste and fewer things that induce distraction and persistent stress.It’s time to stop celebrating Crazy, and start celebrating Calm, Fried and Hansson assert.Fried and Hansson have the proof to back up their argument. "Calm" has been the cornerstone of their company’s culture since Basecamp began twenty years ago. Destined to become the management guide for the next generation, It Doesn't Have to Be Crazy at Work is a practical and inspiring distillation of their insights and experiences. It isn’t a book telling you what to do. It’s a book showing you what they’ve done—and how any manager or executive no matter the industry or size of the company, can do it too.

    You'll understand how to discover and interpret customer pain, and learn how to use this research to guide your team through each step of product creation.Written for designers, product managers, and others who want to communicate better with designers, this book is essential reading for anyone who contributes to the product creation process.Understand exactly who your customers are, what they want, and how to build products that make them happyLearn frameworks and principles that successful product designers useIncorporate five states into every screen of your interface to improve conversions and reduce perceived loading timesDiscover meeting techniques that Apple, Amazon, and LinkedIn use to help teams solve the right problems and make decisions fasterDesign effective interfaces across different form factors by understanding how people hold devices and complete tasksLearn how successful designers create working prototypes that capture essential customer feedbackCreate habit-forming and emotionally engaging experiences, using the latest psychological research