Typical Day of a Business Analyst

Project Sizing for the business team.

Primary liason for the technical group and various business groups that our group
implements projects for.

Use expert judgement, historical analogy, and bottoms up approach for software sizing
estimation.

Conduct meetings with the technical leads of the various technical groups that are involved
in each project request.

Understand the scope of the change and what it will take to implement the change.
Then present finding in a template form to the business team so they can understand the
impact to the various groups.

I collect status of development progress and conduct weekly status meetings.

For all projects being undertaken by our group, Im responsible for:
1) Conducting conference calls
2) Report development status to business team
3) Send out official project status emails to the business group
4) TRIAGE: Im responsible for allocation of bugs found in our product to the
engineers, by internal users like QA, and business people. Understand which
component the bug is in, who the developer is for that component, the severity of
the bug, the release that this bug would be fixed under.
5) Requirements gathering:
a) I participate in requirements gathering with business team and other technical
teams.
b) We collectively brainstorm, interview each other, interview users, figure out
impact to the business processes, and impact to the systems.
c) My role is to mostly act like a system analyst to answer business questions on
various enhancements
6) Forecasting for the group
a) I look at all the projects in pipeline, classify as infrastructure or small
enhancements, and then divide up our resources of team into various modules
of the project.
7) Acting as a SME (subject matter expert). (Based on domain, say health care, or
credit card systems, etc.)
May also provide directions on technical architecture of our platform
8) Maintaining release calendar for the group. There are various products and
domains that our team maintains. I am responsible for being the gatekeeper of all
the releases that we do. And all combed at the growing needs of the business and
well as the bug features we do along the way.
9) I am responsible for making sure that we are releasing the features on the expected
day. I keep a close eye on the configuration management reports, and decide which
build number to release and check out to QA, user acceptance testing, and
production environments.