Scope Management

Knowledge Area	Initiating	Planning	Executing	Monitoring & Controlling	Closing
Scope Management		Plan Scope management, Collect Requirements, Define Scope, Create WBS		Validate Scope Control Scope

Types of Requirements High level representation is shown in below figures. Details are available here.

Creating Work Breakdown Structure (WBS)

Project WBS can be viewed as break down of the milestones to be accomplished into tasks and sub tasks. Another way is to link the WBS to requirements. For example, requirements are represented as Epics and cascaded User Stories. The lowest level user stories are taken up for implementation. The tasks required for a user story to be implemented can be created under the User Story. This way there is traceability of the tasks all the way upto the Epics.

Few approaches to WBS creation are: Analogy Approach, Top Down Approach, Bottom Up Approach and Mind Mapping Approach. Depending on the context one or more of these approaches can be used.

WBS Dictionary is essential for consistent usage and interpretation of the WBS items across the project and stakeholders.

Implicit vs Explicit Requirements

While the documented requirements are the primary reference for any discussion, there are certain implicit requirements which are not documented. These implicit requirements depend on the nature of the product, geography where it is used and such attributes. Hence, while requirements are as detailed as possible – including the implicit ones – the development and testing teams should keep the implicit requirements in mind.

Scenarios for Discussion

1. In an IT project executed using Fixed Pricing, the scope is signed off with the client. If the client comes up with a new requirement (or) a modification of the existing requirement, how can the project manager handle this?
2. Assume that a team is working on the software for a mobile phone to be used in Japan. How can the team take care of customer expectations with respect to the features of the phone – especially the implicit requirements?

References:

Information Technology Project Management, 4ed, ISV, Jack T. Marchewka, ISBN: 9788126543946.

Schwalbe, K. (2016). Information technology project management. Cengage Learning.