I often see that regulatory requirements define the project objectives, its not other way around. So would like your views on the same Saving Changes...
It really depends on what the purpose of the project is. Some projects are launched to meet regulatory compliance needs in which case those requirements would be the primary ones whereas in other projects a different driver such as market share or revenue by researching, developing and successfully launching a new drug might have functional requirements with regulatory requirements being part of the quality obligations.
This is also affected by the culture of the company and the perspective of the project's key stakeholders as to what is most important to them.
Kiron Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
We are creating solutions, where solution is "the thing" to be created plus "the way" to create it. You can call them product and project. Product requirements define project requirements. That´s all you have to take into account as an answer for your question. Usually, business analyst works with focus on product while project manager works with focus in project. Quality is part of the non-functional requirements of the product. Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Raghavendra, in most cases, regulatory requirements act as a constraint to projects and they should comply with them be it building codes, governmental or environmental regulations and others. Saving Changes...
Community Champion
