Business Analysis (BA)
Things to discuss?
— Why
BA Matters?
— Who
defines BA standards?
— What
is Business Analysis?
— Essential
Skills of Business Analyst
— Knowledge
Areas and Relevant Work Experience
— Techniques
— Scrum
– An alternative to Waterfall Model
— Scrum
Roles
— JIRA
Why Business Analysis
Matters?
— Who
defines BA standards?
— IIBA® stands for International Institute of
Business Analysis
— Founded
in Toronto, Canada in October of 2003
— Creates
and develops awareness and recognition of the value and contribution of the
Business Analyst
— Defines
the Business Analysis Body of Knowledge® (BABOK®)
— Publicly
recognizes and certifies qualified practitioners through an internationally
acknowledged certification program
— Provides
a forum for knowledge sharing and contribution to the business analysis
profession
What is Business
Analysis?
— Business
Analysis is the practice of enabling change in an organizational context, by
defining needs and recommending solutions that deliver value to stakeholders.
— The
set of tasks and techniques that are used to perform business analysis are
defined in A Guide to the Business Analysis Body of Knowledge® (BABOK®Guide).
Essential Skills of
Business Analyst
— Analytical
Aptitude
— Skilled
in Critical Thinking
— Possesses
High Degree of Business Acumen
— Advanced
in listening, communicating and facilitating
— Adept
in requirements elicitation
— Able
to analyze complex information from varying sources
— Technical
Proficiency
— Knowledge
Areas & Relevant Work Experience
Certified Business
Analysis Professional™ (CBAP®)
— Minimum
7500 hours of BA work experience aligned with A Guide to the Business Analysis
Book of Knowledge® (BABOK® Guide) in the last 10 years
— Minimum
900 hours in four of the six knowledge areas
— Minimum
21 hours of Professional Development in the past four years
— Two
references from a career manager, client or Certified Business Analysis
Professional (CBAP®) recipient
— Signed
Code of Conduct
Certification of
Competency in Business Analysis™ (CCBA®)
— Minimum
3500 hours of BA work experience aligned with A Guide to the Business Analysis
Book of Knowledge® (BABOK® Guide) in the last 7 years
— Minimum
900 hours in two of the six knowledge areas
— Minimum
21 hours of Professional Development in the past four years
— Two
references from a career manager, client or Certified Business Analysis
Professional (CBAP®) recipient
— Signed
Code of Conduct
Business Analysis
Techniques
— Scenarios
& Use Cases
— Benchmarking
— Client
Interview/ Survey/ Questionnaire
— User
Interface Wireframes
— Prototyping
— Non-functional
Requirements Analysis
Scrum
— Scrum
is a management framework for incremental product development using one or more
cross-functional, self-organizing teams
Scrum – An alternative
to Waterfall Model
·
Scrum’s incremental, iterative approach trades
the traditional phases of "waterfall" development for the ability to
develop a subset of high-value features first, incorporating feedback sooner.
·
The greatest potential benefit of Scrum is for
complex work involving knowledge creation and collaboration, such as new
product development
Scrum Roles
— Product
Owner
1. Single
person responsible for maximizing the return on investment (ROI) of the
development effort.
2. Responsible
for product vision.
3. Constantly
re-prioritizes the Product Backlog, adjusting any long-term expectations such
as release plans.
4. Final
arbiter of requirements questions.
5. Accepts
or rejects each product increment.
6. Decides
whether to ship.
7. Decides
whether to continue development.
8. Considers
stakeholder interests.
9. May
contribute as a team member.
— Scrum
Development Team
1. Cross-functional
(e.g., includes members with testing skills, and often others not traditionally
called developers: business analysts, domain experts, etc.).
2. Self-organizing
/ self-managing, without externally assigned roles.
3. Negotiates
commitments with the Product Owner, one Sprint at a time.
4. Has
autonomy regarding how to reach commitments.
5. Intensely
collaborative.
6. Most
successful when located in one team room, particularly for the first few
Sprints.
7. Most
successful with long-term, full-time membership. Scrum moves work to a flexible
learning team and avoids moving people or splitting them between teams.
8. 7
± 2 members.
— Scrum
Master
1. Facilitates
the Scrum process.
2. Helps
resolve impediments.
3. Creates
an environment conducive to team self-organization.
4. Captures
empirical data to adjust forecasts.
5. Shields
the team from external interference and distractions to keep it in group flow
(a.k.a. the zone).
6. Enforces
timeboxes.
7. Keeps
Scrum artifacts visible.
8. Promotes
improved engineering practices.
9. Has
no management authority over the team
JIRA
— JIRA
Sprint
— JIRA
– Team Scrum Board
Further Reading
No comments:
Post a Comment