Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
It depends on the methodology. Either way the best way direct interaction with the client. and if possible with the end users. It doesn't matter if it's called workshop or backlog creation and who does it.
In terms of tools it looks like the best one remain pen and paper. Saving Changes...
Collins AlugaQuantity Surveyor| MCK Contract Services LtdNairobi, Nairobi, Kenya
I think it will depend on the nature of the project and type of participants.You therefore have to evaluate and decide as a project manager which tools/techniques will work for you better.For instance, in a project with various project team members of distinct professions such as complex construction/infrastructure projects,expert judgement based on previous experiences may just be the best Saving Changes...
By now you should have learned through these discussion posts that there is no such thing as a best tool, technique or practice for ANYTHING in project management.
It always depends on the context of the project and the EEFs affecting it.
Kiron
...
1 reply by SHADAV MOHAMMAD ANSARI
Mar 20, 2019 12:10 AM
SHADAV MOHAMMAD ANSARI
...
Noted with thanks.
Saving Changes...
Joshua RenderProduct Owner| CognizantHarrisville, Ny, United States
For projects I usually work on, as much as I can I try to work with SME's and ask them to get details. Usually though, by the time I am going to the SME's I already have a bunch of generic requirements from managers and I need the SME's to help me fill in the details. Then the SME's learn what the managers want to do and hopefully, they agree. Saving Changes...
Once again, as Kiron mentioned, there is not any best tool or technique. Lots of factors such as the nature of the project, organizational culture, cost, etc. should be considered.
...
1 reply by SHADAV MOHAMMAD ANSARI
Mar 20, 2019 12:06 AM
SHADAV MOHAMMAD ANSARI
...
Noted with thanks. Yes you are right there are lots of factor in it.
The next generation employing MBSE will be a significant improvement over federated list based tools. Linking rather than copying requirements is far more efficient for things like identifying all the places a requirements change will affect, and global requirement changes throughout a project/product. Saving Changes...
I used IBMs rational DOORs tools once and thought it was very good at linking and tracking requirements. When it comes to gathering requirements, the end user and their needs and expectations are often overlooked or even ignored by those that are supposedly more knowledgeable and experienced. I've seen lots of military equipment delivered to soldiers who were never consulted, and ultimately had to "make do".
Just my thoughts. Not sure if it helps.
Gather a focus group that comprises subject matter experts to discuss interactively on the requirements and relate to the expectations.
Utilize an affinity diagram to sort requirements generated from the focus group's discussion, based on their relationships for further evaluation. Saving Changes...
