Information Systems Project Management
Unit 3 Assignment 1
Professor Chad McAllister
February 16, 2013
1. Explain project scope management in terms of its processes.
Scope management is the process of defining and controlling the work that is or is not included in the project (Schwalbe, 2012). This outlines to the team and stakeholders the product that will be produced and the processes that will be used to produce that product. The project scope management consists of five processes:
* Collect requirements- This process defines the specific details of a product’s functions and features. Defining the processes for creating the products is ...view middle of the document...
Changes to the project scope should be carefully considered. This process results in a change request, work performance measurements, updates to organizational process assets, the project management plan and project documents (Schwalbe, 2011).
2. Compare and contrast the five approaches for creating work breakdown structures.
The five approaches to developing the work breakdown structure:
* Using guidelines-
* Analogy approach-
* Top-down approach-
* Bottom-up approach-
* Mind-mapping approach-
The first approach for developing the WBS is using guidelines. Most organizations develop their own guidelines for developing the WBS. It is important to check with the organization to see if they have a preferred set of guidelines, templates or examples. In addition, Microsoft Project Professional has many built in templates including templates for developing the WBS.
The second approach for developing the WBS is the analogy approach. This approach uses a WBS from a similar past project as a starting point for developing the WBS. It is important for the project manager to check with the organization if they have a repository of WBS’s on file from similar past projects to help them in the development of the WBS.
The third approach for developing a WBS is the top-down approach. This approach takes the large items of the project and decomposes them into their subordinate items; this is considered the conventional approach for developing the WBS by many project managers (Schwalbe, 2011). This process refines the tasks into specific details or work packages.
The fourth approach is the bottom-up approach. This approach is popularly used to develop new systems. The bottom-up approach requires team members to define as many tasks related to the project as possible. Then these tasks are aggregated and organized in summary level tasks or higher level tasks on the WBS. This could be done in a brainstorming session (Schwalbe, 2011).
The last approach to developing a WBS is mind mapping. Mind mapping allows members of the project team, to record their ideas in a non-linear fashion when developing the WBS. In this concept, the main idea is written in the middle and the ideas that are developed are depicted branched out from it. This is more of a visual documentation technique. A brainstorming session type of meeting might be used to develop a mind map of the WBS. This brainstorming sessions should involve a variety of team members that come from a variety of job roles and responsibilities. This will be helpful with defining the tasks that are located on the WBS because these tasks will more than likely be perform by team members from a variety of job responsibilities.
3. Explain project time management in terms of its processes.
Project time completion is the tasks and processes that are required to complete a project in a timely fashion (Schwalbe, 2011). There are six processes involved in project time management....