Flexible Careers Are Here, Start Yours Now

Non-Traditional Careers for Business Analysts - Part 2
Non-Traditional Careers for Business Analysts – Part 2

Now is a good time to “consider a more flexible career” because all the changes taking place in the marketplace are fundamentally transforming the way we work as well as the opportunities available to us!

This is great news for anyone interested in a more flexible career or employment including options to work from home, consult for companies or retire or travel while earning an income!

Writing Better Requirements: Why Projects Fail

Write Better Requirements
Write Better Requirements

Why Do We Need Better Requirements?

The following article is a frank, open and surprising discourse on why we need better requirements.

According to Standish or Gartner reports and other case studies, nearly “two-thirds of all IT projects fail” because of poor requirements and other causes.

Why Do Projects Fail?

Consider that a project fails when it overruns the budgeted allocation of resources, time or money or fails to deliver the intended business requirements or value.

Some teams are so deep into this, that throwing more money, people or extending the shipping date is their default solution to scope creep, budget overruns or project failure!

How Important Is Domain Knowledge For A Business Analyst?

The Domain Business Analyst Career Path
The Domain Business Analyst Career Path
Is a business analyst with domain knowledge more valuable than a business analyst without domain knowledge?

By looking at how business analyst job descriptions are written, you may be tempted to say yes!

Business Analyst job descriptions are written as if there is a distinction between IT oriented business analysts with skills in UML, Use Cases, Requirements Elicitation, Requirements Modeling and domain oriented business analysts with knowledge in specific domains like sales, marketing, customer relationship management, insurance, finance!

The Most Valuable Business Analysis Skills Are ??

What Are The Most Valuable Business Analyst Skills?
What Are The Most Valuable Business Analyst Skills?

One of the toughest challenges facing business analysts today is building the domain experience required for business analyst jobs.

Acquiring business analyst domain experience from scratch is hard because you need to get a job before you can build domain expertise … yet no-one will give you a job without that required domain experience!

This post however discusses how to get around the business analyst domain experience required for business analysis jobs.

How To Become A Healthcare Business Analyst

healthcare business analyst career path
healthcare business analyst career path

This question was posted by a Healthcare Business Analyst looking for work!

If you have a Burning Question or a Challenge that you need help with, be sure to ask your question as a comment on this page and I will answer it fully just as I am answering the question below!

If you find this article helpful then share it with your friends using the “Share This Post” Link.

You provide valuable information or advice to others each time you use the Share This Post Link.

Is the Job Market Good Or Bad For Business Analysts?

Ask IT Career Coach
Ask IT Career Coach

This question was posted by a Business Analyst in Milton Keynes, United Kingdom.

If you have a Burning Question or a Challenge that you need help with, be sure to ask your question as a comment on this page and I will answer it fully just as I am answering the question below!

Please, send this post to your friends using the “Tell a Friend” Button button below. You earn points or cash each time you refer an article to your friends using the Tell a Friend Button.

Here is the Question:

Hi,

Bonus Use Cases Training In The Business Analyst Book

Top Paying Skills in High Demand
Top Paying Skills in High Demand

Use Cases skills are in-demand for documenting or communicating the functional requirements of a system

Use Cases skills are employed in product design roles, software development or architecture roles and are among the most sought-after skills for business analyst jobs

Why Use Cases Training for Business Analysts?

Here are some of benefits of Use Case training for business analysts:

  1. Use Cases are effective for documenting the business processes, requirements (business or system), features and functionality of a system. So Use Cases skills are needed at the problem analysis or requirements gathering phase, software design or development phase or testing phase

Good Note Taking Means More Efficient Requirements Elicitation

The discussion of requirements elicitation tools and techniques rarely seems to include a discussion of the best way to document your findings.

Lifehack has written an insightful post on How to Take Notes like Thomas Edison.

Thomas Edison’s diary contains five million pages and is maintained as an important part of the United States historical record. Two of the criteria for Edison’s record system are crucial to the Business Analyst:

Item #3 -The Records must be Rearward-looking. Basically, you should always keep requirements traceability in mind as you take notes.

How to Elicit, Capture or Gather Requirements Effectively

Effective Requirements Elicitation Techniques
Effective Requirements Elicitation Techniques

What is Requirements Elicitation?

Requirements elicitation is the process of identifying the sources of requirements for a new system and obtaining those requirements from those sources.

Potential sources of requirements include users, documents, regulators and even legacy software code.

Requirements elicitation is a crucial part of the Requirements Gathering, Documentation and Analysis Process.

It is a critical business activity that requires the focus of a skilled business analyst.

Regardless of the elicitation techniques you choose or how you implement those techniques, you need to do whatever it takes to understand the real needs of your customers.

Business Analysts Don’t Really “Gather” Requirements

Gathering Requirements
Gathering Requirements

It is common knowledge that the biggest reason for IT project failure is poor requirements. If the requirements that the developers are working from are wrong, incomplete or otherwise inadequate, that project is doomed to join the 70% of IT projects that fail every year.

So why not simply gather good (SMART) requirements? Ask any business analyst and they will tell you that the biggest problem they face is getting users to tell them what they really want out of a new system or process. Why? The reasons are varied. Sometimes it appears that users simply won’t communicate what they really want. Sometimes it appears that the business analyst is asking all the wrong questions. Sometimes it appears that the users change their minds all the time.