Setting the course

Every new project starts with a need. Whether it is a higher productivity, increased competitiveness or improved public service, project managers must understand what a project aims to achieve. Requirements analysis does just that. This article begins by explaining the requirements analysis process, noting that this is where project managers break down stakeholder requests, examine the timeline and budget and then identify any incompatibilities. It then looks at the first step in requirements analysis: deciding which tack to take. It then suggests ways to choose the right approach for a given project, specifically noting how to handle agile, systems engineering, lean, and value engineering approaches. The article describes a challenge project teams face when conducting requirements analysis, which is bridging the gap between technical requirements and project goals. It then notes how leveraging a few useful tools can help streamline conversations based on stakeholder analysis, visualizing, and unified modelin
registered user content locked

Log in or join PMI to gain access

or Account Registration

Advertisement

Advertisement

Related Content

Advertisement

Publishing or acceptance of an advertisement is neither a guarantee nor endorsement of the advertiser's product or service. View advertising policy.