Getting and Writing IT Require

Communicate Business Needs in an Agile (e.g. Scrum) or Lean (e.g. Kanban) Environment

Problem solvers are in demand in every organization, large and small, from a Mom and Pop shop to the federal government. Increase your confidence and your value to organizations by improving your ability to analyze, express, and discuss business needs in formats supported by Agile, Lean, and DevOps.

The single largest challenge facing organizations around the world is how to leverage their Information Technology to gain competitive advantage. This is not about how to program the devices; it is figuring out what the devices should do. The skills needed to identify and define the best IT solutions are invaluable for every role in the organization. These skills can propel you from the mail room to the boardroom by making your organization more effective and more profitable.

Whether you:

• are tasked with defining business needs for a product or existing software,
• need to prove that a digital solution works,
• want to expand your User Story and requirements discovery toolkit, or
• are interested in becoming a Business Analyst,

this book presents invaluable ideas that you can steal. The future looks bright for those who embrace Lean concepts and are prepared to engage with the business community to ensure the success of Agile initiatives.

Learn Step by Step When and How to Define Lean / Agile Requirements

Agile, Lean, DevOps, and Continuous Delivery do not change the need for good business analysis. In this book, you will learn how the new software development philosophies influence the discovery, expression, and analysis of business needs. We will cover User Stories, Features, and Quality Requirements (a.k.a. Non-functional Requirements - NFR). User Story Splitting and Feature Drill-down transform business needs into technology solutions.

Acceptance Tests (Scenarios, Scenario Outlines, and Examples) have become a critical part of many Lean development approaches. To support this new testing paradigm, you will also learn how to identify and optimize Scenarios, Scenario Outlines, and Examples in GIVEN-WHEN-THEN format (Gherkin) that are the bases for Acceptance Test Driven Development (ATDD) and Behavior Driven Development (BDD).

This book presents concrete approaches that take you from day one of a change initiative to the ongoing acceptance testing in a continuous delivery environment. The authors introduce novel and innovative ideas that augment tried-and-true techniques for:

• discovering and capturing what your stakeholders need,
• writing and refining the needs as the work progresses, and
• developing scenarios to verify that the software does what it should.

Approaches that proved their value in conventional settings have been redefined to ferret out and eliminate waste (a pillar of the Lean philosophy). Those approaches are fine-tuned and perfected to support the Lean and Agile movement that defines current software development. In addition, the book is chock-full of examples and exercises that allow you to confirm your understanding of the presented ideas.

Who Should Read 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. This book targets the neglected business roles such as Product Owners, Business Analysts, Test Developers, Business-side and Agile Team Members, Subject Matter Experts, and Product Managers.

Who Wrote It?

The authors, Tom and Angela have taught thousands of students in face-to-face training, published 7 books, authored 9 courses on Udemy.com with 25K students, and enriched the global community with 1.5 million views on their YouTube channel.