| Topic : Data Analysis in Business Intelligence |
|
|
Associated with other topics :
Posted in Community :
Business Analysts In IT
|
Activity:
94 views;
last activity : 07 06 2010 20:18:09 +0000
|
|
|
|
1
Quantitative Approach
2
Custodian of Treaciability Matrix
3
Communication
4
Business Needs
5
Elicitation Process
|
||||||||||||||||||||||
|
It is a given that the role of a business analyst is a crucial one and typically the BA is called when something is Amiss. At the same time the idea I am putting forward is achievable, but depends on the outlook of the organization. What I would recommend is to have a quantitative approach to this problem:
This approach can also be used to monitor and improve the involvement of other roles in the organization. |
1
|
No supporting Arguments for this idea
|
Starting from feasibility study to UAT to post go-live support in all stages of SDLC Business Analysts are required to perform their role so that the business need and IT solution deployed to meet that need are in sync. Business need defined in the begining can be traced to the solution delivered in the end in the form of a trceability matrix and business analysts plays the role of custodian of such treability matrix through out the entire SDLC. |
1
|
No supporting Arguments for this idea
|
Ensure that requirements support your overall Business needs, Having a list of business requirements is certainly an integral part of your long journey toward project success. However, before celebrating, you need to be absolutely certain that those requirements support your organization’s overall business objectives. For example, if a company is looking to increase the efficiency of its call center by 20% over the next 12 months, it must first determine whether the requirements for achieving that goal fall within the business’ needs in terms of benefit and cost. If the requirements call for too much time and money to be spent, than the validity of the project should be called into question.
|
0
|
No supporting Arguments for this idea
|
I think one have to clearly understand the requirements elicitation process, Throughout the business community, it is widely agreed upon that about 50% of troubled projects are troubled because of poor requirements definition. So, obviously, at the beginning of a project, it is vital to effectively elicit all of the requirements needed for success. This is accomplished by relying once again on our old shipmate enterprise analysis.
|
0
|
No supporting Arguments for this idea
Add your Idea
Could not find any idea interesting in:
"Guide for infusing Business Analysis into your Projects " ?
Click here
to add a new idea...
Found the idea contest
"Guide for infusing Business Analysis into your Projects "
interesting ?
Click here to refer to your connections and communities
Leading recruitment Firm
- Create a confidential Career Profile and Resume/C.V. online
- Get advice for planning their career and for marketing of experience and skills
- Maximize awareness of and access to the best career opportunities
Viewers also viewed
|
|
|
Fundamental Analysis vs Technical Analysis |
|
|
346 referals
15 arguments,
902 views
|
|
|
a comparison of top-down and bottom-up planning in management. |
|
|
40 referals
9 arguments,
1189 views
|
|
|
A successful BPR can result in dramatic performance improvements, increase in profits, better... |
|
|
1 referals
4 votes,
776 views
|
|
|
|
|
|
|
Sponsored Jobs
More From Author
I think business today, any business project is ultimately measured by one thing, return on investment. There are dozens of metrics to be measured along the way from budget and deadline to scope and stakeholder satisfaction, however, at the end of... |
How to make sure that you are safe during the period of layoffs. |
I think it has good potential for both DSL extension and local backhaul but the disruption caused to traditional satellite services where applicable (lower extended C Band) is a limitation. If this could be neatly overcome, i think it would have much... |