Project Management Central

Please login or join to subscribe to this thread

Topics: Business Analysis/Requirements Management
Business Analysis - what is the lifecycle of a business analysis with respect to a project?
Network:770



Projects are borne out of business requirements, and analysis of business requirements with respect to possible solution is the scope of Business Analysis. In this context, it is interesting to know what would be the lifecycle of the Business Analysis- covering the start- progress and end.. we may discuss and elaborate here.
Sort By:
Network:298



Hope, I understand your question correct.
Business Analysis is triggered by market and mainly customer demands. So, it exists as a permanent challenge causing change and also a demand for a project or even several different projects.
Anonymous
What should be the major milestones build in a project schedule for the "re-design" of a website?

My team is currently working on a wordpress platform but the new website will be built on blackbauds luminate.

We are outsourcing a design team to do the design work.

The development will be done by a different group.

I am managing the design piece.

What should be the major milestones and how is it best to build the schedule and durations.

The design group is on the other side of the country so the work will be done remotely.

I have in-house design consultants but they are not doing the work.

Any suggestions on how to manage this project?

We also have a tight timeframe for the design prototype to be handed off to Blackbaud by 11/01.
Network:1637



My recommendation is going to PMI and IIBA documentation. I worked from the genesis of the role generation in theory (working with both as volunteer to define the role and to create the standards) and in practice. Business Analysis is beyond requirements. But related to project the best way to understand it is: project requirements are defined from product requirements. Business analyst is accountable for product requirements while project manager is accountable for project requirements. But no project exists if the business analyst does not work all the work needed to decide about the project existence and when project ends business analyst still remains active to monitoring if defined benefits are achieved. if not, a new cycle begins.
Network:770



@Sergio, Thanks for your inputs, I do agree with your mention that business analysis function even goes beyond project.

@Peter Ambrosia, Thanks, for sharing your thoughts about pervasive nature of business analysis function.
Network:11

I agree to you Peter Ambrosy, that was a good explanation indeed. Business Analysis is important because it plays a crucial role in a business or in a company. It influences and it can control the strategic planning and processes of a business.


Maryann Farrugia, CEO
Network:144



Hi Satish,
Based on my experience, here is my explanation...

Precisely, in the traditional waterfall model, business analysis is done by analyst (BA)

Let me twist the question which helps me to elaborate the answer and then come back to original question at the end.

Question: what is the life cycle of Business Analyst (BA)?

BA comes in the Requirement gathering phase, which is facilitated and monitored by a PM.
BA documents it (BRD/SRS/FSD) and get it reviewed and approved by external stakeholder (client), happens under the direction of PM
Once the document got approved (sign off), then PM will acquire a design, development and QA team and asks BA to walk through the requirements to the entire team. Ideally QA is accountable for the requirement document as they will initiate the test cases based on the requirement and others are responsible to align with the document

NOW, BA will be released from the project once implementation phase kick starts.
Other phases like Design, Develop and SIT/QA will be executed based on the requirement document (SCOPE) and then the UAT phase will begin.

During the UAT phase, BA will be assigned back to the project (may not be dedicated resource) to train the business users, fill the gaps, disconnections and helping in determining the CRs (Change Requests) if any, since he/she was interacted with business users during the requirement gathering phase, his/her intervention during UAT will help smoothen the UAT process. But it is always preferred for the PM to have equal knowledge as BA has, to reduce the dependencies and there are other benefits as well, mainly controlling the scope creeps with eventually balance the other constraints.

Coming to the original Question: life cycle of business analysis, is from the inception of the project to closure, irrespective of the SDLC, but the roles will differ based on the methodology used and RACI chart will always help to know who owns it.

Hope the information is helpful...!
Network:29



The short answer is that business analysis never stops! Regardless of the methodology you follow, you will always have business analysis throughout the project lifecycle. Only the nature of business analysis changes. In the inception and design phases you would be eliciting requirements from stakeholders. In development phase you would be refining it and answering business queries from developers. In testing phase, you would be validating it and making decisions for defects based on business requirements. Post production too, you might discover new requirements based on customer feedback. Effectively, business analysis evolves but doesn't stop!
...
1 reply by Sunil Kumar Rangu
Sep 19, 2018 5:11 AM
Sunil Kumar Rangu
...
It depends on the contract type, whether or not to continue the business analysis post production. In a fixed price contract type, if the project is closed and the contract ends, then analysis (and other aspects) stops.
Network:144



Sep 18, 2018 8:29 AM
Replying to Shweta Pai
...
The short answer is that business analysis never stops! Regardless of the methodology you follow, you will always have business analysis throughout the project lifecycle. Only the nature of business analysis changes. In the inception and design phases you would be eliciting requirements from stakeholders. In development phase you would be refining it and answering business queries from developers. In testing phase, you would be validating it and making decisions for defects based on business requirements. Post production too, you might discover new requirements based on customer feedback. Effectively, business analysis evolves but doesn't stop!
It depends on the contract type, whether or not to continue the business analysis post production. In a fixed price contract type, if the project is closed and the contract ends, then analysis (and other aspects) stops.

Please login or join to reply

Content ID:
ADVERTISEMENTS

I hope if dogs ever take over the world, and they choose a king, they don't just go by size, because I bet there are some Chihuahuas with some good ideas.

- Jack Handey

ADVERTISEMENT

Sponsors