Mar 15, 2026
738 Views
1 Comments
This article is a practical case study from my work modernizing financial document collection and I-20 issuance for undergraduate international students at a public university. I’m focusing on the business analysis decisions behind the change: how we uncovered hidden dependencies, clarified ow...
This article is a practical case study from my work modernizing financial document collection and I-20 issuance for undergraduate international students at a public university. I&r...
This article examines how the job of planning the roadmap and choosing which features should be prioritized is being changed by AI agents, according to this story. Instead of going...
This article introduces a new model for risk management that is led by business analysts (BAs). This model builds upon traditional frameworks by incorporating user-center...

More Articles

45460 Views
36 Likes
2 Comments
As a business analyst, one of the most valuable skills you can acquire is the ability to build relationships. This in itself may have more of an impact on your long-term BA career than your business knowledge and technical skills. Because BAs are often key participants in so many different projects and initiatives, it can be difficult to nurture all of the relationships established throughout your organization. The relationship that I will be focusing on, however, is the relationship with the developer(s). Solid business analyst-developer relationships are often easier to facilitate in agile environments; therefore, it is essential to put more effort into managing this relationship in an environment that uses a waterfall or traditional methodology. Below are some tactics we as BAs can use to make developers’ lives easier and enhance the business analyst-developer relationship.
21933 Views
36 Likes
1 Comments

The relationship between a business analyst and the stakeholders is one of the fundamentals to the journey of delivery. If the relationship is dysfunctional, the process of delivering the solution will be negatively impacted... Each one of us is blessed with a different personality that makes us unique. In the case of business analysts, personality plays an important role, thus making it a key to survival. Business analysts are adaptive survivors. It is imperative that every impacted stakeholder is engaged and collaborating. It's fundamental to a robust requirements analysis process. Having mentioned the need to bond with your stakeholders, let’s see what skills are needed to be a successful business analyst.

 

13796 Views
13 Likes
0 Comments

Decisions are at the heart of every business transaction. That’s why it is crucial to make the right decision at the right moment in time. In high turnover environments this can be an issue, as new staff need constant monitoring as they ‘learn the ropes’. This can lead to a significant deficit in efficiency and customer satisfaction.

 

To counter this problem, we advocate what we call a ‘Decision-Centric Approach’, which is designed to address the business challenge by enabling innovative technology in those crucial ‘moments of truth’

28248 Views
26 Likes
0 Comments

 

What do you put down in non-functional requirements when you are documenting requirements in your project? When we say non-functional we typically mean those requirements that are not related to functionality of the system, then what exactly are these and why do we need them.

14770 Views
17 Likes
0 Comments

There are a small number of core concepts that can be said to embody the essence of an enterprise. This article asserts that one such concept is the business algorithm, the unique combination of business logic, algebra, and rules that is used by the enterprise to convert real world data and events into useful outcomes that benefit all stakeholders – giving rise to happy customers, prosperous proprietors, and fulfilled staff! ... The business algorithm is a unique and fundamentally important concept that no enterprise can function without. There are other aspects of the enterprise like brand or culture that may also claim to be ‘of the essence’, but the business algorithm is the only such concept that has a formal existence inside computer systems. The business algorithm is like the soul of the enterprise, uniquely defining the enterprise and giving it life via its systems. As such it has a unique claim to relevance as a first-order systems requirements artifact.

Page 82 of 100First   Previous   77  78  79  80  81  [82]  83  84  85  86  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