This book will help you write better stories, spot and fix common issues, split stories so that they are smaller but still valuable, and deal with difficult stuff like crosscutting concerns, long-term effects and non-functional requirements. Above all, this book will help you achieve the promise of agile and iterative delivery: to ensure that the right stuff gets delivered through productive discussions between delivery team members and business stakeholders. Who is this book for? This is a book for anyone working in an iterative delivery environment, doing planning with user stories. The ideas in this book are useful both to people relatively new to user stories and those who have been working with them for years. People who work in software delivery, regardless of their role, will find plenty of tips for engaging stakeholders better and structuring iterative plans more effectively. Business stakeholders working with software teams will discover how to provide better information to their delivery groups, how to set better priorities and how to outrun the competition by achieving more with less software. What's inside? Unsurprisingly, the book contains exactly fifty ideas. They are grouped into five major parts: - Creating stories: This part deals with capturing information about stories before they get accepted into the delivery pipeline. You'll find ideas about what kind of information to note down on story cards and how to quickly spot potential problems. - Planning with stories: This part contains ideas that will help you manage the big-picture view, set milestones and organise long-term work. - Discussing stories: User stories are all about effective conversations, and this part contains ideas to improve discussions between delivery teams and business stakeholders. You'll find out how to discover hidden assumptions and how to facilitate effective conversations to ensure shared understanding. - Splitting stories: The ideas in this part will help you deal with large and difficult stories, offering several strategies for dividing them into smaller chunks that will help you learn fast and deliver value quickly. - Managing iterative delivery: This part contains ideas that will help you work with user stories in the short and mid term, manage capacity, prioritise and reduce scope to achieve the most with the least software. About the authors: Gojko Adzic is a strategic software delivery consultant who works with ambitious teams to improve the quality of their software products and processes. Gojko's book Specification by Example was awarded the #2 spot on the top 100 agile books for 2012 and won the Jolt Award for the best book of 2012. In 2011, he was voted by peers as the most influential agile testing professional, and his blog won the UK agile award for the best online publication in 2010. David Evans is a consultant, coach and trainer specialising in the field of Agile Quality. David helps organisations with strategic process improvement and coaches teams on effective agile practice. He is regularly in demand as a conference speaker and has had several articles published in international journals.
This book is for cross-functional teams working in an iterative delivery environment, planning with user stories and testing frequently changing software under tough time pressure. This book will help you test your software better, easier and faster. Many of these ideas also help teams engage their business stakeholders better in defining key expectations and improve the quality of their software products.
Author: Jeff Patton
Publisher: "O'Reilly Media, Inc."
Release Date: 2014-09-05
Genre: Business & Economics
User story mapping is a valuable tool for software development, once you understand why and how to use it. This insightful book examines how this often misunderstood technique can help your team stay focused on users and their needs without getting lost in the enthusiasm for individual product features. Author Jeff Patton shows you how changeable story maps enable your team to hold better conversations about the project throughout the development process. Your team will learn to come away with a shared understanding of what you’re attempting to build and why. Get a high-level view of story mapping, with an exercise to learn key concepts quickly Understand how stories really work, and how they come to life in Agile and Lean projects Dive into a story’s lifecycle, starting with opportunities and moving deeper into discovery Prepare your stories, pay attention while they’re built, and learn from those you convert to working software
Bridging the Communication Gap is a book about improving communication between customers, business analysts, developers and testers on software projects, especially by using specification by example and agile acceptance testing. These two key emerging software development practices can significantly improve the chances of success of a software project. They ensure that all project participants speak the same language, and build a shared and consistent understanding of the domain. This leads to better specifications, flushes out incorrect assumptions and ensures that functional gaps are discovered before the development starts. With these practices in place you can build software that is genuinely fit for purpose.
Describes a method of effectively specifying, testing, and delivering software, covering such topics as documentation, process patterns, and automation, along with case studies from a variety of firms.
Humans vs Computers is a book about ordinary people caught between wrong assumptions and computer bugs. You'll read about humans who are invisible to computers, how a default password caused a zombie apocalypse and why airlines sometimes give away free tickets. This is also a book on how to prevent, avoid and reduce the impact of such problems.
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.
DescriptionUser Stories are a great method for expressing stakeholder requirements, whether your projects follow an Agile, Iterative, or a Waterfall methodology. This book presents two common User Story structures to help you ensure that your User Stories have all the required components and that they express the true business need as succinctly as possible. It offers 5 simple rules to ensure that your User Stories are the best that they can be. That, in turn, will reduce the amount of time needed in User Story elaboration and discussion with the development team.After reading this book you will be able to:* Translate business needs into well-structured User Stories* Write User Stories that express the what and avoid the how* Apply five simple rules for writing effective User Stories* Clarify assumptions in User Stories by adding context* Identify and remove ambiguous and subjective terms and phrases in User Stories* Select the appropriate format for expressing User Stories for Agile Projects* Write stakeholder requirements in User Story format that solve business problems* Elaborate User Stories to identify measurable non-functional requirementsAuthor's NoteThe term "User Story" is a relative new addition to our language and its definition is evolving. In today's parlance, a complete User Story has three primary components, namely the "Card", the "Conversation", and the "Criteria". Different roles are responsible for creating each component. The "Card" expresses a business need. A representative of the business community is responsible for expressing the business need. Historically (and for practical reasons) the "Card" is the User Story from the perspective of the business community. Since we wrote this book specifically to address that audience, we use the term "User Story" in that context throughout. The "Conversation" is an ongoing discussion between a developer responsible for creating software that meets the business need and the domain expert(s) who defined it (e.g., the original author of the "Card"). The developer initiates the "Conversation" with the domain expert(s) to define the "Criteria" and any additional information the developer needs to create the application. There is much to be written about both the "Conversation" and the "Criteria", but neither component is dealt with in any detail in this publication. A well-written User Story ("Card") can drastically reduce the time needed for the "Conversation". It reduces misinterpretations, misunderstandings, and false starts, thereby paving the way for faster delivery of working software. We chose to limit the content of this publication to the "User Story" as understood by the business community to keep the book focused and address the widest possible audience.
Agile Estimating and Planning is the definitive, practical guide to estimating and planning agile 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.
Learn how to use stories throughout the agile software development lifecycle. Through lessons and examples, Agile UX Storytelling demonstrates to product owners, customers, scrum masters, software developers, and designers how to craft stories to facilitate communication, identify problems and patterns, refine collaborative understanding, accelerate delivery, and communicate the business value of deliverables. Rebecca Baker applies the techniques of storytelling to all facets of the software development lifecycle—planning, requirements gathering, internal and external communication, design, and testing—and shows how to use stories to improve the delivery process. What You'll Learn Craft stories to facilitate communication within the project team and with stakeholders Leverage stories to identify problems and patterns, accelerate delivery, and communicate business value Apply storytelling techniques to all stages of the SDLC Marshal user stories to focus requirements gathering and ensure a consistent message Who This Book Is For All SDLC and UX roles: product owners, customers, scrum masters, software developers, and UX designers
Author: Jeff Sutherland
Publisher: Broadway Business
Release Date: 2014
Genre: Business & Economics
Looks at the "scrum" project management system popular in the technology industry, and how it may be implemented in other fields to increase productivity through customer feedback and a process of constant reiteration.
Author: Brendon Burchard
Publisher: Hay House, Inc
Release Date: 2017-09-19
Genre: Business & Economics
THESE HABITS WILL MAKE YOU EXTRAORDINARY. Twenty years ago, author Brendon Burchard became obsessed with answering three questions: 1. Why do some individuals and teams succeed more quickly than others and sustain that success over the long term? 2. Of those who pull it off, why are some miserable and others consistently happy on their journey? 3. What motivates people to reach for higher levels of success in the first place, and what practices help them improve the most After extensive original research and a decade as the world’s leading high performance coach, Burchard found the answers. It turns out that just six deliberate habits give you the edge. Anyone can practice these habits and, when they do, extraordinary things happen in their lives, relationships, and careers. Which habits can help you achieve long-term success and vibrant well-being no matter your age, career, strengths, or personality? To become a high performer, you must seek clarity, generate energy, raise necessity, increase productivity, develop influence, and demonstrate courage. The art and science of how to do all this is what this book is about. Whether you want to get more done, lead others better, develop skill faster, or dramatically increase your sense of joy and confidence, the habits in this book will help you achieve it faster. Each of the six habits is illustrated by powerful vignettes, cutting-edge science, thought-provoking exercises, and real-world daily practices you can implement right now. If you’ve ever wanted a science-backed, heart-centered plan to living a better quality of life, it’s in your hands. Best of all, you can measure your progress. A link to a free professional assessment is included in the book.
Design IT Organizations for Agility at Scale Aspiring digital businesses need overall IT agility, not just development team agility. In Agile IT Organization Design , IT management consultant and ThoughtWorks veteran Sriram Narayan shows how to infuse agility throughout your organization. Drawing on more than fifteen years’ experience working with enterprise clients in IT-intensive industries, he introduces an agile approach to “Business–IT Effectiveness” that is as practical as it is valuable. The author shows how structural, political, operational, and cultural facets of organization design influence overall IT agility—and how you can promote better collaboration across diverse functions, from sales and marketing to product development, and engineering to IT operations. Through real examples, he helps you evaluate and improve organization designs that enhance autonomy, mastery, and purpose: the key ingredients for a highly motivated workforce. You’ll find “close range” coverage of team design, accountability, alignment, project finance, tooling, metrics, organizational norms, communication, and culture. For each, you’ll gain a deeper understanding of where your organization stands, and clear direction for making improvements. Ready to optimize the performance of your IT organization or digital business? Here are practical solutions for the long term, and for right now. Govern for value over predictability Organize for responsiveness, not lowest cost Clarify accountability for outcomes and for decisions along the way Strengthen the alignment of autonomous teams Move beyond project teams to capability teams Break down tool-induced silos Choose financial practices that are free of harmful side effects Create and retain great teams despite today’s “talent crunch” Reform metrics to promote (not prevent) agility Evolve culture through improvements to structure, practices, and leadership—and careful, deliberate interventions
Uncover surprises, risks, and potentially serious bugs with exploratory testing. Rather than designing all tests in advance, explorers design and execute small, rapid experiments, using what they learned from the last little experiment to inform the next. Learn essential skills of a master explorer, including how to analyze software to discover key points of vulnerability, how to design experiments on the fly, how to hone your observation skills, and how to focus your efforts. Software is full of surprises. No matter how careful or skilled you are, when you create software it can behave differently than you intended. Exploratory testing mitigates those risks. Part 1 introduces the core, essential skills of a master explorer. You'll learn to craft charters to guide your exploration, to observe what's really happening (hint: it's harder than it sounds), to identify interesting variations, and to determine what expected behavior should be when exercising software in unexpected ways. Part 2 builds on that foundation. You'll learn how to explore by varying interactions, sequences, data, timing, and configurations. Along the way you'll see how to incorporate analysis techniques like state modeling, data modeling, and defining context diagrams into your explorer's arsenal. Part 3 brings the techniques back into the context of a software project. You'll apply the skills and techniques in a variety of contexts and integrate exploration into the development cycle from the very beginning. You can apply the techniques in this book to any kind of software. Whether you work on embedded systems, Web applications, desktop applications, APIs, or something else, you'll find this book contains a wealth of concrete and practical advice about exploring your software to discover its capabilities, limitations, and risks.