Adaptive completes Agile BA workshop for a leading bank in Singapore

It gives us great pleasure in announcing that Adaptive completed a new course, Agile BA for  a leading bank in Singapore.

 

Agile is being increasingly used as a preferred software development methodology. The topics covered during the workshop were as follows.

 

WHAT AND WHY OF AGILE BA

 

Who are Agile BAs anyway?

 

But then Scrum DOES NOT have a role for business analysis?

 

What is Business Analysis?

 

What is Agile Business Analysis?

 

BTW, what are requirements?

 

Are there different types of requirements?

 

Why requirements are crucial to project success?

 

UNDERSTANDING AGILE PROCESS

 

Why traditional waterfall failed?

 

How can one fix issues with traditional waterfall failed?

 

Agile manifesto

 

Principles behind the Agile Manifesto

 

Now what’s Scrum?

 

AGILE BA RESPONSIBILITIES AND SKILLS

 

Expectations from an Agile BA

 

KEY SKILLS FOR AN AGILE BA

 

Communication – Oral and written

 

Stakeholder management

 

Knowledge of business and specific industry

 

Knowledge of the organization

 

Knowledge of the solution

 

Knowledge of Agile BA process

 

Knowledge of elicitation and modeling techniques

 

Knowledge of office tools and modeling tools

 

PLAN BUSINESS ANALYSIS

 

TECHNIQUES FOR PLANNING

 

Acceptance criteria

 

Feature model / Feature tree

 

Release planning

 

Sprint planning

 

Stakeholder list

 

Time boxing

 

ACTIVITIES

 

Understand and document system context

 

Identify requirements sources

 

Identify and prioritize stakeholders

 

Define constraints

 

Decide on Agile requirements management tools

 

Plan releases

 

Plan sprints

 

ELICIT REQUIREMENTS

 

Steps of elicitation

 

Common challenges in elicitation

 

Impact of communication on requirements

 

Understanding transformational effects

 

Modeling requirements

 

ELICITATION TECHNIQUES

 

Activity diagrams

 

Business rules catalog

 

Document analysis

 

Implicit requirements analysis

 

Interface analysis

 

Interviews

 

Matrix Model

 

Non-Functional requirements

 

Observation

 

Persona

 

Problem tracking

 

Process modeling

 

Prototyping

 

Requirements workshops

 

State chart diagram

 

User stories

 

ELICITATION ACTIVITIES

 

Determine suitable elicitation techniques

 

Prepare for eliciting requirements

 

Elicit requirements

 

Document elicitation results

 

Confirm elicitation results

 

MANAGING REQUIREMENTS

 

Requirements life cycle

 

Significance of requirements conflicts

 

Manage requirements conflicts

 

TECHNIQUES FOR REQUIREMENTS MANAGEMENT

 

Impact analysis

 

Inspection, aka formal / technical review

 

MoSCoW

 

Post it notes

 

Sprint retrospective

 

Sprint review

 

Structured walkthrough

 

Walk-through, aka lightweight review

 

Workarounds

 

Agile requirements effort estimation

 

Agile requirements communication

 

ACTIVITIES

 

Agile requirements management process

 

Manage requirements traceability

 

Maintain requirements for re-use

 

DOCUMENT REQUIREMENTS

 

ACTIVITIES

 

Establish project glossary

 

Organize requirements

 

Prepare initial requirements package

 

Prepare final requirements package

 

VALIDATE SOLUTION

 

ACTIVITIES

 

Validate design models

 

Define transition requirements

 

Validate solution

 

Identify workarounds and future improvements

 

 

Leave a Reply

Your email address will not be published. Required fields are marked *

Bitnami