Feb 01, 2026
1032 Views
0 Comments
In tech teams, the word “just” (“just add a field,” “just change a label,” “just add an exception”) is a warning sign—not because people are wrong to ask, but because they’re only seeing the visible slice of the work. This article introduce...
In tech teams, the word “just” (“just add a field,” “just change a label,” “just add an exception”) is a warning sign—not beca...
This article shows BAs, systems analysts, and product managers how to turn vague AI “safety” statements into clear, testable requirements. It introduces a simple artifa...
The advent of Agentic AI forces a fundamental, non-negotiable re-evaluation of business analysis practice. The GenAI Paradox mandates that the Business Analyst is no longer merely ...

More Articles

19918 Views
7 Likes
0 Comments

In all my years as a Consultant Business Analyst, having reached a level of proficiency, I have realised that being a business analyst is seldom about the hard skills. In fact, it is more about the soft skills and BAs who operate at that level are more impressive and effective in their job. Hard skills like documentation, requirements elicitation, process maps etc. are easily taught and acquired but the soft skills are developed with experience and the right attitude towards this role. Over time I feel the perception of the value of BAs has diluted and I blame those who have been superficial about performing this role. Those who think their role is just about the tangible artefacts like the business requirements document, process maps, business case, etc. Those who think they are here to deliver a project and nothing else. Those who think the BA’s job is to take orders and execute. But the fact is that the role of a BA is a lot more subtle than one thinks. There is a much broader aspect to this role, which is often forgotten, and we get caught in deliverables and artefacts.

Let’s look at some aspects of this role, which are common knowledge and broaden our perspective of that. When the mindset of the Business Analyst changes to the bigger picture and to the more delicate facets to this role, you perform much better as a business analyst and are a more reliable and thus a desirable professional for companies.

29317 Views
26 Likes
0 Comments

My experience taught me that the Scrum process framework is not the complete story. Scrum does not identify roles for the business analyst, system architect, tester, UI designer or deployment engineers. Instead, the work normally performed by these roles is performed by the development team or the product owner. It is possible that the Scrum development team includes people with all of these skills, but the problem is that all the development team work is performed within a sprint cycle. The only activity that Scrum identifies outside a sprint cycle is maintenance of a product backlog (and even then it is not documented as an activity in the Scrum framework).

20710 Views
3 Likes
0 Comments

Ever wondered how to write foolproof acceptance criteria? Or even wondered what a business analyst can do to ensure that requirements are testable? Acceptance criteria define the minimum requirements the solution must meet. A business analyst plays a key role in defining the tests around it. The acceptance tests can be at various levels of requirements detail. Starting from high-level requirements to detailed requirements. Let’s take a look at common challenges involved in this part of the world, along with a few ideas to overcome those.

21274 Views
3 Likes
0 Comments

For the past year the COVID-19 virus has forced us to limit our exposure to the outside world. This virus has given us a need to find a home activity to entertain ourselves and our families. One of the activities I have pursued is assembling jigsaw puzzles. As you may know, a jigsaw puzzle is a challenge in assembling picture pieces into a single image. They come in various shapes and sizes. After doing a number of these puzzles, I noticed the similarity between this fun activity and executing a project.

24091 Views
8 Likes
1 Comments

Business is rarely 100% smooth sailing. Regardless of the industry or sector, there are always challenges to overcome and obstacles that must be faced on the pathway to success.

Some organizations aren’t strong enough to ride the waves. Others, however, are, and the reason for their strength is that they’re not navigating the murky waters alone - they’re supported by an ambitious, results-driven business analyst. Research even shows that business projects are more likely to succeed with the help of a great BA.

At their core, business analysts are part problem solvers, part change-makers. The core responsibility of a business analyst, or BA, is to work with organizations to identify a sticking point that’s standing in the way of them achieving their goals, introduce a solution to this problem, and help the business to adapt in a way that makes it easy to implement the solution into the business environment.

Typically, a great business analyst is someone that’s confident enough to think outside the box, who’s solution-oriented and innovative. But today these skills alone aren’t enough, especially as the role of the BA is changing.

Page 52 of 100First   Previous   47  48  49  50  51  [52]  53  54  55  56  Next   Last   

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

Community Blog - Latest Posts

In a competitive and rapidly evolving financial landscape, understanding member needs is vital to maintaining strong relationships and delivering meaningful value. Yet for many institutions, especially those with legacy processes, collecting structured member feedback can be surprisingly underdeveloped. This was the case at the Federal Home Loan Ba...
One of the most underrated skills for a business or system analyst in integration projects is knowing when to recommend a message queue — tools like RabbitMQ, Kafka, or Azure Service Bus. Let’s be honest: not every integration needs one. But when it does, queues can save your system from chaos. What Queues Actually Solve Messag...
When designing ERP integrations (for AR/AP document flows), Business/System Analysts often face a range of “gotcha” questions — technical, architectural, and sometimes unexpected. Here are some of the real-world questions I ask clients during the API and ERP connector discovery phase: What’s the minimum required ERP v...

 



Upcoming Live Webinars

 




Copyright 2006-2026 by Modern Analyst Media LLC