Quality Assurance and Project Management

Feb 29 2016   12:22PM GMT

Business Requirement To Evolve During Product Development

Jaideep Khanduja Jaideep Khanduja Profile: Jaideep Khanduja

Tags:
business requirements
product development

Gone are the times when the business requirement was finalized in the first phase of a project.

The requirement now evolves during the product development.

Gone are the times when the business requirement was finalized in the first phase of a project. The business requirement now evolves during the product development. The earlier project management phases have gone obsolete in terms of freezing the requirements right in the beginning. The requirements evolve as the project progresses. It is no more the ball game limited to project initiation phase. The current phenomenon is to run a project in smaller slots. Build your timelines accordingly. Adhere to timelines and conduct daily or maybe hourly backlog status update meeting. Backlogs are now not entertained in a good way. Backlogs, when created, have to be addressed in a shorter life span. The longer life span of a backlog could have an overall negative impact on the project’s growth.

Business Requirement To Evolve During Product Development

Photo credit: NathanaelBC via VisualHunt / CC BY-NC-ND

The definition of the project manager is also changing. A project manager has to be stronger in product knowledge. Merely a strength in project management with insufficient knowledge of the product or service will not suffice the purpose. That is where the product managers are replacing project managers in a big way, on a global scale. Disruptions in business, economy and customer behavior are the major keyholders in any product development. That is why business or product requirement is bound to change as the project progresses. You can’t rely on a single sign-off from your customer at the end of a project for project closure. There have to be multiple sign-offs.

Business Requirement To Evolve During Product Development

Photo via VisualHunt

Capture requirements in smaller chunks. Build those chunks and handover to the customer for testing once internal processes of development and testing are done. Get customer sign-off for each chunk built. Each build successfully signed-off will create a better success story leading to a timely closure of the project.

 Comment on this Post

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

Share this item with your network: