Business Analyst Community & Resources | Modern Analyst

The Community Blog for Business Analysts

Requirements Management and Communication (BABOK KA)

NO Image:

Paul Crosby

8 Ways to Be a Badass Business Analyst Employee

Being a badass isn’t about intimidation or trying to be something you simply are not. It’s about knowing who you are and using your strengths to drive forward. So let’s look at a few of the ways to be a badass in business: 1. Passion for Your Craft Is a Powerful and Infectious Energy Showing passion for your work in ...

1 Responses

This entry was published on Sep 07, 2016 / Paul Crosby. Posted in Requirements Analysis (BABOK KA) , Requirements Management and Communication (BABOK KA), Project Management, Business Analysis, Interviewing & Hiring Business Systems Analysts, Soft Skills, Leadership & Management, Career as a Business Systems Analyst, Getting Started as a Business Systems Analyst. Bookmark the Permalink or E-mail it to a friend.

Praveen Udupa

All requirements are important!

I was running a meeting with a few stakeholders. I was imploring them to indicate the relative importance of requirements, but was hitting a brick wall; they kept insisting, "They all look the same to me. All requirements are important. They all are must-haves." I tried to reason with them multiple times over. There are just too many requirements...

3 Responses

This entry was published on May 17, 2016 / Praveen Udupa. Posted in Requirements Management and Communication (BABOK KA), Business Analysis. Bookmark the Permalink or E-mail it to a friend.

Alan

BABOK v2 - End-to-end data flow diagram analysis can highlight issues

As part of preparation to sit the IIBA CBAP exam, I wanted a one page summary of the overall BABOK flow. The first step of creating a summary matrix showing a derived master list of documents (e.g. Inputs + Outputs) versus the process that creates or uses it was interesting, but not entirely helpful. By using the matrix to create an indicative ...

1 Responses

This entry was published on Jul 09, 2014 / Alan. Posted in Business Analysis Planning (BABOK KA), Elicitation (BABOK KA), Enterprise Analysis (BABOK KA), Requirements Analysis (BABOK KA) , Requirements Management and Communication (BABOK KA), Solution Assessment and Validation (BABOK KA), Business Analysis, Structured Systems Analysis (DFDs, ERDs, etc.), IIBA & BABOK. Bookmark the Permalink or E-mail it to a friend.

Stephanie Famuyide

3 Tips for Obtaining Requirements Sign-off

Sign-offs are a sign that stakeholders agree with and approve the requirements that have been elicited and documented. There are multiple reasons why BAs seek stakeholder sign-offs and in some cases, it is not always clear whom it benefits. While some methodologies like Agile do not involve a formal sign-off, requirements sign-off does add va...

0 Responses

This entry was published on Feb 28, 2014 / Stephanie Famuyide. Posted in Requirements Management and Communication (BABOK KA). Bookmark the Permalink or E-mail it to a friend.

Ken Young

5 Pitfalls to Avoid in the Requirements Development Phase

Developing requirements is a process with many moving parts. It involves aligning multiple stakeholders from different areas within an organization to determine what must be developed to fulfill a business need. Because it is a process, there are a number of factors that can cause the process to break down and lead to the development of fault...

0 Responses

This entry was published on Aug 07, 2013 / Ken Young. Posted in Requirements Analysis (BABOK KA) , Requirements Management and Communication (BABOK KA), Functional Specifications, Business Analysis. Bookmark the Permalink or E-mail it to a friend.

Lee Grinberg, CBAP, PMP

How to convince stakeholders of BA value for the first time?

In my previous posts I outlined how I was able to succeed being the first and only BA at a company and the importance of establishing trust between you and the stakeholders. So you're the first BA at a company. All are looking at you and thinking what can this person do for me? Good question. What can you do f...

0 Responses

This entry was published on Jun 21, 2013 / Lee Grinberg, CBAP, PMP. Posted in Elicitation (BABOK KA), Requirements Management and Communication (BABOK KA), Functional Specifications, Business Analysis, Analytical and Problem Solving Skills, Career as a Business Systems Analyst, Roles and Responsibilities. Bookmark the Permalink or E-mail it to a friend.

Stephanie Famuyide

A Call to Every BA: 8 Mistakes to Avoid in Writing Requirements Specification Documents

According to the Strategies for Project Recovery report by PM solutions, based on 163 respondents, $74m invested in projects annually are at risk of failure. The report identified one of the top 5 causes of project failures as unclear, non-prioritized, contradictory, ambiguous and imprecise requirements. Information like this...

4 Responses

This entry was published on Apr 04, 2013 / Stephanie Famuyide. Posted in Requirements Management and Communication (BABOK KA). Bookmark the Permalink or E-mail it to a friend.

Adriano Comai

ISO 25010

ISO 25010, "Systems and software engineering - System and software quality models" was published in March 2011. The ISO 25010 standard defines 2 broad non-functional categories of requirements, "Quality in use" and "Product quality", articulated in 13 characteristics, many of which are further subdivided into sub-characteristics. This new ...

1 Responses

This entry was published on Jan 20, 2012 / Adriano Comai. Posted in Requirements Analysis (BABOK KA) , Requirements Management and Communication (BABOK KA), Testing & Quality Assurance (QA). Bookmark the Permalink or E-mail it to a friend.

Seilevel

Five New Year’s Resolutions for Requirements

It’s that time of year, where our thoughts turn to the holidays…the holiday parties, the shopping, the lights, visiting with family! For many organizations, the end of the year tends to be quiet on the IT front, for no organization wants to risk introducing problems into their production environment at year end. So as I look back at th...

0 Responses

This entry was published on Jan 14, 2011 / Seilevel. Posted in Requirements Management and Communication (BABOK KA), Project Management, Business Analysis, Leadership & Management, Career as a Business Systems Analyst. Bookmark the Permalink or E-mail it to a friend.

Seilevel

Is Traceability Possible Without a Requirements Tool?

I have spent the last year and a half working on an enterprise software solution development effort where we do not use a Requirements Management tool like Caliber or Visual Studio TFS. Our requirements are created in Word using standardized templates and distributed to Development and Test teams for consumption. Test cases are written in Excel an...

1 Responses

This entry was published on Dec 20, 2010 / Seilevel. Posted in Business Process Modeling Notation (BPMN) , Requirements Analysis (BABOK KA) , Requirements Management and Communication (BABOK KA), Project Management. Bookmark the Permalink or E-mail it to a friend.

Page 2 of 4

First Previous 1 [2] 3 4 Next Last

Modern Analyst Blog Latests

Jarett Hailes

Three Audacious Goals for Business Analysts in 2013

As we start a new year many of us will take the time to reflect on our accomplishments from 2012 and plan our goals for 2013. We can set small or large goals. goals that will be accomplished quickly or could take several years. For 2013, I think Business Analysts should look to go beyond our traditional boundaries and set audacious goals. Merriam-...

Howard Podeswa

Hey IIBA, What’s Up With That?

Recently, I was asked by the IIBA to present a talk at one of their chapter meetings. I am reprinting here my response to that invitation in the hope that it will begin a conversation with fellow EEPs and BAs about an area of great concern to the profession. Hi xx …. Regarding the IIBA talk, there is another issue that I am considering. It's p...

Adrian M.

BA ABCs: “C” is for Class Diagram

Continuing the ABC series for Business Analysts, Howard Podeswa created the next installment titled "BA ABCs: “C” is for Class Diagram" as an article rather than a blog post. You can find the article here: BA ABCs: “C” is for Class Diagram Here are the previous two posts: BA ABCs: “A” is for Activity Diagram BA ABCs: “B” is for BPMN