What Is “LEAN” or "AGILE" Business Analysis?
- 44 mins on-demand video
- 1 article
- Full lifetime access
- Access on mobile and TV
- Certificate of Completion
Get your team access to Udemy's top 3,000+ courses anytime, anywhere.Try Udemy for Business
- Understand how lean principles affect business analysis and the requirements definition process
Explain what lean requirements such as Features, User Stories, Epics, Scenarios, etc. look like in a lean and agile world
Apply lean principles to known business analysis techniques
Get to know your instructor and learn what topics will be covered in this overview.
A brief look at modern software development methods, their primary focus and methodologies.
Traditional Business Analysis contains a lot of waste. The lecture will show you the 9 most common wastes.
Lean or Agile Business Analysis is about combating waste. After this lecture you know which changes are necessary for your to your current Business Analysis Process to eliminate waste and optimally support new software development methods.
To communicate requirements to software developers, we still need to document them somehow and somewhere. However, the “traditional BRD" does not work in the lean and agile world. You probably know what I mean with "traditional BRD": Pages and Pages of documents with lots of sections which scream “Fill me or the document isn’t complete!”. This lecture shows what requirements repositories look like in a lean and agile world.
The biggest difference between lean and traditional business analysis is the timing of the activities. Whereas conventionally business analysis has been primarily conducted at the start of a project, it is now an ongoing process throughout the product life cycle.
Cynefin is an amazing new technique that belongs in every business analyst's tool box. The Cynefin framework exists to help us realize that all requirements are not created equal and to help us understand that different situations might require different responses to successfully navigate them.
In today's software development environment, good User Stories tend to be small. They typically represent at a few person-weeks worth of work. Typically, a Product Owner or the business side teams will make Features, Epics, and User Stories ready for developers.
- No tools or knowledge required
- Interest in Business Analysis for Information Technology (IT) and Software Requirements Definition / Analysis
Take the Path to LEAN Business Analysis (as it relates to Information Technology)
In today’s world, you and your organization must be responsive, flexible, and make things happen quickly. You must do more with less – and faster. You no longer have business as usual, so why do business analysis as usual?
With the widespread adoption of Agile, software development has gone through some serious remodeling. Agile teams build robust products incrementally and iteratively, requiring fast feedback from the business community to define ongoing work. As a result, the process of defining IT requirements is evolving rapidly. Backlogs replace requirements definition documents. User Stories, Epics and Features replace requirement statements. Scenarios and Examples replace test cases. The timing of business analysis activities is shifting like sand.
This course is a brief overview of how you can reduce waste in Business Analysis practices to optimally support the new lean and agile software development world. You will learn about topics such as:
· The purpose of a product roadmap and a prioritized product backlog
· The concept of a Minimum Viable Product (MVP)
· Agile and Lean thinking applied to requirements discovery, analysis, and acceptance testing
· Lean requirement constructs such as Features, User Stories, Epics, Scenarios, Examples, etc.
· The importance of feedback from your customers to improve the product
- Business Analysts
- Product Owners
- Subject Matter Experts
- Project Managers
- Managers of all levels
- Business Architects
- Anyone interested in Business Analysis for IT projects