Archive for the ‘Business Analyst’ Category

5 December

Defining a Project Scope

The project scope is the core of an individual project.  Without a project scope the project will just float.  Proper needs assessments and other intricate details will be overlooked.  Each project is designed to resolve issues the stakeholders are experiencing in their company.  These well meaning individuals will dump data and information charts, lists and figures presumptuously on the desk expecting it to all make sense.  The “here’s the problem, fix it” attitude can be frustrating.  There are numerous feature requirements which must be met.  It is unclear as to what to prioritize where.  Cost estimates may not be accurate.  Delivery dates are tentative.  It is enough to make someone through up their hands in desperation and say “I QUIT!”.  The trained business analyst will just grin and dive in.  He or she will know what is needed is a project scope.

The project scope is the outline of the project.  The project scope is considered the itinerary of an individual project program.  The project scope is the step by step guide to determine who, what, why, when, and where.  It will be able to define to the stakeholders what they want to have done.  It will be able to list who will be doing which job.  The project scope will list why each step is critical to success of the project.  It will also address the time frame as to when the project should be completed.

The project scope will detail for the stakeholders outside resources being utilized for completion of individual tasks.  Each development team will be able to view the project scope and see what is required of them.  The project scope will also detail needs assessment and cost estimates.

Each project scope will be able to address technical constraints the stakeholders may or may not be aware of.  Within the project scope a detailed report of end user requests will also be added.  This will allow the stakeholders to understand why certain aspects of the project program are different than anticipated.

The project scope is an itinerary listing short term and long term expectations.  Short term goals will be listed allowing the stakeholders to check each milestone.  The project scope will also include a prioritized listing of essential requirements or features needed for short term and long term success of the project program.

One of the most critical reports in the project scope is the vision statement.  The vision statement will define in clear and concise wording the project scope.  The vision statement will allow the stakeholders to understand the problem and the solution needed.  The vision statement will state the user needs in clear terms.  The program features will be outlined in the vision statement.

The project scope is the “do to” list of the program.  A sort of brainstorming, or in some cases, model storming which allows all parties involved to be able to follow along.  Each department along with the stakeholders will be able to refer to the project scope throughout the completion of the project.  Without the project scope the project has no start or end point.  The project will most likely fail.

30 October

Customer Relations and the Business Analyst

In today’s market the customer should always come first.  This has been the bread and butter of many industries throughout the ages.  A satisfied customer is one who will keep coming back.  The customer is the one who helps the bottom line.  This is true in the field of business analysis.  It is the customer’s   needs which the business analyst is fulfilling.  The business analyst should help to strengthen customer relations.  Time put into this is time well spent.  Finding the customer to be unhappy is never a good thing.  Ask any good business manager what their number one priority is and they will answer customer relations.  Sometimes it does not always show.

Many of today’s corporations utilize a big part of their budget on improvements in operations.  The target is the bottom line.  What they fail to realize is this can and will drive customers away.  Targeting the needs of the customer is first and foremost in any business.  The same holds true with business analysts.

When going in to trouble shoot a system, the business analyst becomes a production manager.  If he or she does not put the needs of the customer first, the project will undoubtedly fail.  Listening to the customer to determine what is needed and desired is the start of a good relationship.  When the business analyst fails to listen the entire project could not only start on the wrong foot but end in disaster as well.

The business analyst must encourage feedback.  He or she must understand just what the customer is wanting, even if they do not know themselves.  The customer may know what he or she wants the project to accomplish.  They may know how they want something to run.  The customer just may not know how to say it.  He or she may collect data imperative to the project program.  It is the business analyst’s job to determine if the data is even relevant.  He or she is the liaison in this relationship.  He or she must have good customer relations skills.  The business analyst must speak the customer’s language.

Putting the customer relationship first can be a daunting task at times.  The bottom line is critical to success on any project.  There are times the business analyst will be caught up in keeping cost down and compromise the relationship he or she has with the customer.  The customer will be much happier if you go a little over budget and keep him or her happier in other areas of the project.

Sometimes it is easier to prepare reports and allocate spending to IT to accomplish a task than it is to spend time or money developing a plan for customer satisfaction.  The price any company could pay for this is a high one.  The business analyst is no different.  Customer satisfaction means keeping them informed of progress.  Speak in a language they understand.  Consult with them when a roadblock is met or when a progress point is passed.  Either way, keeping a constant rapport with the customer ensures a satisfied client.  This can lead to repeat business.  This helps the business to grow.

16 July

Business Analyst Job Description

The job description of a business analyst is rather extensive.  He or she must first determine the needs for a company by using many tools.  The business analyst may conduct interviews with management and other department leaders.  He or she must analyze documentation, facts and figures.  The analyst should incorporate a site survey to determine applications being used and what may be needed for superior quality performance.  He or she will consider business applications currently being used which may or may not be working.  The business analyst will do a business analysis and a work flow analysis to assess difficulties in reaching goals and to determine a better strategy.

A qualified business analyst will be able to ascertain the true needs to be met by the project.  He or she will be able to transfer information from management into needed data.  Statistics from other sources will be assessed and turned into usable information.  The business analyst will be able to compile a report in an easily understood projected vision to be implemented.

The job description of a business analyst does not always but should include excellent communication skills.  He or she needs to be able to address a diverse group of inside and outside personnel.  He or she should be able to motivate the departments to challenge themselves and reach their goals.  The business analyst will be required to relay information from the IT team or department to the clients in easily understood terms for both groups.

The business analyst should have past experience to draw from when processing data and information.  He or she will possess knowledge used in case studies and transfer it into usable information.  Prior situations should be able to be compared to avoid counterproductive actions.

The business analyst will be able to draw from known resources when outsourcing or external interactions are needed.  He or she will be able to incorporate joint venture relations into the project scope when it is necessary.  Determining this critical point is instrumental in the job of a business analyst.

Acting as a liaison between clients and development departments, the business analyst shall distinguish requests from needs.  He or she will assess the proposed project plan to ensure all needs are met.  The verifiable solution shall be one which guarantees success.

A statement of purpose will be proposed by the business analyst to ensure the end results are satisfactory to all involved.  There will be a project goal integrating all data collected.  Documentation will be provided by the business analyst to determine which aspects of the project will be handled by outside sources.  These sources shall be listed with critical attention being paid to the specific task of each organization.

The business analyst will have a good understanding of what is expected.  There are many aspects of the project proposal.  He or she will involve themselves with each unit to instill continence and still maintain productive action.  The professional analyst will be able to focus on each department independently and maintain a broad vision of the project scope.  These are the duties of a business analyst.