Are you looking for answers?

Sorry for the late posting. I was distracted by visitors, and the Eurostar Da Vinci Code Quest.
Thursday was Scope Management. I presented my presentation to the Project Management Specialist Group of British Computer Society. It went well. They gave me a souvenir paperweight and a glass wine afterwards. It was a fair exchange. The discussion was interesting and the questions were excellent. My favorite question was about user involvement in requirements gathering and the various approaches.
It is difficult to give an exact answer. It all depends on who you are working with. Two options have proven to be most effective for me.
Each user should be interviewed separately, and then you can compile their comments. To determine if there are divergent requirements, you should carefully read them. To ensure that both parties understand the project’s goals, you will need to bring them together in divergent cases. Users are notoriously difficult to understand, so it is important to help them and guide them. My first version of the scope was to improve it. If you find nothing wrong, circulate it using appropriate version control and wait for the flood of feedback. It would surprise me if there was only a small amount of feedback. This is how you gather requirements.
Interview multiple users. This allows you to benefit both from blue skies thinking as well as the opportunity to share ideas with other participants. However, the quality and quantity you get from the group will depend on how you manage the relationships. It is possible for team leaders to make it difficult for members to voice their opinions and comment. If someone is vocal, it may make it difficult for others to comment without heavy-handed facilitation.

Projects can be difficult because it is not easy to find the answers to any question. This includes what is within scope and what the requirements really are. It all depends on the people involved and the environment they are working in. PM is not a technical discipline. It’s a people discipline. If you don’t have a clear understanding or set of requirements, it’s difficult to communicate with end users, key stakeholders, and the project team. It will be difficult to deliver anything worthwhile. No matter how skilled you are in managing a MS Project and a risk register, your project will fail.