Feb 22, 2026
949 Views
0 Comments
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-centered design principles, predictive analytics, and continuous stakeholder feedback. Its purpose is to address the limitatio...
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...
AI can generate requirements in seconds—but BAs know that’s not the same as getting a solution adopted, funded, and delivered without surprises. This article speaks dir...
This article shows business analysts, systems analysts, and product managers how to build “trust into the UI” by writing practical provenance requirements for AI-enable...

More Articles

17938 Views
33 Likes
0 Comments

One of the Sidebars to the Business Agility Manifesto unabashedly indicts the software industry for its long-standing failure to provide direct support for obligations, an obvious and fundamental aspect of real-life business activity.

Where can you find obligations in business? Virtually everywhere you look: acts, laws, statutes, regulations, contracts, MOUs, agreements, terms & conditions, deals, bids, deeds of sale, warranties, guarantees, prospectuses, licenses, citations, certifications, notices – and of course, business policies.

Direct support for obligations is a fundamental capability your organization needs in the Knowledge Age. What’s it about?

12186 Views
12 Likes
0 Comments

Most of us are well aware of the problem of organizational silos and non-integrated applications and channels. The question is how can we plan to eliminate them?   The notion of a value chain is to take a 10,000-foot view of the business based on how value is created incrementally toward final delivery of products to end-customers. In other words, a value chain model looks holistically at the value-adding capabilities of an organization end-to-end, irrespective of organization lines of responsibility or existing functional activities.

45131 Views
80 Likes
0 Comments
In a classic business analyst universe, requirements are the soul of all the work a business analyst does. If a business analyst fails to identify and translate the right requirements, they’re out of a job. This is the reason why a successful business analyst is always good at requirements handling/management process. What makes requirements...
45274 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.
21845 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.

 

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