# data[].attributes.attachment_link.readable_text
The Project Team

When you look at the tallest skyscraper in the city, do you ever wonder just how it was actually built? It takes hundreds of people to build walls; install windows, doors, and floors; and run electric and plumbing. So, just how does all of this happen?

For one, a project team is formed. This is a group of people that is put together to perform various tasks related to a project. The teams can be made up of workers who have skills in different functional areas of the project. The project team must meet certain criteria. They must:

Understand the scope of the overall job

Know how to plan for the completion of the project

Perform the work within the desired budget and timeframe, and make sure it's up to the expected quality standards

Report project risks, issues, or concerns to the project manager

Communicate work statuses

And most of all, be a team player

Roles of the Project Team

There are three main conventional roles people in a team can take on. The leader is the member who provides leadership through motivation, feedback, and rewards systems. In other words, it is the person's job to inspire others to work more productively and enjoy what they are doing. The people he leads are called members, and they are the people who are actually working on different tasks and are lower on the hierarchy than the team leader.

Some projects use contributors. These guys are very similar to consultants or experts who provide advice to the team leader and members. They generally have some interest in the project but are not members and do not perform tasks. The members are the ones who actually perform the tasks. Speaking of tasks, let's see what exactly a team member should do.

Member Responsibilities

As a team, it is important that each member not only knows but also adheres to the responsibilities and duties of the team as a whole. For one, each member should have a thorough understanding of the quantity and scope of the work. Following plans is also essential. With so many people doing a variety of tasks, being able to follow the work breakdown is important. We'll get to the work breakdown in a moment. Lastly, the team member must be a model of communication throughout the duration of the project.

Now, even the best leader and team cannot build a skyscraper without a plan. That is where the work breakdown structure comes into play.

Work Breakdown Structure

Now that the team is in place, a work breakdown structure needs to be created. This is like a big chart that breaks down the work into chunks. Once the tasks are broken down, the work breakdown will include specific details for each task. Let's see if we can put this into action.

If we were to build a doghouse, we would need a bunch of things. We'd buy wood, carpeting, shingles, a door, and some paint. Oh, we would also need nails and glue. Our work breakdown would look a bit like this. So, you see Fido's Doghouse project will cost us around $320.00, and if every task is completed, that represents 100% of the work needed to build a penthouse for the pooch. I know what you are thinking. Why use a work breakdown structure? If everyone is skilled and has a copy of the blueprints, it seems pretty easy to just build a doghouse.

Organizing Tasks and Time

Not so fast. Let's go back to Fido's new place. We know we had around $320.00 to build the house, but if everyone was grabbing at the money, there may not be enough for everything. So, by allocating a specific amount of money for each of the different tasks, we were able to keep the project within the desired budget.

Next, we had to think about how long each of the tasks would take so that we not only stay on budget but also finish Fido's digs on time. For that, we gave a percentage of time that each task should take, equaling 100%. That's another way to stay on track. By allocating how much time for each task, we can keep a careful eye on whether one task is taking longer. Then, adjustments can be made along the way.

The Responsibility Assignment Matrix (RACI)

Now, our example above was done using a template. However, if you want to get even fancier, you can use a Responsibility Assignment Matrix (RAM) to get the job done. Literally. The Responsibility Assignment Matrix, also known as RACI, is similar to our work breakdown but it is a bit more complex. RACI stands for Responsible, Accountable, Consulted, Informed. Let's break it down.

# data[].attributes.attachment_link.keywords[]
the project team and work breakdown structure - video & lesson transcript | study.com

# data[].attributes.attachment_link.title
The Project Team and Work Breakdown Structure - Video & Lesson Transcript | Study.com

# data[].attributes.attachment_link.description
When you look at the tallest skyscraper in the city, do you ever wonder just how it was actually built? It takes hundreds of people to build walls; install windows, doors, and floors; and run electric and plumbing. So, just how does all of this happen? For one, a project team is formed.

# data[].attributes.attachment_link.readable_text
Project Management Planning

Meet Adam. Adam just got promoted to project team manager at his job working for ABC Corporation. Shortly before the project was to begin, the project manager quit, leaving ABC Corporation to find a new individual to oversee the project. It was at that time that they decided to appoint Adam as the new project manager.

Feeling overwhelmed about his new position, Adam decided to research the various steps to take a project from start to finish. He also brushed up his knowledge about the resources that would be beneficial in helping to manage the project. What Adam was essentially learning, is the process and tools often used with project management planning.

Basic Definitions

Let's take a moment to provide a foundation of terms to better understand the process and tools of project management planning. First, there's project management, which is the process of completing a project from start to finish. A project manager is the individual assigned to oversee the process.

So, the process of project management planning is a combination of steps to complete a project. In other words, it's a list of steps that project managers go through so that the project can be completed successfully. The tools are the resources the project manager can use to aid them in the process. As the lesson continues, we'll learn more specifically what those tools are.

The Planning Process

The following steps are often taken by project managers when completing projects:

Step 1: Identify a Project

Before a project can even begin, a company needs to decide what the project will be. This means knowing what the company needs and what projects can be done that will benefit the company. For example, in order to be an effective project manager, Adam needs to decide what project will be completed and why that project is important to the goals of the company.

Step 2: Determine the Details

Once a project has been established, the next step is defining the key details. Ultimately, this is the step in deciding who will be working on the project, what their responsibilities will be, the timeline of those responsibilities, the resources that will be used, and the budget. So, this is the step when Adam will meet the members working on the project. He'll then assign each of them a task. For example, Maria, the company's graphic designer, might be responsible for designing all of the graphics for the project. Adam will also need to pick a time when the project will be completed, how many hours will be allocated to the project, and how much money ABC Corporation will allocate to the project.

Step 3: Start the Project

When all of the details and planning have been completed, the project will then begin. So, once Adam has planned all of the details for the project, it's time to actually begin working on it.

# data[].attributes.attachment_link.keywords[]
project management planning: process & tools - video & lesson transcript | study.com

# data[].attributes.attachment_link.title
Project Management Planning: Process & Tools - Video & Lesson Transcript | Study.com

# data[].attributes.attachment_link.description
Meet Adam. Adam just got promoted to project team manager at his job working for ABC Corporation. Shortly before the project was to begin, the project manager quit, leaving ABC Corporation to find a new individual to oversee the project. It was at that time that they decided to appoint Adam as the new project manager.

# data[].attributes.attachment_link.readable_text
What Is Project Management?

Imagine that you work as a project manager for a company called Disaster Recovery. Your job is to organize and coordinate human and financial resources so that projects, 1-time events that have a specific start and end date, are completed.

Projects can include a variety of different things, such as designing new software to increase efficiency, building a bridge, creating a new product, or even expanding sales into a new territory. However, your favorite projects involve helping cities and people recover from disasters.

Your boss has just told you that a natural disaster has destroyed part of Corpus Christi, Texas and Disaster Recovery has been hired to help rebuild. These projects can be done informally or the company can engage in project management to complete the task. Project management (PM) is when a company applies its human and financial resources to plan and execute a specific task.

Five Stages of Project Management

The first thing that you do as project manager is review the stages of PM and get to work implementing them. There are five stages of PM.

The first stage is project initiation. You work with your clients to gather as much information as they can regarding project specifications so that they can develop a plan. In this stage, project team members are assigned. Team members may come from a wide variety of fields or geographical regions and may not have worked together in the past. Project goals are also communicated to team members in this stage.

The next stage is project planning. In this stage a written project charter is drafted. You have decided to use PM tools, such as Gantt charts, because the project is large and complicated. A Gantt chart is a chart which shows the workflow of a project, a detailed schedule of what will happen and when. Gantt charts were developed by Henry Gantt, an American mechanical engineer.

The third stage of PM is the execution stage. This is the stage in which the resources are distributed. Relevant project information and assignments are given to team members. Communication is a key component of the PM process.

# data[].attributes.attachment_link.keywords[]
what is project management? - definition & examples - video & lesson transcript | study.com

# data[].attributes.attachment_link.title
What is Project Management? - Definition & Examples - Video & Lesson Transcript | Study.com

# data[].attributes.attachment_link.description
Imagine that you work as a project manager for a company called Disaster Recovery. Your job is to organize and coordinate human and financial resources so that projects, 1-time events that have a specific start and end date, are completed.

# data[].attributes.attachment_link.description
WELCOME TO D CHEMICALMeet the teamMOHD MIRZUANAZIZI MUMWIJOYCELIN CLAREMeet the teamHASMILLAHKHAIRUNISAMARHAINIAISYAHD CHEMICAL2016ABOUT USEXPERIENCEVISION & MISSIONOBJECTIVEORGANIZATION CHARTI NEED A DETERGENT THAT COST EFFECTIVE, ECO FRIENDLY AND EFFECTIVE1ECO- ENZYME DETERGENTWORK BREAKDOWN STRUCTURERESPONSIBILITY MATRIXGANN CHARTDESCRIPTION OF TASKSNETWORK DIAGRAMFINANCECOSTINGCOSTINGIt'sA DEAL2 YEARS CONTRACTChem D & D CHEMICALa ContractSigningVISIT USwww.DCHEMICAL.COMBEHIND THE SCREENWedid it!THANK YOU

# data[].attributes.attachment_link.description
WORK BREAKDOWN STRUCTURE WORK BREKDOWN STRUCTURE Definition of WBS Disadvantages of WBS Too little detail can result in tasks that are too large to manage effectively Advantages of WBS The work breakdown structure provides a common framework for the natural development of the overall planning and control of a contract

# data[].attributes.attachment_link.readable_text
What do you want to do?

Create custom WBS codes

Renumber WBS codes

Use basic outline numbers

Create custom WBS codes

Click Project. In the Properties group, click WBS and then click Define Code.

1. In the Length column, set the number of characters for each level of the code string. Click Any to allow any number of characters for that level.

2. In the Separator column, pick a character to separate the code for one level from the code for the next level.

The default separator is a period. You can choose others or choose not to have a separator character at all.

Note: The separator character can't also be used as part of a code.

3. Set a code string for each level of indented tasks in your outline.

To specify individual codes for each level, click the next row, and complete the Sequence, Length, and Separator columns.

Renumber WBS codes

When you move or delete tasks, Project doesn't automatically renumber the WBS codes in case you're using them in documents or other systems that are not linked to your Project file. This means that the codes for the remaining tasks will likely be incorrect. Here's how to renumber the WBS codes for all tasks or selected tasks:

1. Pick the tasks you want to renumber. The first task you pick will not be renumbered.

To renumber WBS codes for all tasks, don't select any tasks.

2. Click Project. In the Properties group, click WBS and then click Renumber.

3. Click Selected tasks to renumber the codes for the tasks you selected.

Click Entire project to renumber the codes for all tasks in the project.

Use basic outline numbers

If you don't need the detailed structure provided by WBS codes, you can use a basic outline.

Project automatically creates an outline number for each task, based on where the task appears in the structure of the task list. For example, the first task in your task list is numbered 1. If that task has three subtasks, the subtasks are numbered 1.1, 1.2, and 1.3.

Outline numbers consist of numbers only, and you can't edit them. They change automatically when you move a task up or down in the task list and when you indent or outdent tasks.

To show outline numbers, add the Outline Number field to a table or sheet view. You can also add outline numbers directly to the task names:

1. Go to the Gantt Chart or Task Sheet.

2. Click Format, and then in the Show/Hide group, check Outline Number.

Top of Page

This section applies only to Microsoft Project 2007.

What do you want to do?

Learn about WBS codes

Define custom WBS codes

Renumber WBS codes

Learn about WBS codes

There are two types of WBS codes in Microsoft Office Project: outline numbers and custom WBS codes. Read the following sections to learn more.

Outline numbers

Outline numbers are the simplest type of WBS coding. Microsoft Office Project automatically calculates an outline number for each task, basing the numbering on the outline structure of the task list. For example, the first task in your task list is numbered 1. If that task has three subtasks, the subtasks are numbered 1.1, 1.2, and 1.3.

Outline numbers consist of numbers only (no letters), and you cannot edit them. They do, however, change automatically when you move a task up or down in the task list and when you indent or outdent tasks. For example, if a subtask currently has an outline number of 3.5.4, and if you move it up one row in the list, the outline number is automatically updated to 3.5.3. If you then outdent that same subtask, the outline number is automatically updated to 3.6.

Tip: To display outline numbers, you can add the Outline Number field to a table or sheet view, or you can choose to display the outline numbers next to the task names. To display the outline numbers next to the task names, on the Tools menu, click Options, and then click the View tab. Under Outline options, select the Show outline number check box.

Custom WBS codes

If your project would benefit from having detailed WBS codes that are made up of specific lengths, sequences, or sets of numbers and letters, you can define a single custom WBS code mask for the project. (No project can have more than a single custom code mask.) The custom WBS code is recorded in the WBS field.

As with outline numbers, each level of a custom WBS code represents an outline level in the task list. You can use a unique format for each level of the code, and each level is listed in the code according to the hierarchy of tasks, summary tasks, and subtasks.

For example, if you are planning phased projects that align with organizational directives for the upcoming fiscal year, you can create a custom WBS code mask that represents each task by using the corresponding directive, quarter, and project. Using this code, you might have a task that has a custom WBS code of CustSat.Q3.CSTools.11, indicating that it is task 11 in the Customer Support Tools Upgrade project, which starts during the third quarter and which supports the Customer Satisfaction business directive for the planned fiscal year.

Define custom WBS codes

1. On the View menu, click a sheet view, such as the Task Sheet view.

To use a view that does not appear on the View menu, click More Views, click the view that you want to use in the Views list, and then click Apply.

2. On the Project menu, point to WBS, and then click Define Code.

3. To distinguish tasks in this project from tasks in other projects, type a project-specific code prefix in the Project Code Prefix box.

This prefix helps to identify the project at the highest level of the WBS code. The prefix can be useful in identifying the subprojects within a master project, or when you are creating task dependencies across projects.

You can enter any combination of numbers, uppercase and lowercase letters, and symbols for the project code prefix.

4. To specify the code string for first-level tasks, in the first row in the Sequence column, click the type of character that you want to use for this level:

