When the Requirements Collection and Analysis are the Whole Project

  Requirements Management   Work Breakdown Structures (WBS)   Knowledge Shelf  

The management of a project covers all phases, from initiating to closing. Such phases are strictly related and overlap; therefore, all of them are needed and critical for the success of a project. However, sometimes, some phases and knowledge areas are almost the whole project, in the sense that they enclose the key challenges and actual complexity of the whole project life cycle.

This is the case for a new apartment complex project for visually impaired (including blind) people. Indeed, the most relevant issues and aspects of the management are related to the collection and analysis of user requirements, which put stress on the project scope and planning, other than on the different dimensions of the triple constraints and project phases. The management of the quality and communication with the user are also relevant, but for the remainder of the project management, consolidated processes and tools can be used without peculiar criticalities.

In this article, the description of the scope management implementation is presented, with a focus on how requirements are elicited and collected from the main stakeholders (specifically, the customers/users of the project outcome) as well as analyzed and verified. It will be demonstrated that only the effective management of these concurrent processes can lead to project success.

Project managers are increasingly realizing…

Please log in or sign up below to read the rest of the article.