Techniques for Capturing and Communicating Solution Requirements for IT Projects in Lean Use Case Format.

What you'll learn

Document user interaction in Lean Use Cases descriptions and diagrams
Define and defend the need for Lean Use Cases
Describe the major components of a Lean Use Case
Determine how to handle alternate and exception situations
Extract Use Cases from a Vision Statement
Apply Business Event Analysis to discover Lean Use Cases based on business activities
Analyze business scenarios to discover Lean Use Cases

Requirements

No technical background required
The course has no prerequisites
No additional materials are required
Interest in the field of Business Analysis for Information Technology

Description

Business Use Cases Help You Manage Complexity

Use Case Models are well suited to build a product backlog.
They are the ideal tool to identify, clarify, and organize functional software requirements for a digital solution.

Use Cases define the interactions between people and technology. As a business user of IT solutions, a Use Case enables you to talk to technologists about your IT business needs in a manner they can understand. As a technical professional, a Use Case enables you to talk about technology to the business community without using technical jargon.

Lean Use Cases are becoming the de facto standard for defining and communicating functional requirements in Lean and Agile environments. Applying the Lean philosophy of waste reduction to the Use Case concept creates a powerful tool for communication to and within a Lean or Agile Software Development team.

User Stories and other forms of textual requirements often lack context making room for ambiguity. Use Case Models, however, provide this context and are easily understandable by all stakeholders, including customers, users and managers, not just developers and testers.

Writing a Lean Use Case is a skill that anyone in an organization can easily acquire. Learning how to write and manage Lean Use Cases at varying levels of detail is a major step in getting your IT applications to do what you want them to do. Knowing why you need a Lean Use Case, when to create one (especially in a lean environment), and where to put what information is critical to creating high-quality functional requirements.

You Will Learn How to Make Use Cases Work in a Lean / Agile Setting

This exercise and example-rich business analysis training course explains the who, what, when, where, how and why of Lean Use Case models. Learn how to make Use Cases fit in the overall process of Lean and Agile software development by starting small with just enough detail at every point in the Agile development process.

To easily discover Use Cases, we include a section on Event-Response Analysis, Vision Statement Analysis, and Example- or Scenario-based Use Case Identification.

After finishing this course, you will be able to write high-quality Use Cases defining actors, pre-conditions, post-conditions, main paths, alternate paths, and exception paths.


WARNING: People responsible for writing non-technical (Business-oriented) Use Cases from the User perspective are our primary target audience. Business Use Cases are written in a technology-agnostic manner defining actions that the business needs to perform to create a meaningful, observable result. We designed this course specifically to address that audience, meaning it does not address the creation or use of System-level Use Cases. System Use Cases are at a much lower level of detail and usually a tool for technical professionals (developers, software engineers, testers, etc.) to help them create the design for a new technology solution.

Developers who want to understand Use Cases that are codable will not find anything at that level of detail in this course. You have been warned. Thank you for taking this into consideration before buying this course.

Who this course is for:

Anyone who wants to communicate business needs and wants for a future IT solution. Targeted towards members of Lean and Agile teams. Examples:
Product Owners
Business Analysts
Requirements Engineers
Business- and Customer-side Team Members
Subject Matter Experts (SME)
Project Leaders and Managers