Adilson PizeCEO and Consultant| Excellence ConsultantsCaxias Do Sul, Rs, Brazil
Gather all requirements to the project (or at least those most significants) is one of most hard challenges to the project team.
As the requirements are the base to define the project scope, an error when gather them can mean an unsuccessfull project.
There are several techniques to requirements gathering but, normally, the technical skills alone are not suficient, because the team responsible by collect the requirements need work together other people, so soft skills are necessary as well.
In your experience, which are the most important challenges to be surpassed, and how we can do it?
Alessandro MidiriProject/Programme/Portfolio Management, PMP®| Italian Company
From my experience the most important challenge (in terms of priority) can be discovered during the planning process (before the formal Kick Off). It's related also to the contractual context & PLC (and to many other factors as reported in the previous comments). A good stakeholders management is a key factor. In other terms the gathering requirements activity must be consistent & in time (as highlighted by Al Taylor) to be adherent to the (time,cost,quality) main project goals (see also the Business Case). Saving Changes...
Suresh MKConsultant - Transformation| FreelancingBangalore, Karnataka, India
Articulating the requirements clearly is key Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
First, to understand that you have two types of requirements: product requirements (in charge of the business analyst) and project requirements (in charge of the project manager). Most of the project requirements are defined from product requirements. Second, unless the bussines analyst give to you the requirements, if you have to get them from the project stakeholdres, then take into account that you never get requirements. You ever get needs/wants/desires/wishes, etc that you have to convert into requirements after analysis. Saving Changes...
I agree with the above comments about stakeholder identification and analysis before the start of requirement gathering process. This helps the team understand the stakeholder influence and importance to come-up with suitable requirement gathering strategy and process.
During the requirement gathering process, the team should not provide any kind of commitment to the particular stakeholder the requirement will be made part of the scope baseline. Because, which requirement can be part of the scope is decided during the requirement analysis and prioritization based on project objectives and not during the requirement gathering process. Saving Changes...
