In some cases from personal experiences in managing IT projects (Website, software development ), there's always this big problem during Collect Requirement Process.
This problem usually comes mostly when the project owner, Customer or Sponsor or clients do have little or no knowledge of the area or latest and best practice in the IT sector.
I have situations where the requirements as described by the customer or client seems outdated and if the product is to be made to match such, will be an bsolute joke as it wouldn't serve the right purppse and the client do not know these.
As we know that project must always meet the stakeholders requirements, whats will be the best approach in this circumstance to go about producing the best product that meets the best practice and functionallity taking into consideration the poor requirement description from the project owner, sponsor, or customer, which is different from wjat the best option would be if i was to produce the best product from my knowledge base? Saving Changes...
Definitely, you should consider the customer's needs. The needs may be either explicit/implicit or stated/implied. You need to consider both. On the other hand, gold plating is forbidden. You should not add non-required features or deliverables. Saving Changes...
Eric SimmsSenior Program ManagerBaltimore, Maryland, United States
Who is collecting requirements during the Collect Requirement Process? Is a Business Analyst working with the Customer to produce requirements? Or are the Customers just handing you a set of requirements they created themselves? It sounds like the latter is happening, in which case you'd be better off sitting with the customers and gathering their requirements yourself. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Project manager is not accountable for product requirements. Project manager is accountable for project requirements. Business analyst is accountable for product requirements. Indeed, from product requirements the project requirements are defined. Saving Changes...
Customers are rarely able to articulate their needs in the exact manner to help a team meet those needs. That's why business analysis as a competency is critical regardless of the role or title that is responsible for this practice on a given project. Saving Changes...
Ekemini,
As others have stated the business analyst job role has primary responsibility. Other organizations may use the system architect job role, or the systems engineering technical discipline for this.
Whatever they are called, "requirements validation" is a necessary activity to ensure that the requirements are correct, complete, and valid. This is not to be confused with "requirements verification" which is ensuring the requirements are met.
If nobody is going through the process of ensuring that you have the right requirements and they are stated in a way that is executable, then your project is a case-study in how projects fail, waiting to happen.
Loop in Business Analyst who will help to articulate the requirements and act as a bridge between you and customer. This is very common in any IT project and hnadle it carefully else later on it will trun into a big issue. You may face difficulty in getting UAT or Sign offs. Hope it helps Saving Changes...
