05. Project Scope Statement

Project scope management includes the processes involved in defining and controlling what is or is not included in a project. The are five main processes involved in project scope management. (referring to the table on chapter 04.)
1. Scope planning - the main output of the scope planning is the scope management plan which is a document that includes the necessary information for the team will create the project scope statement, how to create a WBS (work breakdown structure), control the deliverables and than control the closing process. As a key output of scope management plan includes a project charter which describes the high level goals for the project. It contains a title, project start and finished date as estimated, project managers information and contact, project objectives and so on until the comments about the project.
2. Project definition - the main output of project definition is creating a project scope statement. It comes after the preliminary scope statement and provides more details about the project scope. After it has been finished, than a work breakdown structure (WBS) is created.
3. Work Breakdown structure (WBS) - is a deliverable oriented grouping of the work involved in a project that defines the total scope project. An example of a WBS is given in the picture. In the WBS the project deliverables are subdivided into smaller pieces, process this known as "decomposition". WBS should be accompanied with a WBS disctionary which is a document that includes description and detailed information about each WBS item. In a WBS may work many people but the main responsibility is to only one of them.
4.Scope verification - involves the acceptance of the finished scope by the stakeholders. The scope statement should be submitted through a clear documentation to the stakeholders.
5.Scope Control - involves controlling changes to the project scope. Some of the tools used to implement scope control includes; a change control system, performing variance analysis and so on. Variance is the difference between planned and actual performance.

Comments

Post a Comment

Popular posts from this blog

02. The Project Management and Information Technology Context

Image
Project Management can be thought as an approach to describe management and problem solving. It includes three parts: 1. System philosophy - a model of thinking about things as systems, 2. System analysis - a problem solving approach, and 3. System management - addressing issues before making changes to systems. To select if to undertake a project or not, project managers must take into consideration the three sphere model which includes analyzing: business, organization and technology (as shown in the picture). Business is concerned with questions like; what will the project cost to the company? What impact it will have? What is going to be the support cost and so on. The organization sphere concerns about: Who will be affected by the project? Who will train the staff and so on. And lastly, the technology sphere is concerned about the issues like: What devices will be used? What operating system? How the system will be accessed and other questions similar to these. 2.1 UNDERSTANDING T
Read more

10. Project Communications Management

Image
We talked about human resource management on the last part. Of course that if we want to have a good relationship among employees and managers, the most important thing is to have good communication. And so, we come to the other knowledge area that is; Project Communications Management. Strong verbal skills are a key factor in career advancement for IT professionals. Project communication management includes the following processes; Communications Planning: Communications planning means determining the information and communications needs of the stakeholders. Every project should include some type of communications management plan. Communication management plan is a document that guides project communications. A very important document in this process is a stakeholder analysis. it describes the characteristics of the stakeholders which helps project managers on how to deal with them. An example for a stakeholder analysis for project communications is shown in the picture for further
Read more

08. Project Quality Managament

Image
In continuing with the nine knowledge areas, the turn comes for project quality management. It is very important to understand the importance of project quality management for information technology products and services because this will help in giving a better output which means, satisfied customers and stakeholders/sponsors. It is very important to give outputs qualified for IT development teams because it sometimes may lead to fatal errors, like the case were in 1986, two hospital patients died after receiving fatal doses of radiation from a Therac 25 machine after a software problem caused the machine to ignore calibration data. Quality in a project may be defined as "the project’s processes and products meet written specifications or more simple saying: "a product can be used as it was intended" . For a more technical definition, we may refer to the International Organization for Standardization (ISO) which defines quality as “the degree to which a set of inherent
Read more