Tutorial IT project management by Leong Chi Lin https://padlet.com/i22022059/uhz211t4b1k7qg9 en-us 2022-03-09 04:11:04 UTC 2025-10-29 13:17:11 UTC hello@padlet.com Q1 List and briefly describe the six main processes involved in project scope management https://padlet.com/i22022059/uhz211t4b1k7qg9/wish/2085334223 Planning scope: determining how the project's scope
and requirements will be managed.

Collecting requirements: defining and documenting the features and functions of the products produced during the project as well as the processes used for creating them.

Defining scope: reviewing the project charter, requirements documents, and organisational process assets to create a scope statement.

Creating the WBS: subdividing the major project deliverables into smaller, more manageable components.

Validating scope: formalising acceptance of the project deliverables.

Controlling scope: controlling changes to project scope throughout the life of the project.]]> 2022-03-09 04:16:47 UTC https://padlet.com/i22022059/uhz211t4b1k7qg9/wish/2085334223 Q2 List and briefly describe five approaches for creating work breakdown structures i21020056 https://padlet.com/i22022059/uhz211t4b1k7qg9/wish/2085337345 Guidelines
The guidelines approach for developing a WBS is important because some organizations have prescribed the form and content for WBS for particular projects. Therefore, project managers and their teams are responsible for reviewing appropriate information to develop their unique project WBS based on the standard provided by the Project Management Institute.

Analogy approach
In this approach, the project teams use a similar project’s WBS as a starting point. By reviewing the example of other similar projects’ WBS, they can tailor it to their own project. For example, when the team has worked on a similar kind of project, it will be easy for them to develop the WBS based on past experience.

Top-down approach
The top-down approach is the third method of developing a WBS. A top-down approach is to start with the largest part of the project, and then break them down into more manageable structures. This method breaks down larger tasks or modules in the project and adds more and more details.

Bottom-up Approach
The next approach is the bottom-up approach. The bottom-up approach is to start with the team members. The team members determine and list all the specific tasks and activities related to the project. It is very direct, it can be put into a group, and it's easy to do. Bottom-up technology is an ideal way to solve problems with brainstorming.

Mind mapping technique
The last technique for developing a work breakdown structure is mind mapping. This is a very useful technique for the project manager. Mind map describes the brainstorming process of creating a branch structure to describe ideas and opinions related to the project. In this method, we need to write the task into a nonlinear branch format, and then create the WBS structure. Once the mind map is completed, it can be used to develop a top-down or bottom-up WBS method. 

]]> 2022-03-09 04:19:28 UTC https://padlet.com/i22022059/uhz211t4b1k7qg9/wish/2085337345 Q3 What are some of the suggestions for improving the requirements process? fnrwibowo https://padlet.com/i22022059/uhz211t4b1k7qg9/wish/2085343858 1.  Allocate a couple of team members to specifically handle requests that change the requirements of the project. 

2. Develop a process to efficiently review the requested changes of the requirements and ensure that the changes requested already include the changes in costs and schedule.
 
3. Stick to the deadlines of the project. 

4. Thoroughly understand user requirements by having 
prototypes, case modeling, and Joint Application Design to further confirm with the client if that is what they wanted for the finished product of the project.

5. List of requirements should always be kept available and ensure there is easy access.
]]> 2022-03-09 04:25:30 UTC https://padlet.com/i22022059/uhz211t4b1k7qg9/wish/2085343858