Tags |
|
|
Casual Articles - Project Plans Are the Way to Go
Business owners everywhere know: it takes policies and strategies to make a business succeed. The idea of owning a business has become so competitive, that most business owners will spend a lot of time trying to find new ideas to implement along with different strategies to use. Finding businesses that know how to succeed are essential in learning what the formulas are. By doing this, you can master your own formula to success!If you want to look around at the businesses that succeed, you will find one thing in common with all of them. They understand that the most important thing to success is customer satis
* 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 Micro
Due to the drought issues which persist still in many states we are seeing the emergence of a new type of car wash in America; one which is indeed quite healthy for the environment. Some car washes are now recycling 90-95% of their wash water, yes that means the water is used over and over and the filters are getting clogged. The POTWs; Publicly Owned Treatment Works must accept high concentrated wastewater once the reclaim tanks are dumped. The smell this creates is also a big deal. In a full service carwash, which there are about 20,000 in the US they will have problems with these nearly 100% reclaim systems.
* 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 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 Micros
Have you ever walked into a business establishment and been immediately struck by a negative, tense atmosphere? Sure you have! And did you do what most of us do? Stand there in the hopes of getting someone's attention - shifting from foot to foot and clearing your throat only to be met with a stony silence and averted faces! Finally you speak up in the hopes that one of the employees in your line of vision will respond. Ah! Here comes one now! Plastered on his/her face is a long-suffering look of "if I must then I will help you"! This is NOT a "happy" employee.How an employer appreciates and treats his emplo
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 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 Micro
So you’ve decided to take the plunge and start hunting for a new job. This takes courage, so congratulations on being willing to step out there! One of the next hurdles in navigating your personal career path is the job interview. Maybe interviews are old hat for you; maybe you're fresh out of school and are just learning the protocol. Either way, consider this article a mini refresher course and pep talk to get you going! Below are a few thoughts to file under "Why I Don't Need to be Nervous on Interview Day." Reason 1: I am not desperate for this job. Many people approach the job interview
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 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 Micro
Lean enterprise and business process improvement, business optimization, cost cutting TQM, quality, Six Sigma, business reengineering and other such-like initiatives, falls within the cadre of business process management.It forms the cradle, feeding ground and impetus for making sense of, improving and capitalizing on the intricacies, dynamic elements and events that occur in our planning, conducting, practice and execution of modern business in the new economy and digital age.It is about objectively, stepping back, diagnosing, base-lining and analyzing, then streamlining and making things more effective,
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 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 Micro
If you’re considering teaching ESL in South Korea, there are a few things that you should know before making your decision. It’s sometimes difficult to get accurate information. I will sum up some of the most important points for you hear. Then, when you decide to go to Korea, you’ll be confident in your decision.1. You don’t need a TESOL CertificateThere are a lot of sites on the Net and businesses out there that will try to convince you to take a course to get certified to teach English as a Second Language. To clear up the misconceptions, you don’t need it! All you need to qualify to teach in South
* 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.casualarticles.com/article/20377/casualarticles-Project-Plans-Are-the-Way-to-Go.html">Project Plans Are the Way to Go</a>
BB link (for phorums):
[url=http://www.casualarticles.com/article/20377/casualarticles-Project-Plans-Are-the-Way-to-Go.html]Project Plans Are the Way to Go[/url]
Related Articles:
The Reflective Supply Chain in Manufacturing
Electronic Resume Writing Tips That Boost Your Interview Appointment Success
The Cold Facts of Starting Your Own Small Business
Bookmark it:
|