Fifty Quick Ideas To Improve Your User Stories

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.

Learn how to improve retrospectives and avoid stagnation, with fifty ideas designed to help you enhance and energise your continuous improvement effort. This book will help you get better outcomes from retrospectives and from any continuous improvement initiative. It will help you consider how best to prepare for retrospectives, generate innovative insights, achieve valuable outcomes, improve facilitation techniques, keep things fresh and maybe even how to have a bit of fun whilst doing it. This book is for anyone who undertakes continuous improvement of any sort, especially those looking to get better outcomes from retrospectives, either as a participant, facilitator, coach or manager of teams. We include ideas for people with varying levels of experience. So, whether you are just getting started with Scrum and retrospectives, or a veteran of continuous improvement looking to fine-tune or get new ideas, or if your retrospectives have become a bit stale and need re-invigorating, there are ideas in here to support you.

A practical guide to impact mapping, a simple yet incredibly effective method for collaborative strategic planning that helps organizations make an impact with software.

WHAT IS THIS BOOK ABOUT? This Book Is About the “Card” (User Story: Card, Criteria, Conversation) User Stories are a great method for expressing stakeholder requirements, whether your projects follow an Agile, Iterative, or a Waterfall methodology. They are the basis for developers to deliver a suitable information technology (IT) app or application. Well-structured user stories express a single action to achieve a specific goal from the perspective of a single role. When writing user stories, stakeholders knowledgeable about the role should focus on the business result that the IT solution will enable while leaving technology decisions up to the developers. Good user stories are relevant to the project, unambiguous, and understandable to knowledge peers. The best user stories also contain crucial non-functional (quality) requirements, which are the best weapon in the war against unsatisfactory performance in IT solutions. 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 five 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. This book targets business professionals who are involved with an IT project, Product Owners in charge of managing a backlog, or Business Analysts working with an Agile team. Author’s Note The 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. WHO WILL BENEFIT FROM READING THIS BOOK? How organizations develop and deliver working software has changed significantly in recent years. Because the change was greatest in the developer community, many books and courses justifiably target that group. There is, however, an overlooked group of people essential to the development of software-as-an-asset that have been neglected. Many distinct roles or job titles in the business community perform business needs analysis for digital solutions. They include: - Product Owners - Business Analysts - Requirements Engineers - Test Developers - Business- and Customer-side Team Members - Agile Team Members - Subject Matter Experts (SME) - Project Leaders and Managers - Systems Analysts and Designers - AND “anyone wearing the business analysis hat”, meaning anyone responsible for defining a future IT solution TOM AND ANGELA’S (the authors) STORY Like all good IT stories, theirs started on a project many years ago. Tom was the super techie, Angela the super SME. They fought their way through the 3-year development of a new policy maintenance system for an insurance company. They vehemently disagreed on many aspects, but in the process discovered a fundamental truth about IT projects. The business community (Angela) should decide on the business needs while the technical team’s (Tom)’s job was to make the technology deliver what the business needed. Talk about a revolutionary idea! All that was left was learning how to communicate with each other without bloodshed to make the project a resounding success. Mission accomplished. They decided this epiphany was so important that the world needed to know about it. As a result, they made it their mission (and their passion) to share this ground-breaking concept with the rest of the world. To achieve that lofty goal, they married and began the mission that still defines their life. After over 30 years of living and working together 24x7x365, they are still wildly enthusiastic about helping the victims of technology learn how to ask for and get the digital (IT) solutions they need to do their jobs better. More importantly, they are more enthusiastically in love with each other than ever before!

Set in the future when "firemen" burn books forbidden by the totalitarian "brave new world" regime.

NEW YORK TIMES BESTSELLER For the first time, Curtis “50 Cent” Jackson opens up about his amazing comeback—from tragic personal loss to thriving businessman and cable’s highest-paid executive—in this unique self-help guide, his first since his blockbuster New York Times bestseller The 50th Law. In his early twenties Curtis Jackson, known as 50 Cent rose to the heights of fame and power in the cutthroat music business. A decade ago the multi-platinum selling rap artist decided to pivot. His ability to adapt to change was demonstrated when he became the executive producer and star of Power, a high-octane, gripping crime drama centered around a drug kingpin’s family. The series quickly became “appointment” television, leading to Jackson inking a four-year, $150 million contract with the Starz network—the most lucrative deal in premium cable history. Now, in his most personal book, Jackson shakes up the self-help category with his unique, cutting-edge lessons and hard-earned advice on embracing change. Where The 50th Law tells readers “fear nothing and you shall succeed,” Hustle Harder, Hustle Smarter builds on this message, combining it with Jackson’s street smarts and hard-learned corporate savvy to help readers successfully achieve their own comeback—and to learn to flow with the changes that disrupt their own lives.

With plenty of ideas, suggestions, and practical cases on software quality, this book will help you to improve the quality of your software and to deliver high-quality products to your users and satisfy the needs of your customers and stakeholders. Many methods for product quality improvement start by investigating the problems, and then work their way back to the point where the problem started. For instance audits and root cause analysis work this way. But what if you could prevent problems from happening, by building an understanding what drives quality, thus enabling to take action before problems actually occur? What Drives Quality explores how quality plays a role in all of the software development activities. It takes a deep dive into quality by listing the relevant factors of development and management activities that drive the quality of software products. It provides a lean approach to quality by analyzing the full development chain from customer requests to delivering products to users. I'm aiming this book at software developers and testers, architects, product owners and managers, agile coaches, Scrum masters, project managers, and operational and senior managers who consider quality to be important. A book on quality should be practical. It should help you, the reader of this book, to improve the quality of your software and deliver better products. It should inspire you and give you energy to persevere on your quality journey. What drives quality tries to do just that, and more. This book is based on my experience as a developer, tester, team leader, project manager, quality manager, process manager, consultant, coach, trainer, and adviser in Agile, Lean, Quality and Continuous Improvement. It takes a deep dive into quality with views from different perspectives and provides ideas, suggestions, practices, and experiences that will help you to improve quality of the products that your organization is delivering. This book views software quality from an engineering, management, and social perspective. It explores the interaction between all involved in delivering high-quality software to users and provides ideas to do it quicker and at lower costs.

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.