eleks.com

Business Analyst Role in the Project.by Ruslan Tsopa, Business analyst

Agenda• Who is Business Analyst• What are the

requirements• User stories• Use cases• Examples

How does the project begin?

How does the project begin?

Question

Who is involved in development process?

How client sees…

How developers see…

What happens if mix All?

How project fails looks like

Projects success statistics

Who is Business Analyst?

Project fails by activities

Working in Team

BA Architect

UX

No busines

svalue

No softwareSOLUTION:

- business value- strong

architecture- awesome design

No usabilit

y

How Agile Requirements looks like?1. Preliminary elicitation with customer2. Review high level requirements with

Architect and UX3. Clarifying details with customer4. Specification requirements5. Grooming session with Team6. Planning iteration, break down stories by

tasks and tasks estimation

What are requirements?Functional requirements - describe the capabilities that a solution must have in terms of the behaviour and information that the solution will manage

Non Functional Requirements - do not relate directly to the behaviour of functionality of the solution, but rather describe conditions under which a solution must remain effective or qualities that a solution must have

Business rules - statements of goals, objectives, and outcomes that describe why a change has been initiated. They can apply to the whole of an enterprise, a business area, or a specific initiative

How to represent requirements?Requirements representation

• User stories• Use cases• Documents• Mockups• Prototypes• States flow / flow charts/ activity diagram

User storyA user story - simple description of a feature told from the perspective of the person who desires the new capability. It contains enough information so that the developers can produce a reasonable estimate of the effort to implement it. Why all like user stories?:• Small• User/Customer centered• Use end user/customer language• Easy to read /understand bridges the gap between technical and

business• Focus on Delivering Value• Useful for Planning• Easily prioritizable and reprioritizable

User storyAs a <User> I want to <Do something> so that <Expected outcome> Who? What? Why?

Acceptance criteriaDefines conditions for “satisfaction”

 Definition of done

Defines conditions for “readiness”

What is a User story

How good your User story is?

Use caseUse case is a list of steps, typically defining interactions between a role (known as an "actor") and a system, to achieve a goal. The actor can be a human, an external system, or time. Elements of a Use Case Depending on how in depth and complex you want or need to get, use cases describe a combination of the following elements:• actor • precondition/triggers• main scenario• alternative paths/exceptions• post condition

Use caseMore about elementsActor – anyone or anything that performs a behavior (who is using the system) • Class of Users (Role)• External SystemsPreconditions – what must be true or happen before use case to be initiatedMain scenarios [Basic Flow] – use case in which nothing goes wrong.• Main Flow is the sequence of steps that helps the Actor achieve his or her

goal. • Main Flow is the most “typical/common” (usually also simple) success

scenario. • Main Flow always ends with success. Alternative paths [Alternative Flow] – these paths are a variation on the main theme. These exceptions are what happen when things go wrong at the system level.Post condition – what is the state of system or what is expecting result after success 

How Use Cases describe the system behavior

Use case exampleDescription: Pay by credit cardActor – BuyerPreconditions- User is authorized in the system- Amount in cart is more than 0Main scenarios 1. Enter credit card number2. Enter credit card expiration date3. Enter CVV number4. Proceed paymentAlternative pathsA1. Continue shoppingA2. Logout ExceptionE1. There is not enough money in the credit card accountPost conditionPayment is done

User stories & Use case

For ReadingKarl Wiegers – SoftwareRequirements (3rd Edition)

Mike Cohn - User Stories Applied For Agile Software

Inspired by Technology.Driven by Value.

Questions?

Skype: ruslan.tsopaFacebook: tsopa.ruslan