Starter guide for project management

• A “critical path” method is a type of step-by-step project timeline. It’s best used when at least some of the tasks needed to complete a project depend on one another. 

• A project manager using critical path first lists the tasks, then determines which tasks depend on one another and which tasks can be delayed without holding up the entire project. This PM is mainly looking for the quickest way to complete a project with the least amount of downtime in between tasks. 

• The chronological sequencing of tasks, then, is a big focus here, as is the estimated duration of each task. Project management software can help make these calculations, too. 

• A “waterfall” project management method is also sequential. One of the traditional project management tools, it calls for a strictly linear progression of tasks that leads to project completion. It heads only in one direction, like a waterfall.

• The waterfall method works best when team members rely on the completion of other tasks before starting their own. It also works best if there aren’t likely to be many big surprises or changes along the way.

• A waterfall method allows projects to scale well, as it is a design-heavy and disciplined approach that can keep even large projects in check.

• As its name implies, “agile” is one of the most flexible project management methods. It was designed for teams that must be able to respond quickly to market forces or client needs. 

• Agile breaks a project down into a series of iterative cycles, or “sprints.” For example, in the software industry, those sprints usually include both the development and QA testing of one aspect of the overall product.

• Agile provides flexibility when your team doesn’t need complete control over deliverables. For example, if a working prototype of a project is your first goal, flexibility and client feedback is more important than sticking to a strict protocol. 
   

4. Scrum

• A “scrum” falls under the broader category of agile project management. It is based on small teams using short, focused sprints to achieve iterative goals. 

• These sprints usually last for a defined amount of time, usually no more than a few weeks. 

• A scrum is principally designed to break a more extensive project down into manageable chunks. It has defined roles for team members, set objectives for each sprint and a method for evaluating each sprint.

• Each sprint has a defined deliverable, too. Members of a sprint team usually conduct short, daily check-ins during the sprint and a review meeting at the end of it.
   

5. PERT (Program Evaluation and Review Technique)

• The “PERT” technique is typically used alongside critical path project management. It’s a tool whose main goal is to reduce the costs and time needed to complete a project.

• Often used in manufacturing or construction projects, PERT works best for large-scale, complex projects that have a defined sequence of tasks.

• One of PERT’s main features is a visual diagram of the project’s tasks and timelines. Within this diagram, users can draw arrows to define the “critical path” (see above). The tasks on this path are those needed to complete the entire project.
   

How to choose the right type of project management for you

Here are a few questions you and your team might ask after you’ve determined the main focus and main goals of your project.

What is the industry of the project?

• Considering what world you’re working in can eliminate certain types of project management methodologies automatically. Some methods work best for software development, for instance, while others work best for large, sequential projects like building construction.

How flexible is your timeline?

• More rigid timelines will need more linear project management methods, such as critical path or waterfall. 

• What are your start and end dates? If they’re strict, linear PM methods might work best; if they’re malleable, and other aspects of the project are more important, an agile approach might work best.

What is your budget?

• Having a fixed budget might mean you need to have a fixed timeline. That might mean you’d choose a more fixed approach, such as critical path or waterfall.

• Some project methods, such as waterfall and PERT, tend to be better for larger teams. If you don’t have the budget for a larger team, those methods may not make sense.

What kinds of teams will you be working with?

• Scrum and other forms of agile methodologies work best with several small, self-directed teams that communicate well. 

• Are there any special roles needed? Flexible methods such as agile can help with projects that have a lot of moving parts and need small, nimble teams.

How involved will all the stakeholders be?

• If your clients or other stakeholders will be involved along the way, you’ll need to consider that when planning out team size, complexity, timeline and budget.

• An iterative, responsive model like agile is most helpful when you’ll be checking in frequently for feedback.

• On the other hand, if your team or your clients are resistant to change, you may want to pick a method that lays everything out upfront. 

How complex is the project?

• Complexity affects the budget, timeline and team size, but it also affects the methodology. Simpler, shorter projects with clear and fixed requirements often work best with a waterfall or similar, linear method. 

• Will the project need to scale up? A large, complicated project also might benefit from a more heavily planned and consistently documented method, like critical path or waterfall.

No matter what type of project management you choose, trying out a specific method can help. With project management tools in hand, a complex and chaotic task can become efficient, collaborative and cost-effective.