• Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off
Reading...
Front

Card Range To Study

through

image

Play button

image

Play button

image

Progress

1/13

Click to flip

Use LEFT and RIGHT arrow keys to navigate between flashcards;

Use UP and DOWN arrow keys to flip the card;

H to show hint;

A reads text to speech;

13 Cards in this Set

  • Front
  • Back
Using a detailed example to illustrate your answer, describe what a Work Breakdown Structure (WBS) is and how you would use it to manage scope in an IT project. (1)
- The Work Breakdown Structure, is a tool project managers use to break projects down into manageable pieces.




Using a detailed example to illustrate your answer, describe what a Work Breakdown Structure (WBS) is and how you would use it to manage scope in an IT project. (2)
- Most project professionals recognise the importance and benefits of a WBS in outperforming projects without one.
Using a detailed example to illustrate your answer, describe what a Work Breakdown Structure (WBS) is and how you would use it to manage scope in an IT project. (3)
- A WBS is a hierarchical decomposition of deliverables needed to complete a project. It breaks the deliverables down into manageable work packages that can be scheduled, costed and have resources assigned to them.
Using a detailed example to illustrate your answer, describe what a Work Breakdown Structure (WBS) is and how you would use it to manage scope in an IT project. (4)
- A WBS is deliverables based; meaning the product or service the customer will get when the project is finished.
WBS Example
Now we switch to software project management, where you startup a computer animation company. To be the first to get your computer game on the market, you could assign teams to the different aspects of writing, drawing and building animated computer games, as shown in diagram E-2 below.



Perhaps your key programmer is also a pretty good artist. Rather than have him divide his time and energy by trying to do both tasks, you will realize faster results if the programmer concentrates on programming while his cousin Jenny draws the scenery.

WBS Benefits
Provides a solid foundation for planning and scheduling. Breaks down projects into manageable work packages. Provides a way to estimate project costs accurately. Makes sure no important deliverables are forgotten. Helps project managers with resource allocation. Provides a proven and repeatable approach to planning projects. Provides an ideal tool for team brainstorming and for promoting team cohesion.
Granular Scoping
- The budget should be allocated to each resource at a task level.

- Ensure hours are broken down into as much detail as much as possible. This will allow you to subsequently assign and manage project hours in smaller steps, which will inherently provide you with greater control and transparency.




- Greater visibility regarding project task length.




- This information will be invaluable to you as you estimate future projects with similar tasks.

Time Management (1)
There is no chance a project manager will have success in measuring project profitability with any comprehension if each resource isn't recording hours spent on specific projects.
Time Management (2)
Ideally, resources will log how much time is used on each project task (back to granularity), so that you will understand exactly what areas of the project are most time consuming.
Time Management (3)
This information will allow you to compare estimates against actuals, refining your scoping methodology by making corrections moving forward.
Milestones (1)
Reconciliation (Milestones) is an exercise during which you analyse project completion (how much work has been done) in comparison to work effort (how may hours have been used).
Milestones (2)
If you have broken down the scope and hour allocations in a detailed way, and hours are being recorded by each project resource, you will be able to reconcile at key points in the project to identify if you are over or under budget before the project is completed.
Milestones (3)
If you know you are over budget early on, you may be able to take action and correct this trend before it's too late to make a difference. Project reconciliations also present an opportunity for you to share accurate information related to scope and budget with your client.