The Community Blog for Business Analysts


Requirements Management and Communication (BABOK KA)

NO Image:
Requirements define the needs of the project to provide best of its utility and benefits. If they aren’t clear or analysis is not done properly, it might lead to failure of the project no matter how good the concept and design is. Just as a system is composed of various functionalities, requirements too are identified in various forms. This ...
0 Responses
This entry was published on Apr 10, 2017 / Surbhi Mahnot. Posted in Requirements Analysis (BABOK KA) , Requirements Management and Communication (BABOK KA). Bookmark the Permalink or E-mail it to a friend.
All professionals talk about identifying business needs, identifying requirements to create tools so that they can help businesses take better decisions. In your career as an IT professional, I am sure at some point you must have heard terms such as “Requirements”, “Business Requirements”, “Software Requirements”...
3 Responses
This entry was published on Mar 16, 2017 / Surbhi Mahnot. Posted in Requirements Analysis (BABOK KA) , Requirements Management and Communication (BABOK KA). Bookmark the Permalink or E-mail it to a friend.
Scope – the last frontier.  We are on a mission where no business analyst has gone before.  To explore strange new diagrams and to have the project scope clearly understood.  Extra credit to those who remember which TV show that was from!  Scope and context are the number one reason business expectations about a project ar...
0 Responses
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
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.
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
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.
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.
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
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.
  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.
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
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
I've been blogging lately about a couple of topics pertaining to 'agile' methods. Along those lines, I wanted to consider one suggested practice that I think is worth reflecting on, that is; the treatment of NFRs (non-functional requirements) as stories. Let's draw back for a moment. Regardless of process approach, be it traditional or agile, po...
0 Responses
This entry was published on Dec 17, 2010 / FergalMcGovern. Posted in Business Analysis Planning (BABOK KA), Requirements Analysis (BABOK KA) , Requirements Management and Communication (BABOK KA). Bookmark the Permalink or E-mail it to a friend.
I know you are going to call me crazy, but I just have to let everyone know.  Machines are controlling us.  Don’t say I didn’t warn you.  You don’t believe me?  Okay, I’ll explain. People come and go in organizations.  Systems tend to stay much longer.  Simple enough right?  Here is the kicker.  When that sy...
0 Responses
At Mendix, we find that our customers appoint a particular kind of person to work with our products. Sometimes they’re from IT, sometimes they’re a business analyst or project manager – in any case, they practice the skills of both fields. Times are changing, departmental lines are blurring, and a new breed of business superhero has risen: the BE. ...
4 Responses
This entry was published on Oct 05, 2010 / Mendix.com. Posted in Requirements Management and Communication (BABOK KA), Business Analysis, Soft Skills, Career as a Business Systems Analyst. Bookmark the Permalink or E-mail it to a friend.
Its being held in Sydney Australia September 27th- October 1st 2010.If you are attending this conference don’t miss out on the  Requirements Engineering Education and Training Workshop that is taking place September 28th. Do you want to broaden your skills? Learn new techniques?  This is the workshop for you. This workshop will add...
6 Responses
This entry was published on Sep 06, 2010 / Seilevel. Posted in Requirements Analysis (BABOK KA) , Requirements Management and Communication (BABOK KA), Business Analysis. Bookmark the Permalink or E-mail it to a friend.
By Jhulgan I used to dread hearing the question, “So what do you do for a living?”  This was often usually asked by a family member or other acquaintances not familiar with the software development lifecycle, IT, or business processes in general.  For business analysts, product managers, and other software requirements types, it’s diffic...
5 Responses
Not a suggestion for eliminating the process of documenting a software application, but rather a proposed for replacement of the documenting activity and manually produced documents with something more manageable and less likely to frighten the development team. Initiative for this work comes from a number of discussions I have been following and ...
1 Responses
This entry was published on Mar 22, 2010 / Leslie. Posted in Requirements Management and Communication (BABOK KA), Functional Specifications, SDLC, Process, and Methodologies. Bookmark the Permalink or E-mail it to a friend.
Ad Hoc Procedures My belief is that software development should be more of a science and contain as little artistry as necessary. It is great to come up with ingenious processes and guidelines for developing your software, but if they impact your colleagues you must get buy-in from everyone who is impacted before you start using them. Some people...
1 Responses
This entry was published on Mar 18, 2010 / Leslie. Posted in Requirements Management and Communication (BABOK KA). Bookmark the Permalink or E-mail it to a friend.
Page 1 of 2First   Previous   [1]  2  Next   Last   


Blog Information

» What is the Community Blog and what are the Benefits of Contributing?

» Review our Blog Posting Guidelines.

» I am looking for the original Modern Analyst blog posts.



Modern Analyst Blog Latests

Jarett Hailes
Jarett Hailes
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-...
2 Responses
Howard Podeswa
Howard Podeswa
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...
11 Responses
Adrian M.
Adrian M.
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
1 Responses
Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC