Project planning for new product Introduction

list all of the task that are required to put together the project plan

list the detailed design elements 

• _{List What are the major deliverables?}
• _{How will we get to those deliverables to meet the deadline?}
• _{Who is on the project team and what role will they play in those deliverables?}
• _{When will the team meet milestones, and when will other members of the team play a role in contributing to or providing feedback on those deliverables?}
• _{What are the goals of the project}
• _{What are your client’s needs and expectations}
• _{The makeup of your client team and their decision making process (i.e. How they’ll review and approve your team’s work), which might answer:}
  • _{Who is the Project Sponsor and how available is he or she?}
  • _{Who is the PM and will he or she plan on being in constant contact with you (they need to be)}
  • _{Who are the additional stakeholders your team should be aware of?}

• _{Has your team discussed how you will gather feedback?}
• _{Who is the final sign off? Or, who owns the project?}
• _{Is there a stakeholder we need to consider who is not on your list? (A president, dean, the boss’s wife?)}
• _{What is the project deadline? What are the factors or events that are calling for that date? (a meeting, an ad campaign, an event?)}
• _{Are there any dates when you will be closed or not available?}
• _{Will there be any meetings or points in the project where you’ll want us to present on the current project status to a larger group (i.e a board meeting)?}
• _{Has your team been through a project like this in the past?}
• _{How did it go?}
• _{Is there anything that would prevent the project from being successful?}
• _{Is there a preferred mode of communication?}
• _{Are there any points in the process that some stakeholders might not understand that we can explain?}
• _{What are your deliverables and the tasks taken to create them}
• _{What is your client’s approval process}
• _{What are the timeframes associated with tasks/deliverables}
• _{What are the resources needed for tasks/deliverables and are they available when you need them ?}
• _{Make a list of the assumptions you’re making in the plan this way you have a basis for your decissons.}
• _{Include all pertinent project info:}
  • _{Client Name, Project Name}
  • _{Version Number, Delivery Date}
• _{Break out milestones and deliverables in sections by creating headers and indenting subsequent tasks (reading one long list of tasks is really monotonous and can be mind numbing even to the best of us)}
• _{Call out which team is responsible for each task (example: “CLIENT: Provide feedback”)}
• _{Add resources responsible to each task so there is no confusion about who is responsible for what.}
• _{Be sure to show durations of tasks clearly. Each task should have a start and an end date.}
• _{Add notes to tasks that might seem confusing, or need explanation. It never hurts to add detail!}
• _{Call out project dependencies. These are important when you’re planning for the risk of delays.}
• _{Include your company’s logo and your client’s logo if you’re feeling fancy.}
• _{Use your company’s branded fonts if you’re feeling really fancy.}
• _{Put this information in a wbs in a Gantt chart then have everyine review it, comment on it and buy into it then publish it.}
•