Project Scope Mangement

Alternative name( Project Requirement Management)


Project requirement management can be descried as a process in which the customer explains their visions or the map of their projects to the project manager. Furthermore, the project has to [[#|access]] if the [[#|business case]] is viable or not. On the other hand, project requirement management is a process of capturing, analysing the stakeholders stories for justification and modification before project progression (APM, 2006).
This entails that project requirement is key in every project life cycle because initially customers does not really have a good idea on how to manage their requirements. The [[#|project manager]] may not be engaged from the starting of the project. However, the project manager have to manage every project requirement effectively to ensure that projects scope is effectively plan, define, control, crate effective work breakdown structure and manage variations(PMBOK,2008). Nevertheless, in agile project management user stories are used to capture project requirements throughout the project management life cycle. User stories are short and always informal. Therefore, customers objectives needs to be developed by the project team throughout the project life cycle and the user stories encourages verbal communication

Agile values

Agile values relevant to project requirement management include manifesto, XP, and scrum value. Project requirement management have to deal with effective communication with the customer and the project team to ensure that the user stories are effectively communicated within the stakeholders which is been address in XP and scrum value (Augustin and Woodock,2003). User stories make project management requirement unambiguous as a result of its ability to capture customer’s expectation(West and Grant, 2010).
At the same time, user stories keeps project requirement management simple in order to meet customers need and enables refactoring throughout the process. However, in agile building user stories requires courage because managing customer requirement as shown in the picture is not realist; but the user stories enables the customer to express their expectation continually. Finally, feedback is necessary because the customer, developer, integrator and scrum master uses the user stories to integrate the customer requirement throughout the project life cycle. Therefore, communication and feedback is the most important in managing project requirement management in agile value.

Agile principles

Agile principle identify include incremental change, humanity, quality and learning from failure. Incremental change enables effective implementation of feedback to ensure that customers’ expectations are met (Augustin and Woodock,2003). This indicates that an agile principle enables project requirement management to be driven by customers’ requirements to ensure that their needs are met. However, incremental change may be suitable for information technology projects and small business. Agile principles relies on its team to ensure success of the project, in terms of requirement management the project team and the stakeholders respects perspective of humanity because individuals have different perception about decision in requirement management (Beck,2005).
This entails that effective leadership is required in project requirement management. Thirdly, quality in requirement management is highly required it enables the project stakeholders to manage quality of their requirements by eliminating constraints and improving process efficiency. In addition, refactoring the user stories throughout the project life cycle will improve the efficiency and quality of the project. Finally, learning from failure in agile principle will enable effective project requirement management. For example, the chaos report will enable the project stakeholders to identify area of improvement in agile principle.

Agile practices

Agile practices which are applicable to project management requirement include XP, ASD, refactoring and scrum. User stories capture project requirement management throughout the project life cycle. This means that requirements in agile uses user stories to capture, analyse, test and manage customers aim throughout a project life cycle and this is what XP and scrum does(Augustin and Woodock,2003). In addition, user stories are being steered not control because of high expected changes in projects . However, continuous integration enables modification of requirements management continuously because customers’ needs and wants are not always initial, but, user stories integration enables the project team to capture and effectively analyse customer’s objective daily in order to ensure effective deliverables. Nevertheless, refactoring enhance implementation of feedback to meet customers expectation. This entails that the project requirements will be continuously reviewed in order to edit and manage requirements effectively. In addition, the editing will improve quality of the project throughout a project life cycle. Finally, customer on site enables project requirement management more effective because when the user is involve it is more easier to capture and analyse the customers’ needs and wants effectively because they are involved throughout the project. In addition, changes can be monitor and control effective by the project stakeholders.


Project requirement management in traditional approach does not involve the customer throughout the project life cycle which makes changes difficult while in agile it has be establish that changes must occur. However, projects are strictly driven by business case or objective in order to improve quality management in projects and services .In addition, quality management is totally dependent on the customer. This entails that the customer should be part of project from the initial stage to the commissioning stage of the project; although in traditional approach customer are partially involved. On the other hand, in agile requirement management uses user stories throughout the project life cycle and changes is strictly anchored on the customers expectation. This explains that customer is engaged throughout the project life cycle. Furthermore, as change is expected in every project agile has the ability to adapt to change and ensure that project requirements are fully capture, planned and process throughout the project life cycle. For example, in traditional approach organisational structure can be a Barrie to continue integration and incremental change in requirement management while in agile user involvement will help to increase quality of products and services because the user is involve throughout the project life cycle. Nevertheless, project requirement management is suitable for innovation projects and information system project because of its user involvement and incremental change control. In contrast, agile in project requirement management will not be suitable for mega construction project because its continuous integration and incremental change in requirement will lead to time and budget overrun. Therefore, project requirement management in agile uses user stories to manage, control, and plan and monitor customers requirement.

Links from this KA to other KAs

The knowledge area that is related to project requirement management includes project communication, collaboration, team, stakeholders’ management and user involvement. Project requirement needs effective communication with user for refactoring, incremental and continues user involvement in order to achieve the customer’s wants or need. In addition, without the teams collaborating effectively requirement in projects will be difficult to communicate to other stakeholder involve in the project. Agile has iterations and planning is strictly focused on the user stories in order to capture, analyse and test the customer’s requirements via user stories to ensure that the customer objectives are met. Therefore, this explanation justifies how communication, team, stakeholders management and user involvement is related.


Association for Project Management (2006):APM Body of Knowledge. 5th ed. APM publishing,High Wycombe
Augustine,S., and Woodock,S. (2003) Agile Project Management, CCPACE
Beck K.(2005) Extreme
Programming Explained: Embrace Change, 2nd edition, Addison Wesley
Davis,A.M., Hickey,A.M and Zweig,A.S . Requirement Management in a project Management Content

External links

<List relevant external pages, For example: Wikipedia entry on this KA entry on this KA>

Read in another language

<If available, include links to pages with translations to other languages>

Chinese Translations


同时,用户故事使项目需求管理简单的为了满足顾客需要,使重构整个过程。然而,在敏捷构建用户故事需要勇气,因为管理客户要求见图片不是现实主义者,但是用户故事使客户能表达他们的期望不断。最后,反馈是必要的,因为客户,开发人员,积分器和scrum master使用用户故事集成客户需求在整个项目生命周期。因此,沟通和反馈中最重要的是管理项目需求管理在敏捷值。