I wanted to ask this question regarding scope management,the question is
In a project where the product is not clearly defined, what would be the best or adequate techniques to define the requirements?
Thanks Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
No matter the product is well defined or not you always will have a deviation, an inherent error in your estimation. That´s was fully demostrated for Barry Bohem when created the "Cone of Uncertainty" thing that has been taken as a reference for lot of disciplines. On the other side remember that project manager is accountable for project requirements, not for product requirements but project requirements must be defined from product requirements. With that said, what you stated is one of the things to take into account to select the approach, life cycle and life cycle modificators. I will take an example to desmitify some things outside there. Here comes. I was part of the group that created the web browser that today is almost a "de facto standard" in PCs and Movil Phones. We used a waterfall based life cycle with incremental delivery and prototype as the modificator. Sequential is most of the times confused with Waterfall. Waterfall has retroalimentation into it. Prototypes (take into account there are two main types: through away and incremental) could help you to clarify and taken requirements puting the prototype in hands of the final users for example. Saving Changes...
Thank you Sergio, i had the same thoughts regarding the prototype, your contribution is very welcomed and appreciated, buen apunte.
...
1 reply by Sergio Luis Conte
May 18, 2020 10:54 AM
Sergio Luis Conte
...
You are welcome.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
May 18, 2020 10:09 AM
Replying to Majed Afifi
...
Thank you Sergio, i had the same thoughts regarding the prototype, your contribution is very welcomed and appreciated, buen apunte.
You are welcome. Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Majed,
agree with what Sergio said.
The key point is that the scope of the product (and the project) is only certain after the project has ended. We always work in uncertainty, albeit at different levels, so different ways to create certainty are needed and exist. A good project manager can chose a good way, so he/she must have knowledge of many methods.
PMBoK calls this progressive elaboration of artifacts.
...
1 reply by Varun Jayaraman
Mar 21, 2025 6:14 PM
Varun Jayaraman
...
I can resonate with the point you raised around certainty of scope after project closure. If we are building a solution to a business problem, the stakeholders start off with an idea (expectation or notions) of what the solution should and shouldn't do. PM will have to find ways to get feedback on solution under development through different methods (iteratively or incrementally).
And building on Thomas's feedback, if you are in a position where frequent, incremental delivery of the scope of the project is possible to progressively gain benefits while at the same time getting a better understanding of the scope, then you are edging towards an adaptive or agile life cycle.
The key point is that the scope of the product (and the project) is only certain after the project has ended. We always work in uncertainty, albeit at different levels, so different ways to create certainty are needed and exist. A good project manager can chose a good way, so he/she must have knowledge of many methods.
PMBoK calls this progressive elaboration of artifacts.
I can resonate with the point you raised around certainty of scope after project closure. If we are building a solution to a business problem, the stakeholders start off with an idea (expectation or notions) of what the solution should and shouldn't do. PM will have to find ways to get feedback on solution under development through different methods (iteratively or incrementally). Saving Changes...
