Business Analyst RSS

Business Analyst Jobs
Business Analysts

Business Analyst Jobs

"Business Analyst jobs are a prize for business and technical graduates."

People land Business Analyst jobs in many ways. Junior Business Analyst jobs are available to people who graduate from college and have very little or no prior experience. These roles as entry level management jobs, entails them being an individual contributor and requires working under supervision. In other instances, people work in an industry and gain an understanding of the business before taking up a Business Analyst job role. Such people take up middle management level positions and may play a supervisory role.

Skills Required

Business Analyst Jobs

Business Analysts perform a wide variety of roles depending on the organization they work for and the title that they hold. The job description would vary and the skills required would also differ accordingly. Entry level Business Analyst jobs would require strong analytical thinking capabilities, collaboration and communication skills. These are foundational skills that would be required throughout the career in business analysis. At the middle and senior levels, there is an increasing emphasis on leadership, business knowledge and multi-tasking skills.

Business Analyst Job Description

Business Analyst Jobs are plentiful if you have the right credentials.

Given the varying nature of the Business Analyst job, there is no standard job description for a Business Analyst. Primarily, BAs act as a liaison between the technology and business organizations and help implement solutions that meet stakeholders' requirements.

Business Analyst Career

Business analysts can pursue a career within the area of business analysis or seek a lateral move. Organizations that offer a structured career path for BAs often have training programs that impart new skills (These may be in the form of usage of new tools, conflict management, workshop facilitation and effective presentation skills). This would ensure that people are geared to take up higher responsibility in their jobs. At middle and senior levels (people with about ten years of experience), Business analysts would be deployed on complex and critical projects that would run for longer duration, require significant stakeholder management skills and the ability to present at senior executive levels. Over the long term, these roles can lead to taking up leadership positions at a division or Business Unit level within an organization.

Career moves outside business analysis include taking up roles as a Project Manager, Product Manager or a Product Specialist. BAs with a good grasp of technology can take up the role of a Solution Architect. Solution Architect roles are in high demand given the requirement for professionals with sound technical and business skills. In the long term, some business analysts take up independent consulting jobs that may prove to be more remunerative than full time employment.


Business analysts should be aware of career options within the area of business analysis and lateral career options. They should equip themselves with the appropriate skills to make career progress. Business analysts must be able to chart the course of their careers than wait for things to happen. Business Analyst jobs offer a variety of experience that can help professionals make a career in other areas like consulting, product management, project management and general management.

© 2015 Stellar Force

Business Analyst Community & Resources | Modern Analyst
RSS feeds for Business Analyst Community & Resources | Modern Analyst

