You need to explain a few things to your boss (perhaps print and show him
this message). Best practices say that you should not EVER be inputting the
start and end dates for the individual tasks in Project except in the very
specific circumstance when you need to establish a constraint. The
exception, the constraint, is used to take into account events that
influence your project but are out of your control such as when a vendor may
not be delivering the parts required for a certain task before 15 January -
in that case you would input 15 Jan as the start date of the task that uses
those parts so a start-no-earlier-than constraint is established, insuring
that it is never scheduled any earlier than the date the parts will be
there. But manually inputting the task dates based on your boss's estimates
puts constraints on *all* the tasks and results in a schedule that is
seriously crippled in terms of being a useful project modeling and
management tool. All manner of problems might develop as work on the
project proceeds and there's an excellent chance you'll never see them until
it's too late because the inappropriate constraints have disabled most of
Project's forecasting abilities.
Project's purpose is NOT to illustrate a schedule that has been derived
elsewhere - in the best use, you input the project's start date only.
Project then takes that, along with the estimated durations and logical
relationships between the tasks, and computes the individual task start and
finish dates for you. It is scheduling software, designed to create
schedules from basic information about the work to be done and the assets
with which you have to do it, not just make pretty pictures of schedules
that already exist. Since your boss already has some dates in mind, it can
serve as a reality check as to whether those dates are do-able and
realistic. And that's why you can't leave a task start and finish date
blank or leave it NA - there will always be something there, the result of
Project's calculations. If the dates Project comes up with when you let it
do its thing unimpeded by dates you have input differ from the dates your
boss thinks tasks should happen, the smart money will bet on Project's
calculated schedule being the one closer to what is really going to happen
in the real world when your resources go out there to do the work.