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?
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
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
Feature model / Feature tree
Understand and document system context
Identify requirements sources
Identify and prioritize stakeholders
Decide on Agile requirements management tools
Steps of elicitation
Common challenges in elicitation
Impact of communication on requirements
Understanding transformational effects
Business rules catalog
Implicit requirements analysis
State chart diagram
Determine suitable elicitation techniques
Prepare for eliciting requirements
Document elicitation results
Confirm elicitation results
Requirements life cycle
Significance of requirements conflicts
Manage requirements conflicts
TECHNIQUES FOR REQUIREMENTS MANAGEMENT
Inspection, aka formal / technical review
Post it notes
Walk-through, aka lightweight review
Agile requirements effort estimation
Agile requirements communication
Agile requirements management process
Manage requirements traceability
Maintain requirements for re-use
Establish project glossary
Prepare initial requirements package
Prepare final requirements package
Validate design models
Define transition requirements
Identify workarounds and future improvements
24+ years of professional experience inbusiness analysis, software product development, business analysis, ERP implementations, software processes , strategic Change Management Consultancy.
Author of 12 books on Business Analysis and Requirements Engineering
Latest posts by LN (see all)
- 100 common risks for business analysis - June 20, 2017
- Stakeholder groups vs. UN Security Council – What’s the commonalities? - June 5, 2017
- Certifications are truly useless. Only if…. - May 29, 2017