Access

your
account
Case study for business analysts,
developers, PM, SM & PO
Business Objective

 Improve customer experience

 Reduce manual intervention
 Improved turn around time
 Reduced operation cost
 Initial analysis

High level business requirement

Project
Initiation

GAP Analysis
Business analysis

 Business requirement- Internet

Banking/Access(initiate online
transactions, access & update
personal information.)
Sprint 1 (Overview)

 Project planning
 Business analysis
 Team setup
 Technical setup

Along with user stories, product backlog and regular development activities.
Sprint 1 Details

 2 week sprint
 Daily stand up call for 15 mins
 Sprint planning
 Sprint review
 Sprint retrospective
Sprint 1 Day 1-PO

 Product Owner works with users and stakeholders and elicit requirement, this is the
creation of product backlog. This will happen every day in sprint 0 and throughout the rest
of the project across different sprints.
 Product will owner will work with develop team to estimate these user stories and based
on that put them in order and prioritize them.

 Let’s say, putting non-functional requirements related to region, license should be

delivered first so that team can work on coding and unit testing.
Sprint 1 Day 1-SM

 Scrum Master will organize Sprint planning meeting. Product owner share details about
user stories and answer questions on them. Development team reviews them, analyze their
capabilities (numbers, skills, technical infrastructure) and recommend user stories they will
deliver in next sprint. These user stories will become part of Sprint Backlog.

 Sprint 1 should be small, preferably 1-2 weeks and primarily for planning and sorting out
any management/technical issues. Few projects directly start from sprint 1 if they have
everything ready and they have been working on the product for some time now.
Sprint 1….

 Scrum Master organizes daily scrum call. Ask three questions;

1. What you did yesterday

2. What do you plan to do today?
3. Any obstruction or issues for today’s work.
 It’s a quick 15-30 mins call, preferably everybody stands because it has been seen that
people tend to spend more time if they get to sit and get comfortable.
Sprint 1….

 If you are starting with scrum, it’s better to also work on developing a guideline for daily
scrum/stand up, for example;

1. Turn off your mobile phones during call

2. Only 1 person will speak at 1 time
3. Wait for your turn
4. Don’t share ideas
5. Stay objective
Sprint 1…

 Sprint 1 Second Last Day

 Scrum Master will hold sprint review meeting where delivered functionality is
demonstrated.

 Along with other activities so far

Sprint 1…

 Sprint 1 Last Day

 Sprint retrospective meeting takes place where everybody shares their ideas and how
things can improve. Scrum master update burndown charts. Product owner add new user
stories to product backlog. These user stories are again estimated, prioritized and ordered.
 Scrum master will organize sprint planning meeting for upcoming sprint.
 And Scrum
continues for
forever-sprint by
sprint
Business Analyst/Product Owner

 Create requirements (waterfall) or epic & user stories in scrum.

 Refine requirements and user stories.
 Identify stakeholders
 Walk through requirements or user stories with them.
 Prioritize requirement or user stories.
 In scrum, if any new change is identified, it will be moved to some future sprint i.e. part of
future sprint backlog.
 Coordinate with PM/SM, development team and testers.
 Understand requirement

Break down it in smaller and simpler

requirements/user stories.

How to
approach a Identify any gaps and impacts.
project for
BA/PO
Identify risks, in-scope and out of scope items.
Questions

1. What is the purpose of this portal or

whatever change they are asking?
2. Who is going to use it?
3. How users are going to use this portal or
any other application your stakeholders are
asking you to build.
Answers

 Business objective
 User details like customers, vendors, agents, lawyers, doctors etc. you will use this
information to build user persona. Or you design team can build user persona at the time of
building prototypes. You will need to pass this information to them. this information will
tell you the requirements of the users. And when I say user, it could be external users like
mentioned earlier-customers, doctors, lawyers etc. Or internal customers like employees in
certain departments. You may build application an HR application where each employee
can see their details and perform certain functions like applying for leave etc. so you can
have internal or external employees. In this case, we are building a portal and it will be
used by customers.
 And response of third question will tell you what they are going to do with it. How they are
going to interact with the system.
How to approach a project for BA/PO

START WITH WHY AND THEN MOVE ON TO

WHAT HOW
 UI/UX (frontend) Backend Review current tools or
technologies they are using

Approach for
this project

Identify user stories for Then identify necessary

frontend functionality like fields,
validation, pop ups, etc.
Remember
iteration
 Demo with
gmail