Entries for July 2018

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

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

11660 Views
17 Likes
2 Comments
With this article, I’ve done the heavy lifting for you, by mentioning some of these jargon-based pearls of wisdom here. You need to realize that in order for you to make some headway in the corporate world, you’ll need to get some skin in the game, stop being an armchair general and put your head on a block instead.
29008 Views
65 Likes
2 Comments

Chaos! Stress! Everyday mess! Isn’t this an everyday situation for a business analyst? If not, either you’ve job satisfaction or you’re not being introduced to the real world of business analysis.

A person might possess great skills, however, (s)he might not be able to utilize skills without the right mix of tools and environment. A toolbox enables a person to implement the skills in the most efficient way. Possessing necessary tools is just the one part of it. Another is the knowledge to utilize the right tools at the right time to cater the solution and ensure timely committed delivery.

What are these tools? How do we map the usage of tools to the given circumstance? How can we efficiently utilize the tool? Does it depend on the solution or the approach?

18070 Views
13 Likes
1 Comments
A replacement project replaces an existing software system with a new custom-built system, a commercial off-the-shelf (COTS) system, or a hybrid of those. There are some challenges that most replacement projects share, including stuffing in unnecessary functionality, degrading the organization’s operational performance, users refusing to adopt the new system, and having such a large project that it never deploys. Focusing requirements practices on addressing these issues directly can increase the likelihood of a system replacement that delivers the desired value and is accepted by the users.

 



Upcoming Live Webinars

 




Copyright 2006-2024 by Modern Analyst Media LLC