Agile Software Requirements


Book Description

“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.




Requirements Engineering and Management for Software Development Projects


Book Description

Requirements Engineering and Management for Software Development Projects presents a complete guide on requirements for software development including engineering, computer science and management activities. It is the first book to cover all aspects of requirements management in software development projects. This book introduces the understanding of the requirements, elicitation and gathering, requirements analysis, verification and validation of the requirements, establishment of requirements, different methodologies in brief, requirements traceability and change management among other topics. The best practices, pitfalls, and metrics used for efficient software requirements management are also covered. Intended for the professional market, including software engineers, programmers, designers and researchers, this book is also suitable for advanced-level students in computer science or engineering courses as a textbook or reference.




Managing Software Requirements the Agile Way


Book Description

Learn how to deliver software that meets your clients’ needs with the help of a structured, end-to-end methodology for managing software requirements and building suitable systems Key FeaturesLearn how to communicate with a project’s stakeholders to elicit software requirementsDeal every phase of the requirement life cycle with pragmatic methods and techniquesManage the software development process and deliver verified requirements using Scrum and KanbanBook Description Difficulty in accurately capturing and managing requirements is the most common cause of software project failure. Learning how to analyze and model requirements and produce specifications that are connected to working code is the single most fundamental step that you can take toward project success. This book focuses on a delineated and structured methodology that will help you analyze requirements and write comprehensive, verifiable specifications. You'll start by learning about the different entities in the requirements domain and how to discover them based on customer input. You’ll then explore tried-and-tested methods such as impact mapping and behavior-driven development (BDD), along with new techniques such as D3 and feature-first development. This book takes you through the process of modeling customer requirements as impact maps and writing them as executable specifications. You’ll also understand how to organize and prioritize project tasks using Agile frameworks, such as Kanban and Scrum, and verify specifications against the delivered code. Finally, you'll see how to start implementing the requirements management methodology in a real-life scenario. By the end of this book, you'll be able to model and manage requirements to create executable specifications that will help you deliver successful software projects. What you will learnKick-start the requirements-gathering and analysis process in your first meeting with the clientAccurately define system behavior as featuresModel and describe requirement entities using Impact Mapping and BDDCreate a feature-based product backlog and use it to drive software developmentWrite verification code to turn features into executable specificationsDeliver the right software and respond to change using either Scrum or KanbanChoose appropriate software tools to provide transparency and traceability to your clientsWho this book is for This book is for software engineers, business analysts, product managers, project managers, and software project stakeholders looking to learn a variety of techniques and methodologies for collating accurate software requirements. A fundamental understanding of the software development life cycle (SDLC) is needed to get started with this book. Although not necessary, basic knowledge of the Agile philosophy and practices, such as Scrum, along with some programming experience will help you to get the most out of this book.




Creating Requirements for Software Projects: A Business Analyst's Guide to Requirements Management


Book Description

If you're new to writing requirements, and you're assigned to a new enterprise software or IT project to create requirements, where do you begin? How do you elicit requirements effectively from stakeholders? What's a good requirement versus a bad one? This book explains how to write requirements according to the standards in A Guide to the Business Analysis Body of Knowledge(R) (the BABOK(R) Guide) published by the International Association of Business Analysts. It describes the process you'll need to go through from start to finish, from the point that you're assigned to the project to when you finalize your requirements. It provides suggestions for tools, processes, and techniques you'll need to develop quality-oriented requirements for your stakeholders, all aligned with the knowledge areas of the BABOK(R) Guide. Some examples of requirements for the Agile software methodology are also provided. This book is written by Pamela Paterson, MS, CBAP, who is a senior business analyst with over 20 years of experience on enterprise IT projects. Pamela has written several books, including the #1 international best-seller Get the Job.




User Stories Applied


Book Description

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.




Software Requirements Essentials


Book Description

20 Best Practices for Developing and Managing Requirements on Any Project Software Requirements Essentials presents 20 core practices for successful requirements planning, elicitation, analysis, specification, validation, and management. Leading requirements experts Karl Wiegers and Candase Hokanson focus on the practices most likely to deliver superior value for both traditional and agile projects, in any application domain. These core practices help teams understand business problems, engage the right participants, articulate better solutions, improve communication, implement the most valuable functionality in the right sequence, and adapt to change and growth. Concise and tightly focused, this book offers just enough pragmatic "how-to" detail for you to apply the core practices with confidence, whether you're a business analyst, requirements engineer, product manager, product owner, or developer. Using it, your entire team can build a shared understanding of key concepts, terminology, techniques, and rationales--and work together more effectively on every project. Learn how to: Clarify problems, define business objectives, and set solution boundaries Identify stakeholders and decision makers Explore user tasks, events, and responses Assess data concepts and relationships Elicit and evaluate quality attributes Analyze requirements and requirement sets, create models and prototypes, and set priorities Specify requirements in a consistent, structured, and well-documented fashion Review, test, and manage change to requirements "I once read the ten best-selling requirements engineering books of the prior ten years. This one book succinctly presents more useful information than those ten books combined." --Mike Cohn, author of User Stories Applied and co-founder, Scrum Alliance "Diamonds come about when a huge amount of carbon atoms are compressed. Karl and Candase have done something very similar: they have compressed their vast requirements knowledge into 20 gems they call 'core practices.' These practices are potent stuff, and I recommend that they become part of everyone's requirements arsenal." --James Robertson, author of Mastering the Requirements Process and Business Analysis Agility "Long story short: if you are going to read only one requirements book, this is it. Software Requirements Essentials distills the wealth of information found in Software Requirements and many other texts down to twenty of the most important requirements activities that apply on nearly all projects. Today's busy BA simply doesn't have the time to read a lengthy instructive guide front-to-back. But they should find the time to read this book." --From the Foreword by Joy Beatty, COO, ArgonDigital "Software Requirements Essentials will be a high-value addition to your business analysis library. Anyone looking to improve their business analysis practices will find great practical advice they'll be able to apply immediately." --Laura Paton, Principal Consultant, BA Academy, Inc. Register your book for convenient access to downloads, updates, and/or corrections as they become available. See inside book for details.




