1. Team member, Team member and Team member
Team Name
Team member, Team member
and
Team member

2. Your project objective statement
everyone has their project, it is up to your team to define the project objective and come up with your project objective statement.

3. Scope Statement
In defining and documenting the scope statement in effect says “here is what we will do on this project or “Here is the approved project and product scope for this project.”
The development of the scope statement can take a lot of time and involve the expert judgment of many stakeholders and even experts from outside of the organization. The project scope statement along with the Work breakdown structure (which we’ll talk about later) comprise the scope baseline, which is part of the project management plan.
*read bullets
Constraints are factors that limit the teams options, such as limits on resources, budgets, schedule and scope (mgmt saying the project must be completed with only five resources)
Assumptions are things that are assumed to be true but may not be true (it is assumed that we will not need engineering departmental approval before we start the activity)
If the constraints change or the assumptions are proven wrong, the project management plan may need to change. 3

4. Project Requirements
Identify 12 requirements; Try to include at least one requirement from each category; Regulatory, Business, User, Functional and Non Functional
Read Bullets
If you need examples of the different types of requirements, take a look at Chapter 11; Project Planning- on page 54- there are examples of what each type of requirement might be for an ATM machine.
10 minutes 4

5. Work Breakdown Structure
15 minutes
(this is where we ended) 5

6. Network Diagram
The first step is to arrange the tasks from your WBS into a sequence. Some tasks can be accomplished at any time throughout the project where other tasks depend on input from another task or are constrained by time or resources.
The WBS is not a schedule, but it is the basis for it; the network diagram is a schedule that ultimately goes into user friendly schedule formats, such as milestone and Gantt charts. 6

7. Assign Resources and Estimate the Duration
Before you can put the final schedule together, you need to know who is going to each job, and what you need available in order to do it!
Resources are people, equipment, locations, or anything else that you need in order to do all of the activities that you planned for. 7

8. Gantt Chart
Here is an example of what a gantt chart looks like from Micrsoft project 8

9. Estimate Cost
Don’t forget to set aside some money for costs overruns just in case!
Now you have full picture of how long the project will take, what resources you need and how much it is going to cost. 9