Enterprise Analysis (BABOK KA)

Can the design of the enterprise’s business processes evolve to a state where the Business Analysts can customize the business processes specifically to the requirements of the owner using inventoried primitive elements; similar to using the metaphorical inventoried components/parts for a laptop? And can these primitive elements get assembled into new/enhanced business processes within a short period of time?

SWOT is an acronym for Strengths, Weaknesses, Opportunities and Threats. By using these four areas to identify an organization’s characteristics and climate, a SWOT Analysis offers a high-level evaluation of your company’spros and cons.The goal of a SWOT Analysis is to help an organization to identify strategies for success.

Business analysts need to understand their role on a project. Please note I use the word 'role' and not 'job' or 'the work we do'. As business analysts, our role is to deliver business value. If you do not have a clear definition of what that business value is, how can you expect to deliver it? “Improve the customer experience.” Where is the business value in that? And how do you measure it? When faced with objectives that are poorly defined, the business analyst is allowed to become like that irritating toddler, constantly asking “why? why? why? why? why?”.

This year’s top 10 business analysis trends focus on leveraging the power of requirements at all levels through Agile and business architecture to deliver business value to the organization. We also expect to see business analysts being utilized in more robust ways, forcing them to take on new skills to meet a broader job scope.

Most of the projects inevitably struggle at some point or the other if the scope is not defined properly. The right note to start a project is to have a clear Project and Solution/Product scope at hand. It is very critical for a Business Analyst to clearly understand and define the Solution Scope in black and white before even going into the Requirement Elicitation phase. This article focuses primarily on key aspects of understanding and defining Solution Scope in traditional methodologies.  

We are frequently asked about connecting and tracing software architecture elements to business processes by integrating BPMN business models and software models in UML (Unified Modeling Language)... Now we will explore how to supplement business architecture with software architecture. 

Of the four articles in the series, this particular article is the most sensitive. If not practiced with caution, trying to influence someone or a situation could have a devastating impact. Therefore, this article comes with a disclaimer: “Stupid is as stupid does.”
 

Enterprise analysis (also known as strategic enterprise analysis or company analysis) is defined as focusing “on understanding the needs of the business as a whole, its strategic direction, and identifying initiatives that will allow a business to meet those strategic goals.” 

Now that you’re prepared to work with executives, I’m sorry to inform you that the tough stuff is about to begin. While preparation and understanding are crucial elements, and speaking executive language further deepens our conversations, the real meat on the dog bone is taking the next step and beginning to develop your relationship and establishing yourself as a trusted advisor.
 

In this four part series, I will give you the confidence and motivation you need to make a difference; a difference that will allow you to “Bark with the Big Dogs.” What I’m about to share is tried, tested and true. There are no gimmicks. Before you read on, ask yourself this: “Am I willing to try something different?”

“…The Analyst will [...] facilitate the identification, design and implementation of business and systems solutions in a rapidly growing and evolving business…”   What strategic initiatives might a business analyst as described above discover, and how will they deliver the “business and systems solutions” in today’s 21st Century competitive environment?
 

Ron Ross and Gladys Lam have written an important book for the business analyst community. It aims to get business analysts out of the technology ghetto that many of us get stuck in. Regardless of the type of analyst you are, I think it would be worth your time to get your hands on and read this book. I’ll explain why below.

So many IT projects ultimately end in failure and are simply written off. Same old story, time and time again. Why is it so hard? Why can’t we figure out beforehand whether some solution will actually work once we roll it out? Most project management approaches and many IT methodologies include steps for building business cases and provide guidelines for project planning and estimating. What’s missing?

Welcome to the new series of articles on the BA as the 21st Century Creative Leader. It was a perfect storm. As we entered the second decade of the 21st century, we found ourselves struggling to adapt. ... It is no coincidence that the business analysis profession is taking hold to address many of the 21st century business challenges.
 

To remain competitive, it is more important than ever for an organization’s leadership team to use business analysis (BA) practices to execute strategies through innovative solutions. Over the years, business analysis has been rapidly developing as a profession and as a core business practice in many organizations; however, all too often business analysis is still in its foundational stages.