Requirements Development Guidebook


Book Description

"How do I know I covered all the requirements? Where do I begin? When should I stop? Did I miss something that will result in unpleasant surprises down the road?" If you are a Business Analyst, these questions will certainly mean something to you. You've probably asked yourself these questions at one point or another when you were assigned your early requirements development tasks.In this book, I introduce a requirements development roadmap that will guide you from start to finish. It is a plan carefully prepared and organized around consecutive stations. At each station, I tell you:1. The target objective, and why you need to think about that particular objective at that specific point in time2. Which elicitation techniques will best serve the objective, and which questions to ask in order to capture the information you need3. Which analysis tools to apply in order to analyze the information from different angles4. How to document the output of the exercise that you just performed




Software Requirements


Book Description

In Software Requirements, you'll discover practical, effective techniques for managing the requirements engineering process all the way through the development cycle--including tools to facilitate that all-important communication between users, developers, and management. Use them to: Book jacket.




Mastering the Requirements Process


Book Description

One of the joys of product development, whether it be software, service, or hardware, is getting it right. The way to get it right is to uncover the real business problem, and to write the requirements for the solution that best solves that problem. Without the right requirements it is impossible to build the right solution. Mastering the Requirements Process, Fourth Edition, gives you an industry-proven process for getting to the essence of the business problem and then writing unambiguous and testable requirements for its solution. This fourth edition is an almost complete rewrite that brings requirements discovery into today's world--it is the book for today's business analyst. Product owners and project leaders will also find it valuable as it explains how to discover precisely what the customer needs and wants, and to do it effectively in any business or project environment. The book tells you how to: Use the Volere requirements process to discover requirements in both traditional and agile environments Incorporate off-the-shelf (OTS) solutions into your requirements discovery Use artificial intelligence (AI) as part of your requirements discovery, and as part of your business solution Use quickly sketched prototypes to explore the problem space Understand functional and non-functional requirements Write better agile stories Make your requirements and stories measurable and testable using fit criteria Use business events as the heartbeat of business analysis Discover requirements in agile, commercial, and milspec project environments Find and prioritize your customer segments Leverage systems thinking when discovering requirements Use story maps and other requirements repository techniques Know which trawling techniques are the most effective for requirements discovery Synchronize your requirements discovery with agile development teams Make better decisions in the early days of a project to increase your chances of success Employ the Volere requirements specification template (downloaded 10,000+ times) as the basis for your own requirement specifications "One of the most valuable things about this book is that it provides a process to follow that will get people asking the right questions and expand their perspective on the problem." --Kevin Brennan Register your book for convenient access to downloads, updates, and/or corrections as they become available. See inside book for details.




Safety and Health for Engineers


Book Description

SAFETY AND HEALTH FOR ENGINEERS A comprehensive resource for making products, facilities, processes, and operations safe for workers, users, and the public Ensuring the health and safety of individuals in the workplace is vital on an interpersonal level but is also crucial to limiting the liability of companies in the event of an onsite injury. The Bureau of Labor Statistics reported over 4,700 fatal work injuries in the United States in 2020, most frequently in transportation-related incidents. The same year, approximately 2.7 million workplace injuries and illnesses were reported by private industry employers. According to the National Safety Council, the cost in lost wages, productivity, medical and administrative costs is close to 1.2 trillion dollars in the US alone. It is imperative—by law and ethics—for engineers and safety and health professionals to drive down these statistics by creating a safe workplace and safe products, as well as maintaining a safe environment. Safety and Health for Engineers is considered the gold standard for engineers in all specialties, teaching an understanding of many components necessary to achieve safe workplaces, products, facilities, and methods to secure safety for workers, users, and the public. Each chapter offers information relevant to help safety professionals and engineers in the achievement of the first canon of professional ethics: to protect the health, safety, and welfare of the public. The textbook examines the fundamentals of safety, legal aspects, hazard recognition and control, the human element, and techniques to manage safety decisions. In doing so, it covers the primary safety essentials necessary for certification examinations for practitioners. Readers of the fourth edition of Safety and Health for Engineers readers will also find: Updates to all chapters, informed by research and references gathered since the last publication The most up-to-date information on current policy, certifications, regulations, agency standards, and the impact of new technologies, such as wearable technology, automation in transportation, and artificial intelligence New international information, including U.S. and foreign standards agencies, professional societies, and other organizations worldwide Expanded sections with real-world applications, exercises, and 164 case studies An extensive list of references to help readers find more detail on chapter contents A solution manual available to qualified instructors Safety and Health for Engineers is an ideal textbook for courses in safety engineering around the world in undergraduate or graduate studies, or in professional development learning. It also is a useful reference for professionals in engineering, safety, health, and associated fields who are preparing for credentialing examinations in safety and health.