Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
In a predictive development approach is there any time when the project manager no longer collects requirements?
If so, what is this moment? Saving Changes...
The requirement will evolve in the course of the project. In a large complex project, it is not possible to define everything at the start. So precision would keep on coming.
It should not change the scope of the project and not be confused with a change request. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
There is something critical to understand: project manager is accountable for project requirements, not for product requirements. It is important taking into account that from product requirements project requirements are defined. On the other side, you do not collect requirements. You elicit needs/wants/desiers/etc that you or somebody must translate into requirements or, if you prefer, into well formed requirements. Finally, Barry Bohem´s Cone of Uncertainty will help to understand the problematic about requirements which in escence are data that somebody has to transform into information. Saving Changes...
George FreemanThought Leader | Author | Architect| Florida, United States
In practicality, there is no true predictive development environment unless you outlaw the concept of monitoring and controlling scope. We use the term predictive, but in reality, we are stating that reasonable due-diligence has been done defining our scope, but in truth, we believe we are 80% or 90% there (politically stated higher based on information known at the time).
Predictive is a mindset as agile is one, in enterprises, it would be rare to have truth on either pole; instead, we are somewhere in-between. We have no choice but to build projects within the constraints of political acceptance; otherwise, we would be unemployed. So, whether our scale is tilted towards predictive or adaptive we accept change as an absolute and manage it the best we can via process.
To answer the question: A change request once accepted becomes a functional requirement, therefore whether it’s called a requirement or a change, we “continuously collect,” but that doesn’t mean that we “continuously accept.” Saving Changes...
