Agile Business Analysis Requirements and Management Folio of Work

Agile Business Analysis
Requirements and Management Folio of
Work
Project: Name of project
Name of Client
Author: Name
S Number: Number
Workshop: Day, Time, Instructor

Table of Contents
1 Introduction..............................................................................1
1.1 Purpose of this Document.....................................................................1
1.2 Scope of this document.........................................................................1
1.3 Background...........................................................................................1
2 Business Goals........................................................................1
2.1 Agile Approach......................................................................................1
3 Stakeholders............................................................................2
3.1 Stakeholder Definition...........................................................................2
3.2 Stakeholder Communication.................................................................2
4 Product Vision.........................................................................2
5 Requirements.........................................................................26
Delivery and Review................................................................2

1 Introduction
1.1 Purpose of this Document
The document is a business analysis document which is prepared for the
purpose of providing an overview of the current state of the Sam Chat Bot
project and is associated with providing an agile solution for the purpose of
pursuing further developments in the system.
1.2 Scope of this document
This document would be entirely associated with discussing and covering the
different aspects of the project along with defining the important
characteristics of the project. The major aspects includes he business goals,
definition of the stakeholders, vision of the product by means of the agile
tools, the requirements of the products, review of the delivery and lastly the
project management approach.
1.3 Background
The main purpose of this document is discuss the project and the main
purpose of this project includes the expansion of the current demo Chat Bot
solution Sam. This Chat Bot was developed with an aim of providing a 24*7
service and assistance to the students as well as to the faculties and the
external users regarding an interactive system which can be utilized by eth
users for the purpose of finding out answers to different queries of advance
nature which might seem impossible to be conveyed in an easy way.
The current situation of the system is associated with providing assistance to
the users by means of answers which are severely limited during the off-hours
and the reason behind this is the unavailability of the facilities at night or
during weekends or on holidays. Implementation of a Chat Bot would be
associated with offering a unique along with an innovative solution for the
problem as well as a strong parsing capability and a large knowledge base.
Besides all this the chat bot would also be capable of providing answers to the
queries which are related to the accounts of the user and the technical issues
which arises along with providing information about the university.
The product which is to be delivered at the end of the project would be
consisting of an highly functional Chat Bot which would be accessible 24*7 by
the students as well as the faculties and the external users as well. This in
turn would be associated with alleviating the pressure upon the employees
who are working in the help desks or is associated with providing tech support
during the day shifts by acting as an alternative option for the users and the
would be associated with allowing the users in seeking help at different times
such as after the working hours or during holidays.
Page 1

2 Business Goals
The product which is to be delivered at the end of the project would be
associated with providing an online platform for the students as well as for the
faculties and for the external parties as well, which in turn would be used by
the users for the purpose of finding answers to the different queries that are
related to the services which are provided by the university. The chat bot
would also be associated with providing of various information such as the
information of the degree or the information related to the courses which are
available, information related to staffs along with a general technical support.
The innovation which has been demonstrated by this particular platform is
capable of helping in bolstering the interest of the activities of the university by
the external parties. This in turn is capable of leading to have a more as well
as large scholarship deals for the university which in turn provides more
availability of opportunities amongst the students at the time of getting their
degree or during more enrolment of the students.
2.1 Agile Approach
Which approach (or ‘flavour’) of Agile will you use in the project? Justify your
choice.
Agile development consists of several approaches and the major reason
behind is that they can be used very easily with the projectmanagementby
making use of the advantages and the disadvantages in accordance to the
requirements. The project would be conducted by making use of the agile
approach which is known as the scrum approach.
The reason lying behind choosing the Scrum approach is that it is associated
with allowing the product development in an incremental way by means of a
sequential stages of sprints. Each and every sprint is associated with
providing a routine update of the status of development and is associated with
affording the clients in having an opportunity to request certain alterations or
new features. Besides this the state of the product at the end of a sprint
should be at a potentially shippable state and should be necessarily be
associated with meeting all the tasks which have been assigned so as to to be
completed within that sprint.
The products of the work which are generally produced in the scrum approach
should necessarily be associated with including the project vision document,
the sprint backlog documents along any other documents which are related to
the software backend as well as a user manual related to how the product is
to be used. The vision document would be associated with including the
general information related to the project and the this would be primarily be
associated with including an preliminary plan related to development along
with a general list consisting of the product requirements.
A log of task is assigned to each sprint and the sprint should be necessarily
be capable of completing each of the task so as to remain in track. The
progress in the early stages of the sprint is associated with determining the
Page 2