Showing posts with label requirements. Show all posts
Showing posts with label requirements. Show all posts

Saturday, August 2, 2014

How Business Analysis Services Add Business Value

Just as the Agile approach to software development contains a few methodologies, Business Analysis contains a few business services to drive better business outcomes. Notice, I did not use the term “business solutions” as Business Analysis is more than just business solutions, it contains a few services outside of information technology projects that deliver business solutions. Business Analysis is about defining and delivering the outcomes that are best for the organization; strategically, tactically and operationally.


It never ceases to amaze me how many people don’t feel that they are a Business Analyst because their job title is not Business Analyst, or some derivative thereof. There are many job titles that perform business analysis activities, and this is increased by those companies that get creative with their job titles. There are job titles in and outside of IT project work that perform business analysis activities. Remember, whether you are a business analyst is determined by the tasks you perform for the company, not by your job title.

Read more about the many business services under the umbrella of business analysis…Read the whole article

Tuesday, January 21, 2014

The Top 8 Mistakes in Requirements Elicitation

Take a look at my list of the top 8 traps that Business Analysts fall into while eliciting requirements; business, stakeholder or functional, from business stakeholders.  I also give some tips to avoid these mistakes.  So take a look, see if you agree.  Perhaps you have some to add, or would take one or more away.  Give it a read and join the conversation... The Top 8 Mistakes in Requirements Elicitation