INITIAL PHASE

Many projects do not have a formal design phase. Instead, there is an

initiation phase, in which a detailed project plan, project charter, or project initiation
document (PID) is created. The approach you take will depend on your organization.

For projects that are quite technical or complex, you may also want to add a stage for
proof of concept .

If your proof of concept is feasible, this can reassure clients, stakeholders, and/or
funding sources they have made a good investment.

In software development, diagrams, trees, charts, or maps of the software

architecture and/or functionality are common (more on this in the software
development)

Prototypes or models may be created for product development projects. While

flowcharts are common in the non-profit realm.

Risk identification. It is one of the most important factor which decides the fate of
Risk Management in an Enterprise or organization.

Routine identification techniques such as brainstorming or checklists could be used

for opportunity identification, but the habit of management teams to think negatively
in such settings is hard to overcome.

In recent years, risk management has developed into an accept discipline, applied
broadly across a range of industry types and countries, with its own language,
techniques and tools, and a growing body of literature devoted to the subject.

Opportunities and threats both involve uncertainty that has the potential to affect
objectives, and both can be handled by the same process, although some
modifications may be required to the standard risk management approach in order to
deal effectively with opportunities.

The goal of risk management is to optimize accomplishment of objectives by

minimizing threats and maximizing opportunities.

As a project manager, you can decide on waterfall or agile approaches, but when it
comes down to it, you need to know that the team can realistically execute the plan.

Some projects are smooth and easy to manage, and others are a complete
nightmare that wakes you up at early morning.

Running ideas by the team and having an open dialogue about the approach cannot
only help you with building a project plan, it’s also a big help in getting everyone to
think about the project in the same terms. This type of buy-in and communication
builds trust on a team and gets people excited about working together to solve a goal.

When you’ve got all the info you need and you’ve spoken to all parties, you should
feel more than comfortable enough to put together a rock solid project plan using
whatever tool works for you. The easiest way to build a project plan is to make it
readable.
Formatting Skills. To make your project plan readable, use some formatting skills to
make sure tasks, durations, milestones, and dates are crystal clear. Try to make a
simple project plan—the more straightforward and easier to read it is, the better.
GANTT CHART/ WORK SCHEDULE

Before you start to make a Gantt chart, you can see this theoretical process
and get everything needed in a Gantt chart.

 Know the project: It is essential before making a Gantt chart to know

the project thoroughly. The first thing is to divide the whole project
into sub-basic tasks, and then the whole team has to sit and study each
task in the project carefully. Every bit of the task, the probable time it
would consume, the resources required, etc.

Just go through each step of the task. Because this is what complete
planning is all about. After this process, you have to see how the tasks
relate, the relationship between them, how they communicate, etc.
According to this, you will decide the sequence of the tasks.

 Decide the Time duration: Now, when you have done all the division
and studying process, it's time to set the time on which these tasks
have to be completed. The exact time before this, the probable time
was set. For this purpose, it is vital to involve the whole team, take their
feedback, and know their abilities. Decide the time the resource
requires to complete a particular task.
 Everyone should know everything: It is important to consider the
whole team while planning the project. Each and every person in the
project should know what things are required to complete a project.

They should know everything about the project. The person with whom
they would communicate should know the milestones, the resources,
 and the tools used to complete a specific task. Everything in the project
planning should be transparent to the whole team working on it.

 Mapping all the things to the Gantt Chart: After you have gathered
all the tasks and the resources on a platform, now is the time to map all
the stuff on the Gantt Chart. The chart should be made with all the
considerations you have made.

List down all the tasks on the first column, then there would be
resources in the next column, and then you will set the bars in front of
every or a group of tasks that will depict how much work has been
done.

Also, map the decided time duration above the chart plus set the
milestones with the bars. Use computer software that will make your
Gantt chart look complete and perfect.