PROJECT RELATED COMPETENCIES

Analysis and Solution Definition

o Quickly understands the business issues and data challenges of client's organization and industry.
o Identifies client organization's strengths and weaknesses and suggests areas of improvement.
o Reviews and edits requirements, specifications, business processes and recommendations related to
proposed solution.
o Develops functional specifications and system design specifications for client engagements.

Technical Recommendation and Testing

o Leads testing efforts.

o Ensures issues are identified, tracked, reported on and resolved in a timely manner.
o Works with client personnel to identify required changes.
o Communicates needed changes to development team.

Project Execution

o Assists in enforcement of project deadlines and schedules.

o Takes input from supervisor and appropriately and accurately applies comments/feedback.
o Communicates and applies project standards.
o Manages resources in accordance with project schedule.
o Consistently delivers high-quality services to our clients.
o Understands the components of running a fiscally successful project.
CAREER PATH CORE COMPETENCIES
Communication

o Assists in the facilitation of team and client meetings.

o Delivers informative, well-organized presentations.
o Understands how to communicate difficult/sensitive information tactfully.

Technical Understanding

o Possesses understanding in the areas of application programming, database and system design.
o Understands Internet, Intranet, Extranet and client/server architectures.
o Understands how legacy and web-based systems interface with each other.

Problem Solving

o Identifies critical issues with ease.

o Exhibits confidence and an extensive knowledge of emerging industry practices when solving business
problems.
o Pushes creative thinking beyond the boundaries of existing industry practices and client mindsets.
PROFESSIONAL QUALITIES
Leadership
o Generates enthusiasm among team members.
o Proactively seeks opportunities to serve in leadership roles.
o Challenges others to develop as leaders while serving as a role model.
o Manages the process of innovative change.

Teamwork

o Facilitates effective team interaction.

o Acknowledges and appreciates each team member's contributions.

Client Management

o Develops relationships with client personnel that foster client ties.

o Communicates effectively with clients to identify needs and evaluate alternative business solutions with
project management.
o Continually seeks opportunities to increase customer satisfaction and deepen client relationships.
o Manages client expectations effectively.
ORGANIZATIONAL RESPONSIBILITIES
Innovator Development

o Conducts effective progress evaluations in a timely manner.

o Mentors those with less experience through informal channels.
o Seeks and participates in development opportunities above and beyond training required by us.
o Trains other innovators through both formal and informal training programs.

Internal Operations

o Suggests areas for improvement in internal processes along with possible solutions.
o Leads internal teams/task forces.
So, what exactly is a Business Analyst? What is the role of the Analyst in the software development lifecycle? If you
don’t want to be completely confused, don’t bother trying to get a conclusive definition by just “Googling” it. There are
dozens of variations on the BA role depending on the company, and on the software engineering methodology used.

You’ll hear of Systems Analysts, Requirements Engineers/Analysts and a host of other related titles. These, again
depending on the company, may be the same thing as a BA, somewhat similar, or completely different.

Based on my experience, I like the Business Analyst job description provided over at Mike Schaffner’s blog. It seems
to hit all the main points as well as some of the more generic desired attributes in an IT professional.

I like that Schaffner goes a bit further in pointing out specific attributes (I’ve highlighted them in blue text) that
distinguish the BA from a typical “good applications person.”

Here’s the list:

 Elicit requirements using interviews, document analysis, requirements workshops, surveys, site
visits, business process descriptions, use cases, scenarios, business analysis, task and workflow
analysis.
 Critically evaluate information gathered from multiple sources, reconcile conflicts, decompose high-
level information into details, abstract up from low-level information to a general understanding, and
distinguish user requests from the underlying true needs.
 Proactively communicate and collaborate with external and internal customers to analyze
information needs and functional requirements and deliver the following artifacts as needed:
(Functional requirements (Business Requirements Document), iii. Use Cases, GUI, Screen and
Interface designs)
 Utilize your experience in using enterprise-wide requirements definition and management systems
and methodologies required.
 Successfully engage in multiple initiatives simultaneously
 Work independently with users to define concepts and under direction of project managers
 Drive and challenge business units on their assumptions of how they will successfully execute their
plans
 Strong analytical and product management skills required, including a thorough understanding of
how to interpret customer business needs and translate them into application and operational
requirements.
 Excellent verbal and written communication skills and the ability to interact professionally with a
diverse group, executives, managers, and subject matter experts.
 Serves as the conduit between the customer community (internal and external customers) and the
software development team through which requirements flow.
 Develop requirements specifications according to standard templates, using natural language.
 Collaborate with developers and subject matter experts to establish the technical vision and
analyze tradeoffs between usability and performance needs.
 Be the liaison between the business units, technology teams and support teams.

Read more: http://practicalanalyst.com/2007/02/14/business-analyst-job-description/#ixzz0zhw1XQdE