An Overview of the Underlying Competency of Behavioral Characteristics
by Transform VA
19 Jun 2017 at 6:13am
While BABOK and other sources include Behavioral Characteristics as an essential underlying competency for business analysts, many analysts may have only a vague idea of how it applies to their personal work environment, or even exactly what behavioral characteristics are, so let’s define those first.... The term behavioral characteristics simply refers to an analyst’s workplace ethics and character.    Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ? Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English  
Documenting Requirements for Outsourced Projects
by Transform VA
11 Jun 2017 at 8:30am
The purpose of this brief article is to explain the connection between documenting requirements and contract type. Recently I consulted with a firm eliciting requirements for a new product. In this case, an internal business analyst team was documenting the product requirements by consulting with appropriate stakeholders. The follow-on project intent was to outsource the work to develop the product in the form of a contract.
Crossing the Imaginary Line - Design Thinking in Business Analysis
by michael_r_roy01
4 Jun 2017 at 10:50am
I take the approach that as Business Analysts, the line between requirements and design is an imaginary line. We need to be pragmatic (abandon purist thinking) and not be afraid to wear the design cloak, to adopt design thinking.    So how do we incorporate design thinking in Business Analysis in a value-add way? Take the following thoughts into consideration when working on your next project that involves building or significantly updating a customer-centric application. Author: Michael Roy, Business Analysis Professional / Requirements Leader Michael is a solutions-focused Business Analysis professional with extensive experience leading change initiatives at a tactical and strategic level.  
What Are True Business Rules?
by Transform VA
29 May 2017 at 9:00pm
Don't underestimate how pervasively across your organization business rule is misunderstood. What is a true business rule? A true business rule is simply a criterion used in daily business operations to shape behavior or make decisions. The things that IT implements under today’s software platforms are not true business rules; rather, they are mostly encoded representations of business rules.
?But I Already Know What I Want!?: Helping Our Stakeholders Think Beyond One ...
by Transform VA
21 May 2017 at 4:43pm
I bet everyone has, at least once in their career, heard the expression: “We don’t need any up-front analysis: I already know what I want!” Often these words are followed by a description of a specific type of solution, often an IT system, and often a specific vendor name. Perhaps our executive stakeholder has decided they need to migrate onto the newest platform, the organization needs a new ‘mobile app’, or we need to ‘move all of our data into the cloud’. I can imagine some people will be holding their heads in their hands as they read this paragraph…
iRise: Why Prototyping is Essential In the Post-Information Age
by adrian
13 May 2017 at 11:17am
iRise gives Business Analysts the tools they need to communicate clearly with both the business and its stakeholders.  They use working previews that can be virtually indistinguishable from the final product.  When business analysts uses iRise to elicit and document requirements: the business analyst becomes a powerful weapon to get to the right answer, ...
Deep Dive Models in Agile Series: State Models
by Transform VA
7 May 2017 at 8:00pm
State Models include two RML Data models (State Tables and State Diagrams) that show the transition of an object through various states or statuses, including which transitions are valid and what triggers an object to transition state. A state is a short-form description of a stage in a data object’s life that influences the behavior of the system. These two models are covered together in this paper because they generally show the same information, just in different ways. These models are great for any object which has state about which there might be business rules, like workflow processes!
Using Decisions to Prioritize and Identify Requirements for Business Analytic...
by Transform VA
29 Apr 2017 at 11:48pm
The end products of requirements development for a business analytics project will be similar to those for any other project—a set of business, user, functional, and nonfunctional requirements. Process flows, use cases, and user stories can reveal that someone needs to generate analytics results, and performance requirements describe how quickly they need results, but none of these uncovers the complex knowledge required to implement the system... An effective elicitation strategy for business analysts (BAs) is to drive requirements specification based on the decisions that stakeholders need to make to achieve their business objectives.
Aligning Multiple Definitions: Guidelines for Building World-Class Business G...
by Transform VA
23 Apr 2017 at 8:40am
A good business definition is not only good because it is clear and concise, but because it holds a clear, exclusive position within its full set of peers – i.e., the glossary for your business vocabulary. This discussion outlines five basic guidelines for ensuring the quality of a glossary holistically, focusing on avoiding naming anomalies, subtle redundancies, and avoiding circularities. Find out how you can become world-class at communicating the meaning of your business concepts. Part of the secret is a clear focus on seed concepts.
Beyond Better Requirements - Selling Business Analysis in Business Terms
by michael_r_roy01
16 Apr 2017 at 11:35pm
We hit a challenge however when we attempt to promote the value of Business Analysis to IT Management or the Business...  The reality is that simply promoting “better requirements” does not sell our value-add in terms that management from an IT or Business perspective understands... So how do we do this? Let me share five lessons learned based on my experience as a senior requirements management consultant. 
Fast Track Product Management
by Transform VA
10 Apr 2017 at 4:50am
The paradigm shift towards agile and lean product development has brought collaboration between large cross-functional team in the spotlight. The existing literature is already mature explaining clearly how benefits can be reaped fast by executing a clean transition to agile delivery by enhancing the performance of the new cross-functional teams. However, in parallel, the time spent in endless meetings by product owners, business analysts, engineers, product managers and many others involved in the product creation, has grown exponentially. This leaves key product people with little or no time to do the critical activities they are employed for.
You Have Got to Be Lazy to Be an Effective Business Analyst
by adrian
2 Apr 2017 at 5:27pm
You see, I am a business analyst (BA), and more precisely the lesser-spotted, lazy beta alpha, the evolutionary pinnacle of my profession, at the tip of the BA spear. While the work of throwing or stabbing with the spear requires an effort by the arm that wields it, I prefer the sharp bit to do the work for me. In other words, doing as little as possible apart from…well, being sharp. While the sharp bit does all the work I am able to still the get the glory and recognition of a job well done. While the spear tossers return with painful shoulders, weary and, hopefully sometimes with a degree of success.
5 Tips for Success with Packaged Solution Requirements
by michael_r_roy01
29 Mar 2017 at 1:22pm
A common challenge of enterprise Business Analysts is the discovery, understanding, and description of requirements in the context of implementing packaged solutions. Management assigns us to projects with a predefined solution, and we struggle to figure our role when there seems to be no significant build activity. What are we supposed to do in this situation when there seems to be no need to produce standard requirement deliverables?   Put a typical Business Analyst in this environment and do not be surprised to hear the phrase “I’m not sure of my role.” Why do packaged solution projects cause discomfort?
Capturing the Essence of Concepts: Guidelines for Building World-Class Busin...
by Transform VA
26 Mar 2017 at 8:20pm
There are various schools of thought about how to define terms, some arising from professional terminologists and academia. But those approaches are often relatively arcane and not well-suited to everyday business practice. Definitions with subtle IT or ‘data’ bias are an anathema to effective communication with business partners. Good business definitions are oriented to what words mean when used by real business people talking directly about real business things.
The State of I.T. in Business
by timbryce
23 Mar 2017 at 1:32pm
Watching the speed by which Information Technology (I.T.) has changed over the last forty years has been amazing. Hardly a day goes by without some new twist or invention. In particular, my interest is in how I.T. can be applied to support the systems needed to operate a business, such as for manufacturing, inventory, order processing, customer service, accounting, human resources, and much more. I have seen a lot during the last four decades, perhaps too much.

Newsfeed display by CaRP
Share this page

Follow Business Analysts