Tags |
|
|
Links |
|
|
Answer Upon - Project Plans Are the Way to Go
Running a successful restaurant business is not an easy task. There are many issues that can come up and that must be dealt with immediately. In view of the daily chores that must be completed, most restaurants don’t bother to set any long term goals. However, you must spend some time on improving your restaurant and also set reasonable long term goals to succeed. Here are some tips for making your restaurant business a success.One tip for a successful restaurant is the location in which you restaurant is situated. This plays an important role in your success. The location of your restaurant should be easily acce
14. Quality Management Approach -- This section ensures that the customer's expectations are being met. You should write about
* How you plan to review the plan to ensure that it is going according to plan.
* The tools/techniques you will use to measure the progress.
* The acceptance criteria for the final work.
* Describe the roles and responsibilities of the individuals that will be in charge of monitoring the quality of the project.
Special Tip: This is an essential part of a project. Create a separate document that will go into detail called the Quality Management Plan, and reference it in the Project Plan.
15. Project Standards -- Identify
Fund raising has become one of the main ways for many organizations to survive. When you think of a fundraiser you immediately think about churches, schools, and other groups. Fund raising is essential for many groups to be able to function and do what they do. This article will look at some key aspects to fund raising and how you might be able to improve your fund raising skills in the future.You Must Have a PlanYou must set your eyes on a target or goal that you plan to reach. With any fund raising project you must detail out every possible aspect to the fund raiser in order to be successful. There will
* What is expected of them.
* The main milestones and deadlines.
* The dependencies.
* The limitations.
Project Plan Format
The standard format of a project plan is as follows
1. Cover Page -- The cover page should have
o Name of the project
o Your company's name
o Date of issue
o Document revision number.
Special Tip: Use page borders and your company's logo to personalize the cover page.
2. Signature Page -- This ensures that all key players have read and understand what is expected.
3. Document Revision History -- You would format this page in table format. The headers would be:
o Change number, which starts at one.
o Revision Date
o Section/Pages Affected
o Summary of changes
o Initial of person that changed project plan.
4. Table of Contents Special Tip: In Microsoft Word, use styles to create the Table of Contents.
5. Table of Figures/List of Tables -- Any drawings, flowcharts, and tables in the project plan should go on this page.
6. Introduction -- A two to three -sentence paragraph describing the project.
7. Goals and Objectives -- Some people bypass this part, but this is something you might want to reconsider. This will give you and your team desired outcomes that will aid in challenging them to excel in the project. Goals are long-term, while objectives are short-term (12-24 months) tasks that will aid in achieving the goals.
Special Tip: Make sure your goals and objectives are S.M.A.R.T (specific, measurable, attainable, and timely).
8. Scope -- Describes the quantitative assumption of the work plans, budgets, schedules, and expectations. If any work falls out of the defined scope, then the Project Manager must make adjustments, either to the scope or to the actual plan.
9. List of Deliverables -- In this section, you should have the main deliverables for the project. If there are secondary ones, list them as an appendix, as well as descriptions for all deliverables, which includes the main ones.
Special Tip: A table can give a brief overview of the deliverables in a well-formatted way. Use it.
10. Milestones -- These are the major tasks in the project that have to be accomplished. Have a start and end date for each one.
11. Assumptions -- This section is where you would write what you assume will happen in the project.
Special Tip: They should be specific and measurable.
12. Constraints -- Describe limitations and deadlines that the project must adhere to.
13. Critical Dependencies -- These are related tasks and sub tasks that are dependent on one another. For instance, Task B cannot start unless Task A is completed, or Task B doesn't finish unless Task A finishes.
14. Quality Management Approach -- This section ensures that the customer's expectations are being met. You should write about
* How you plan to review the plan to ensure that it is going according to plan.
* The tools/techniques you will use to measure the progress.
* The acceptance criteria for the final work.
* Describe the roles and responsibilities of the individuals that will be in charge of monitoring the quality of the project.
Special Tip: This is an essential part of a project. Create a separate document that will go into detail called the Quality Management Plan, and reference it in the Project Plan.
15. Project Standards -- Identify
I was helping a friend to get a visa to travel to a foreign country when I encountered some of the worst customer service within memory.The “dysfunctionary “ behind the bullet proof glass took a look at the application materials and started to criticize them, harshly, making it sound as if they were woefully inadequate.This triggered a back and forth cycle of defensiveness, each party justifying his or her opinion.At one moment, I remember thinking: “If this country doesn’t want your travel business, to heck with them; then go somewhere else!”But a few minutes later, in bumper to bumper traff
Special Tip: Use page borders and your company's logo to personalize the cover page.
2. Signature Page -- This ensures that all key players have read and understand what is expected.
3. Document Revision History -- You would format this page in table format. The headers would be:
o Change number, which starts at one.
o Revision Date
o Section/Pages Affected
o Summary of changes
o Initial of person that changed project plan.
4. Table of Contents Special Tip: In Microsoft Word, use styles to create the Table of Contents.
5. Table of Figures/List of Tables -- Any drawings, flowcharts, and tables in the project plan should go on this page.
6. Introduction -- A two to three -sentence paragraph describing the project.
7. Goals and Objectives -- Some people bypass this part, but this is something you might want to reconsider. This will give you and your team desired outcomes that will aid in challenging them to excel in the project. Goals are long-term, while objectives are short-term (12-24 months) tasks that will aid in achieving the goals.
Special Tip: Make sure your goals and objectives are S.M.A.R.T (specific, measurable, attainable, and timely).
8. Scope -- Describes the quantitative assumption of the work plans, budgets, schedules, and expectations. If any work falls out of the defined scope, then the Project Manager must make adjustments, either to the scope or to the actual plan.
9. List of Deliverables -- In this section, you should have the main deliverables for the project. If there are secondary ones, list them as an appendix, as well as descriptions for all deliverables, which includes the main ones.
Special Tip: A table can give a brief overview of the deliverables in a well-formatted way. Use it.
10. Milestones -- These are the major tasks in the project that have to be accomplished. Have a start and end date for each one.
11. Assumptions -- This section is where you would write what you assume will happen in the project.
Special Tip: They should be specific and measurable.
12. Constraints -- Describe limitations and deadlines that the project must adhere to.
13. Critical Dependencies -- These are related tasks and sub tasks that are dependent on one another. For instance, Task B cannot start unless Task A is completed, or Task B doesn't finish unless Task A finishes.
14. Quality Management Approach -- This section ensures that the customer's expectations are being met. You should write about
* How you plan to review the plan to ensure that it is going according to plan.
* The tools/techniques you will use to measure the progress.
* The acceptance criteria for the final work.
* Describe the roles and responsibilities of the individuals that will be in charge of monitoring the quality of the project.
Special Tip: This is an essential part of a project. Create a separate document that will go into detail called the Quality Management Plan, and reference it in the Project Plan.
15. Project Standards -- Identify
You’ve got your business ideas, you know what you want to sell and to whom. You’ve even got enough money to survive for six months. The next bit is easy then. Sorry no it’s not – now the hard grind starts. Here are some business myths that you should be careful not to believe.Starting a new business is easy: Well you have done a lot of the hard work if you’ve done your planning but now you are working for yourself and need to be your own boss. You will need to set clear objectives, work towards them and keep yourself motivated.I won’t have to work so hard: Sorry but entrepreneurs ge
7. Goals and Objectives -- Some people bypass this part, but this is something you might want to reconsider. This will give you and your team desired outcomes that will aid in challenging them to excel in the project. Goals are long-term, while objectives are short-term (12-24 months) tasks that will aid in achieving the goals.
Special Tip: Make sure your goals and objectives are S.M.A.R.T (specific, measurable, attainable, and timely).
8. Scope -- Describes the quantitative assumption of the work plans, budgets, schedules, and expectations. If any work falls out of the defined scope, then the Project Manager must make adjustments, either to the scope or to the actual plan.
9. List of Deliverables -- In this section, you should have the main deliverables for the project. If there are secondary ones, list them as an appendix, as well as descriptions for all deliverables, which includes the main ones.
Special Tip: A table can give a brief overview of the deliverables in a well-formatted way. Use it.
10. Milestones -- These are the major tasks in the project that have to be accomplished. Have a start and end date for each one.
11. Assumptions -- This section is where you would write what you assume will happen in the project.
Special Tip: They should be specific and measurable.
12. Constraints -- Describe limitations and deadlines that the project must adhere to.
13. Critical Dependencies -- These are related tasks and sub tasks that are dependent on one another. For instance, Task B cannot start unless Task A is completed, or Task B doesn't finish unless Task A finishes.
14. Quality Management Approach -- This section ensures that the customer's expectations are being met. You should write about
* How you plan to review the plan to ensure that it is going according to plan.
* The tools/techniques you will use to measure the progress.
* The acceptance criteria for the final work.
* Describe the roles and responsibilities of the individuals that will be in charge of monitoring the quality of the project.
Special Tip: This is an essential part of a project. Create a separate document that will go into detail called the Quality Management Plan, and reference it in the Project Plan.
15. Project Standards -- Identify
You probably see hostile customers every day. You know, the ones that treat you like a personal dumping ground for everything that has ever gone wrong in their lives? They may be sarcastic, or abusive. They may swear at you, threaten, attempt to intimidate. They are difficult to deal with, and an encounter with one of these people can ruin your day.Although you may be provoked, it isn't a good idea to respond in kind. Doing so will usually inflame the situation, and can, in fact put you at risk. Yelling back, or trading insults can result in only negative consequences for you.Let's face it. You don't have
Special Tip: A table can give a brief overview of the deliverables in a well-formatted way. Use it.
10. Milestones -- These are the major tasks in the project that have to be accomplished. Have a start and end date for each one.
11. Assumptions -- This section is where you would write what you assume will happen in the project.
Special Tip: They should be specific and measurable.
12. Constraints -- Describe limitations and deadlines that the project must adhere to.
13. Critical Dependencies -- These are related tasks and sub tasks that are dependent on one another. For instance, Task B cannot start unless Task A is completed, or Task B doesn't finish unless Task A finishes.
14. Quality Management Approach -- This section ensures that the customer's expectations are being met. You should write about
* How you plan to review the plan to ensure that it is going according to plan.
* The tools/techniques you will use to measure the progress.
* The acceptance criteria for the final work.
* Describe the roles and responsibilities of the individuals that will be in charge of monitoring the quality of the project.
Special Tip: This is an essential part of a project. Create a separate document that will go into detail called the Quality Management Plan, and reference it in the Project Plan.
15. Project Standards -- Identify
It seems to me when I was young, that the holiday season didn't start until after Thanksgiving. Not after the 4th of July. By September I am so sick of hearing about what people are doing for the holidays, that I just don't care anymore.There doesn't seem to be any Christmas spirit anymore. Oh sure, you see the occasional Nativity Scene, but even then it is only on church properties. What is wrong with a symbol of the holiday being on public property? We recently had an incident here in Detroit, where someone complained about Christmas trees at our airport being decorated. They apparently thought the Christmas tr
14. Quality Management Approach -- This section ensures that the customer's expectations are being met. You should write about
* How you plan to review the plan to ensure that it is going according to plan.
* The tools/techniques you will use to measure the progress.
* The acceptance criteria for the final work.
* Describe the roles and responsibilities of the individuals that will be in charge of monitoring the quality of the project.
Special Tip: This is an essential part of a project. Create a separate document that will go into detail called the Quality Management Plan, and reference it in the Project Plan.
15. Project Standards -- Identify standards, such as status reporting, meetings, acceptance criteria.
16. Roles & Responsibilities -- Define individuals' roles and responsibilities.
Special Tip: Use a table with headers: roles, description, and responsibilities.
17. Communications -- Describe the ways and time individuals will communicate with one another.
18. Appendices -- You would put the acronym list, detailed list of deliverables, forms that will be used, contact directory, etc.
Special Tip: Use a program like Microsoft Project to create a Work-Breakdown Structure (WBS) that will aid in creating a pictorial view of the project (i.e., Gantt charts, milestones, dependencies, resources, etc.). It will make it easier on everyone involved.
This will start you off in the right direction to create a functional project plan that will keep your project on-time, within budget that will ensure customer satisfaction.
More resources:
1. Cerritos College's Project Plan Definition
2. Wikipedia's Project Planning
3. Gantthead.com's Project Plan Specifications
HTTP = HTML link (for blogs, profiles,phorums):
<a href="http://www.hubyou.info/article/20377/hubyou-Project-Plans-Are-the-Way-to-Go.html">Project Plans Are the Way to Go</a>
BB link (for phorums):
[url=http://www.hubyou.info/article/20377/hubyou-Project-Plans-Are-the-Way-to-Go.html]Project Plans Are the Way to Go[/url]
Related Articles:
Paid Travel for Adventurous University Graduates
What is the Best Franchise for Me?
Establish A New Business And Prove Your Entrepreneur Skills
Bookmark it:
|