×
Please Provide Following Information. We will get back to you as soon as possible.




×

Please Provide Below Information.




HRDF CLAIMABLE

This program is eligible for the HRDF training grant claims under the TRAINING ASSISTANCE SCHEME (SBL SCHEME). Click on the below link to know the eligibility criteria and claim procedure.

HRDF Claim Eligibility and Procedure

Agile Business Analysis Workshop

37% project fails due to incomplete requirement, poor specification and lack of user input. “How agile will help in improving this situation?” This is a very common questions. 2nd most common question is “How do you document requirements in Agile?” Yes these are important questions but why not to start from basic? Why we are developing product? Who are our user? What behavior change we are expecting in our user? How to translate product vision in product features? Rest can be taken care by self-organizing Scrum team. Let team agrees about requirement capturing format and define purpose. Team may like to have user story or use case based on past experience so let’s focus on need, vision, impact, preparing features, identifying MVP and prioritization etc. This workshop will try to address all above questions by hands-on activities.

Learning objective of the workshop:-

  • Role of product owner, business analyst, developers and testers in Agile
  • Understanding Product Discovery and Impact Mapping to prepare product backlog
  • Product Backlog Refinement and user story writing skills
  • Splitting complex features in independent user story
  • User story mapping to identify priority
  • Dealing with non-functional requirement in agile
  • Identification of MVP and MMF
  • Importance of Acceptance criteria and Specification by Examples
  • What to write in definition of ready (DOR)
  • What is definition of DONE (DoD) and how it prevents from technical debt
  • Effective product backlog management bring transparency
  • Scrum Framework in nutshell

Learning Activities – Hands-on activities (60-70%) and discussion on mentioned topics (30-40%). Hands-on activities includes writing specification, writing examples and some group creativity activities.

Target Audience – Agile team members including product owner, business analyst, developers and testers.

Detailed Agenda for workshop:

Workshop will be delivered in 6 iterations with possible agenda as below:

Product Envisioning Workshop

  • Why do we need product vision?
  • How to develop Product Vision?
  • Developing a Product Video?
  • Product vision techniques such as Elevator Pitch
  • Review examples of good Product Vision.

Product Chartering Workshop

  • How to identify all the users of the Product?
  • Identify the user activities that Product will support.
  • Identify the product features that help the end users to perform the activities
  • Develop impact stories for the Product.
  • Learn to develop Product Canvas

User Research Workshop

  • Learn why User Research is important and how it pays off
  • Learn different ways of conducting User Research and apply on class project
  • Observe users at their native place
  • Conduct interviews and surveys
  • Lean Startup approach
  • Learn and Develop User Personas for the class Project.

Impact Mapping Workshop

  • Discovering product feature by Impact Mapping
  • Writing product vison using product vision canvas
  • Identifying Actors and Impact
  • Preparing product Features

User story workshop

  • Slicing features in independent user story by INVEST
  • Arranging user story
  • Prioritizing user story by Kano model
  • Identifying MVP
  • Ensuring stories are ready for development by identifying required artifacts

Product Backlog Management

  • Who prepare product backlog
  • How to make product backlog transparent
  • What is DEEP product backlog
  • Responsibility of Product Owner in maintaining product backlog
  • What business analyst do or how they support product owner

Specification by Examples Workshop

  • Challenges in Collaboration between Business and Development Team
  • How to write better Specification
  • Why Examples needed for specification
  • Writing Scenarios and Examples in Gherkin

Agile Estimation Workshop

  • Why estimating size and deriving duration is the key behind accurate estimates.
  • How to choose between using story points and ideal days for planning
  • Why you need to make sure you’re answering the right question
  • How story point estimates can be used even if you don’t know all the information
  • When you should defer estimating till you have the information you need.
  • Whether you should use story points to estimate in terms of the time or complexity of a task

Scrum Framework and Agile Requirement

  • Why to use Scrum to develop complex product
  • What are the essential elements of Scrum
  • Accountability, responsibility and skills for Product Owner, Scrum Master and Development Team
  • What they do during Scrum Events – Daily Scrum, Sprint Planning, Sprint Review and Sprint Retrospective and Backlog Refinement
  • Who writes and own definition of DONE (DoD)
  • How to write good DoD
  • When to update DoD and how to update
  • Who define Definition of Ready (DoR) and what it contains?
  • When to prepare and why to prepare DoR
  • How DoR is different than DoD
  • What is Technical Debt and how to prevent it
  • What’s the difference between DoD and Acceptance Criteria