Oct 15, 2017
1989 Views
0 Comments
A requirement is “a condition or capability needed by a user to solve a problem or to achieve an objective” (AKA a goal). Thinking in terms of problems and goals thus is a core competence for the requirements engineer. But what in fact is a problem or a goal? This may seem to be a rathe...
A requirement is “a condition or capability needed by a user to solve a problem or to achieve an objective” (AKA a goal). Thinking in terms of problems and goals thus i...
The experience age will force the business analyst, more so than ever, to be closer to business. The focus will have to move from how the IT landscape looks at the architectural le...
Prior to proceeding with a strategic project, project leadership needs to ensure that the project still: aligns with the direction of the business entity, and fi...

Upcoming Live Webinars

Community Blog - Latest Posts

Peter
Peter
If you are building a reusable Security Product tool to specifically address Security Technical Implementation Guide (STIG)  Findings, should the requirements be considered Non Functional Requirements or Functional Requirements? For example if there are a number of STIGs such as: The minimum password length shall be 15 characters ...
1 Responses
Bert Wagner
Bert Wagner
It’s 4:30 pm on Friday and Mr. Manager comes along to tell you that he needs you to run some important ad-hoc analysis for him. Previously this meant having to stay late at the office, writing cumbersome queries to extract business information from transactional data. Lucky for you, you’ve recently started using Temporal Tables in SQL...
0 Responses
Ronak Sanghavi
Ronak Sanghavi
Current State For many years now, the most commonly used metaphor on Business Analysis has been the “Bridge”. However, in recent past, some in the BA community have started revisiting the metaphor resulting in a debate on how relevant it is. Of course, the value business analysis can provide for an organization does not depend on how i...
2 Responses

MA Blog - Selected Posts

The Dirty Harry Approach to Requirements, or “Are you Feeling Lucky, Punk?” Solve Problems First, Ask Questions Later - Part 1
Have you ever had to use a map to get somewhere, and after navigating around the wilderness for hours, eventually had to ask for directions because it... Read More...

When the Client Isn't the Customer
Usually when a Business Analyst is working on a project the client (which I’ll define as the party or stakeholder who receives the benefit of the Anal... Read More...

Continuing a project in the penumbra...
INTRODUCTION Being dropped in the middle of a project that is already in a bad shape (over budget, over schedule and under compliance) is not easy (o... Read More...

Templates & Aides

Templates & AidesTemplates & Aides: find and share business analysis templates as well as other useful aides (cheat sheets, posters, reference guides) in our Templates & Aides repository.  Here are some examples:
* Requirements Template
* Use Case Template
* BPMN Cheat Sheet




BA Humor & Cartoons

Performance Metrics for Analyst/DesignerModern Analyst?  Digital Skills Are a Must...
Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC