Every IT project is executed with set of deliverables and has an expected closure time. Within this closure period, there is a predetermined set of tasks and activities to complete the project successfully. These tasks constitute the scope of a project. Since a project schedule is closely tied to the delivery time line and the scope, a little variation in the scope can affect delivery and in turn affect the success of the project. When people talk about scope, they immediately think time and cost. Time and cost are outputs of scope. Determining scope is a different exercise. In this thesis the definition of a scope is about developing a common understanding as to what is included in, or excluded from, a project. This means that defining the scope is not the same as deciding how long it will take, or how much it will cost. That comes after the scope is defined.The statements above are shown to be true based on the research that is done in this thesis. The thesis looks in details at one case study and one project that are analysed with the use of the APMS method and in one case the tool.