What can a Business Analyst do differently than project or program manager (Design Architect) with respect to successfully getting the project implementation done.
RE: What can a Business Analyst do differently than pr...
A project/program manager, as the name suggests, is mostly concerned with the progress of the entire project and taking care of the project members. This includes cost management (invoicing, billing), time management (scheduling), risk management (project closure) and similar things.
A business analyst is mostly concerned with gathering and documenting business requirements (application requirements) and communicating them to the development and test teams.
RE: What can a Business Analyst do differently than pr...
Business Analyst role is not entierly different than Project manager role but Project Mangaer is more bigger role than business Analsyst. Project manager is responsible for all the deliveriables like - schedules/ timeslines - resources management - risk management - Daily/weekly status report to project stack holders etc. where as business analyst sometimes report to project manager or may report to business manager. Business Analyst deals with business users to gater requirements, prepare RD,FD and coordinate with development team for development and then do the testing inolve with users in testing get the sign off and move component to live environment.
RE: What can a Business Analyst do differently than project or program manager (Design Architect) with respect to successfully getting the project implementation done.
Most of the development projects get delayed or fail because of incomplete, changing, unclear etc etc requirements. This is where the BA role comes where in he works within the scope of the project but this role demands efficiency in terms that he is able to gather all the requirements from the client, has the understanding to clarify/classify (raise questions to understand the req.) reqs, is technically sound enough to work out the feasibility of the req., has good writing abilities so that can draft an SRS which becomes the bible for the developer/project.
A requirement going wrong at the BA end can blow up toa huge bug/problem/CR by the time it is ready for testing.
Hence a BA shall be successful if there are least req changes and clear req which shall help the project to be implemented smoothly.
