Description

About the course:

As you and your team work through a case study project, you’ll learn how to use agile analysis tools to help teams overcome some of the most vexing issues that confront agile teams today, including: how to work with the business to develop a product development strategy on an agile project, how to help business owners overcome ‘prioritization phobia’ by guiding them towards iterative, MVP/MMP development; how to track dependencies between requirements; how and when to unbundle epics into manageable User Stories; when to ‘bend’ agile principles; how to apply UML 2.0; and how to manage supplementary requirements such as non-functional requirements and constraints. You will also learn when and how to create requirements documentation for communication with non-agile teams and for future use on Maintenance and Enhancement initiatives after the project is over.

Objectives:

• Be able to carry out the Business Analysis function on an agile project using an ‘end-to-end’ agile analysis approach that grows requirements from business needs to detailed User Requirements.
• Implement an integrated lean, agile analysis approach that ties together tools from Scrum, Lean Startup, Extreme Programming (XP) User Stories, Story Mapping, Kanban and Use Case 2.0.
• Be able to guide the business in agile planning at various horizons: Strategic (long-term) planning; Mid-term (Quarterly/Release Planning); Short-term (next 2-3 weeks).
• Be able to integrate Lean Startup principles and practices into the product development lifecycle – from visioning through development to final validation in the marketplace.
• Be able to help guide Customers towards an MVP/MMP (Minimum Viable Product/Minimum Marketable Product) iterative approach to development.
• Be able to split epics into valuable User Stories by applying the Lawrence Patterns and INVEST
• Create high-quality User Stories.
• Be able to guide the Customer to make effective choices for the iterative rollout of features in a way that maximizes business value early.
• Trace User Stories and iteration (Sprint) goals backwards to Use Cases, business processes and business needs; forwards to tests and solution artifacts; and horizontally, to track dependencies between requirements.
• Know when and how to create Acceptance Criteria using the BDD template.
• Identify analysis and implementation gaps in each iteration and be able to forecast the need for temporary workarounds.
• Identify and document defect-handling activities (‘bug fixes’) within the User Story approach.