Click Numbers (ordered) to show a numeric WBS code for this level (for example 1, 2, and 3 for the first three summary tasks in the project).

Click Uppercase Letters (ordered) to show uppercase alphabetical WBS codes (for example A, B, and C for the first three summary tasks in the project).

Click Lowercase Letters (ordered) to show lowercase alphabetical WBS codes (for example a, b, and c for the first three summary tasks in the project).

Click Characters (unordered) to show any combination of numbers and uppercase and lowercase letters (for example, Arch1, Const1, and Insp1 for the first three summary tasks in the project).

Choosing this option gives you the most flexibility for entering customized WBS codes. Project displays an asterisk (*) in the WBS field until you type or enter a string of characters for this level of the WBS code.

5. In the Length column, type or select the number of characters for each level of the code string. You can either enter the exact number of characters or select Any to allow any number of characters for that code level.

For example, you can type 3 to make three characters the mandatory number of characters to enter in one level of the WBS code. The total length of a WBS code can be from 1 to 255 characters.

6. In the Separator column, type or select a character to separate the code string for one level from the code string for the next level.

By default, the separator character is a period. You can use a different separator character at each code level.

You can also choose not to use any separator character between code levels. In the Separator field, delete the separator character.

7. Specify one code string for each level of indented tasks in your outline.

To specify individual code strings for each level, click the next row, and complete the Sequence, Length, and Separator columns.

The character that you use as a separator cannot also be used as part of the code. For example, if you use a hyphen as the separator, you cannot use a hyphen in the code that you use to represent a task.

You cannot define more than one set of WBS codes per project. If you need to show an additional organizational structure for tasks, you can use custom fields to create or apply a separate set of codes.

To view WBS codes, you must add the WBS field to your view.

To change the WBS code for a summary task and all of its subtasks, you must change the existing code, or set of asterisks, in the WBS code of the summary task to another set of characters.

For example, your WBS code for a specific subtask is Ph3.Prj5.Arch.Task3. "Task3" represents the "Develop plans" subtask, and "Arch" represents the "Architect solution" summary task. The name of the summary task is changed to "Design solution," and you need to update the code for the summary task and all of its subtasks. You modify the WBS code so that the summary task is represented by "Des," and the WBS code for the "Develop plans" subtask is automatically updated to Ph3.Prj5.Des.Task3.

Renumber WBS codes

After you move or delete tasks, their custom WBS codes may no longer be in correct sequence. Project does not automatically renumber the WBS codes, because you may be using those WBS codes in documents or other systems that are not linked to your Project file. You can renumber the WBS codes of all tasks or selected tasks:

1. On the View menu, click a sheet view that contains the tasks that you want to renumber, such as the Task Sheet.

To use a view that does not appear on the View menu, click More Views, click the view that you want to use in the Views list, and then click Apply.

2. Select the tasks that you want to renumber. (The first task in a selection of tasks is not renumbered. It is used as the reference point for renumbering the other tasks.)

To renumber WBS codes for all tasks, don't select any tasks.

3. On the Project menu, point to WBS, and then click Renumber.

4. To correct the WBS code sequence for only selected adjacent tasks, click Selected tasks.

To correct the WBS code sequence for all tasks in the project, click Entire project.

If your project contains subprojects, you can renumber some or all tasks in each subproject by displaying all of the subtasks. Click Show , and then click All Subtasks. (Project cannot renumber tasks from subprojects that are not displayed.)

Renumbering subprojects that are inserted into a master project also changes the code that represents each subproject at the project level.

To display WBS codes, you can add a WBS column to a sheet view.

To change WBS codes after Project calculates them, on the Project menu, point to WBS, and then click Define Code. In the Sequences column, change the type of character of any level of the code mask. When you update a code at the summary task level, all subtasks for that summary task are automatically updated.

If you have difficulty changing your WBS codes, it may be for one of the following reasons:

You are trying to change a WBS code that has a code mask, after the code was calculated If you created a WBS code mask, and WBS codes were already calculated for tasks, you can change the WBS code only by redefining the levels of the code mask. After redefining levels of the code mask, you can change any level of the code mask from ordered numbers, ordered uppercase letters, ordered lowercase letters, or unordered characters to another type.

You are trying to change WBS codes at a lower level in the task list You cannot change the characters in the WBS code for a subtask, only for the summary task where that level of the WBS code is defined.

Top of Page

# data[].attributes.attachment_link.description
Create custom WBS codes Renumber WBS codes Use basic outline numbers Click Project. In the Properties group, click WBS and then click Define Code. In the Length column, set the number of characters for each level of the code string. Click Any to allow any number of characters for that level.

# data[].attributes.attachment_link.title
What is Project Management? Training Video

# data[].attributes.body
Bachelor of Muamalat Administration