Lab 2 create a gantt chart and pert chart using ms project
- 1. Lab 2 Project Management Activity: Creating a Gantt Chart and PERT Chart using MS PROJECT
- 2. WHAT IS A GANTT CHART? • A Gantt chart is a project management tool assisting in the planning and scheduling of projects of all sizes, although they are particularly useful for simplifying complex projects.
- 3. Gantt Chart in Software Engineering planning, analysis designing, implementation and maintenance.
- 4. Another common breakdown also contains 5 phases: Requirements, Design, Implementation, Test, Maintenance.
- 5. A more detailed breakdown consists of • Initiation, • Concept Development, • Planning, • Analysis, • Design, • Development, • Integration and Test, • Deployment, • Operations and • Maintenance, and Disposition.
- 6. Why use a Gantt chart? who is going to do what, when and how long will it take. Establish the initial project schedule ensure everyone knows who is responsible for what.Allocate resources the initial plan will need many adjustments. Make project adjustments helps you stay on schedule. Monitor and report progress clear visuals for stakeholders and participants. Control and communicate the schedule shows key events.Display milestones As everything is depicted visually you can immediately see what should have been achieved by a certain date and, if the project is behind schedule, you can take action to bring it back on course. Identify and report problems
- 7. What is Pert Chart? • A PERT chart is a project management tool used to schedule, organize, and coordinate tasks within a project. It is basically a method to analyze the tasks involved in completing a given project, especially the time needed to complete each task, and to identify the minimum time needed to complete the total project.
- 8. What is PERT Chart? • Pert chart is a graphical representation of a project's timeline. • PERT stands for The Program Evaluation Review Technique. • PERT is a project management planning tool used to calculate the amount of time it will take to realistically finish a project.
- 9. Gantt charts vs. PERT charts: What’s the difference? • Essentially, a Gantt chart is a bar chart that lays out project tasks and timelines linearly. • The y-axis is made up of individual tasks and the x-axis represents time. • Gantt charts are great for improving efficiencies and optimizing time management, as PMs can adjust tasks in the chart as the project progresses to keep it on track for a timely delivery. • A PERT chart, on the other hand, is structured as a flow chart or network diagram that displays all the project tasks in separate boxes and connects them with arrows to clearly show task dependencies. • Although PERT — short for Program Evaluation and Review Technique — charts don’t have dates along their x-axes like Gantt charts, the individual boxes that make up PERT charts identify the time needed to complete each task.
- 10. Gantt charts vs. PERT charts: What’s the difference? GANTT CHART PERT CHART Essentially, a Gantt chart is a bar chart that lays out project tasks and timelines linearly. A PERT chart, on the other hand, is structured as a flow chart or network diagram that displays all the project tasks in separate boxes and connects them with arrows to clearly show task dependencies. The y-axis is made up of individual tasks and the x-axis represents time. Gantt charts are great for improving efficiencies and optimizing time management, as PMs can adjust tasks in the chart as the project progresses to keep it on track for a timely delivery. Although PERT — short for Program Evaluation and Review Technique — charts don’t have dates along their x-axes like Gantt charts, the individual boxes that make up PERT charts identify the time needed to complete each task.
- 11. Gantt charts vs. PERT charts: What’s the difference?
- 13. Project Management Activity: Creating a Gantt Chart and PERT Chart using MS PROJECT a Gantt chart shows the following details: • the project tasks • the people assigned on the tasks • the tasks’ start and end times • the duration of every task • the way tasks are grouped, link with each other, and overlap
- 14. Milestone If you’ve ever been confused about what is (or isn't) a milestone in your project plan, ask yourself these questions: • Is this a task or a deliverable? • Will this impact the final deadline? • Is this an important moment in the project that will indicate forward progress? • Does this need to be reviewed by stakeholders? • Is this an event that impacts the project?
- 15. Milestone • Let’s dig a little deeper and explore 3 specific examples of how using project milestones can benefit your projects. • Monitor deadlines • Spotlight important dates • Identify potential project bottlenecks
- 16. Gantt chart dependencies There are four possible relationships (dependencies) between tasks: • Finish to Start (FS) - the default • Start to Start (SS) • Finish to Finish (FF) • Start to Finish (SF)
Editor's Notes
- #4: Software engineering life-cycle consist of a series of phases, from planning, designing, coding to testing and maintenance. Gantt chart in software engineering, for example helps to streamline the entire process, leading to greater results and delivery of expected product. One common breakdown of phases does include 5: Planning, Analysis, Design, Implementation, and Maintenance.
- #5: 5 stages of SDLC: Another common breakdown also contains 5 phases: requirements, design, implementation, test and maintenance.
- #6: A more detailed breakdown consists of There are plenty of other ways to decompose the various activities that compose the lifecycle of a system.
- #17: There are four possible relationships (dependencies) between tasks: Finish to Start (FS) - the default: The task cannot start before its predecessor ends, although it may start later. This is the most common type of relationship and is described above. Start to Start (SS): The task cannot start until the predecessor starts, although it may start later. This can be useful if you have a task whose start date depends on the start date of another task. Finish to Finish (FF): The task cannot end before the predecessor ends, although it may end later. Start to Finish (SF): The task cannot end before the predecessor starts, although it may end later. This task relationship is rarely used.