42218 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.
19395 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.

 

11648 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’

25250 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.

12749 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.

39201 Views
29 Likes
0 Comments

Project statistics state that most project rework/failure is due to incomplete/improper/unclear requirements, hence the role the Business Analyst becomes even more critical as they shoulder a huge responsibility of eliciting and collaborating with the stakeholders to obtain clear, concise and complete requirements.  The elicitation and collaboration knowledge area focuses on drawing forth or receiving information from stakeholders and other sources by directly interacting with stakeholders, researching topics, experimenting or simply being handed information.

18049 Views
17 Likes
2 Comments

Many professionals and organizations understand the value of a business analyst (BA), however, the role itself is still ambiguous to many. There are numerous articles and resources that outline business analysis and the general role of a BA so I won’t be focusing on those aspects. Every organization and industry is unique therefore the needs and expectations for a business analyst can vary greatly. However, there are a few core competencies that remain consistent. The goal of this article is to give BA practitioners (especially new practitioners) an approach to determine what their specific organization expects from them in order to get on the path of success throughout their career. Below are some steps you can take to define your role in the organization you serve.

11683 Views
22 Likes
1 Comments
Well, for one thing, consider the user. I mean, what is a ‘user’?”...  I understand that is what the term is used for, but can you point me to a user. Don’t answer. You could probably point to any number of people around you who would be users.  ...That man over there is using his cell phone, some app or other.... The nice lady who fixed my coffee entered the transaction on a computer in her stand to account for the money and the inventory. She is a user. 

17066 Views
16 Likes
0 Comments

Business Requirements Advocacy is neglected in the business analysis practice!  Once considered to be an essential part of IT teams, the business analyst has become an integral position in any successful, market-driven organisation. Rightly said to be the change agents for any business, business analysts help organisations adapt to the changing environment while meeting the needs and demands of all their stakeholders, including employees, customers, and suppliers.

13459 Views
14 Likes
1 Comments

There is much to say about the often challenged relationship between IT and “the business” that has existed since IT became IT. Centralization, decentralization, self-service tools and applications, enterprise tools and applications – the pendulum swings again and again.  You’d think by now that we’d get it. There is no one all-encompassing data management or BI solution that will satisfy all of your data related requirements.

16318 Views
17 Likes
0 Comments

In this article, I am going to focus on the key 3 tools that you can use to help you identify the pain points in your workflow.  One of the key things to identify when working in a visual manner is understanding where your blockers are. It is only when you have identified these blockers, you then able to do something about them. There is no use trying to change something when you don’t have the evidence to baseline the problem. As business analysts, we wouldn’t tell the business where the problems are without conducting a thorough root cause analysis. So, why do we do it at work, why do we think without evidence we know exactly what the problem is and the impact it has on. 

14764 Views
23 Likes
0 Comments

The purpose of this article is to cite an example of using Lean-Agile project management for a small home construction project – a bathroom remodel. The remodeling firm unknowingly uses a Lean-Agile project approach that was the result of lessons learned over years of experience. In fact, when I questioned the remodeling firm about Lean-Agile, the firm’s response was “What is that?” Regardless of what you call it, the firm uses their construction approach because it works.

23894 Views
33 Likes
1 Comments

Somebody inquired to me in one of the professional networking site if I can suggest what the difference between a Business analyst and data analyst is.

This is a dilemma that is common in the minds of numerous professionals who are new to Business analysis or intending to get into this space.

As the name proposes a first hand analysis by any layman will state that the business analyst role includes analysis from a business perspective, though the data analyst role deals with primarily analyzing data.

25605 Views
19 Likes
1 Comments

In order for any project or initiative to be successful, an agreed upon business need must be determined. This need may present itself as a problem or an opportunity. Business Analysts must be able to guide the business in articulating which of these is the catalyst for the initiative prior to starting any BA work. Projects without a clearly defined business need get drawn out due to issues such as increased stakeholder conflict, poorly defined requirements, and excessive rework. So, to save you some pain and effort, below are some reasons why defining the business need is a critical starting point for any organizational change.

10936 Views
10 Likes
3 Comments

I wanted to get to the bottom of things once and for all. We had been having several discussions about the birth of business analysis and how the profession of business analyst came into being. There were no business analysts, at least as currently incarnated, in Data Processing when I started a long time ago, and a look into the history of business analysis might be interesting. So I went sought out Doctor BA who has been around a lot longer than I.

Page 25 of 87First   Previous   20  21  22  23  24  [25]  26  27  28  29  Next   Last   

 



 




Copyright 2006-2025 by Modern Analyst Media LLC