Financial planning covers a wide variety of money topics including budgeting, expenses, debt, saving, retirement and insurance among others. Understanding how each of these topics work together and affect each other is important for laying the groundwork for a solid financial foundation for you and your family.
1. BudgetingAt the very basic level of personal finance you are dealing with a budget; you make money and then you spend that money. Even if you haven’t created a detailed and written budget you continue to budget on a daily basis. When you are faced with spending money on something, you think about it and realize that by spending that money, you will not be able to spend that same money on something else.When you create a budget, you begin to see a clear picture of how much money you have, what you spend it on, and how much, if any is left over. When you can clearly see where your money is going, you can then budget appropriately so your money is going where it should.
2. Cutting ExpensesAfter you have successfully created a budget, you'll have a much better understanding of where your money goes and where you can possibly trim expenses. For many people, this is as simple as cutting back on some of the little things that can add up.
3. Getting Out of DebtEven after creating a sound budget and cutting unnecessary expenses, you may still find yourself with lingering debt to get rid of. Using credit and taking on some debt itself isn’t necessarily a bad thing, but when you can't keep up with the payments or borrow more than you can afford to pay back, you could be in trouble. One of the most important steps in getting out of debt is to pay more than the minimum amount due each month. Even a modest credit card balance can take over a decade to pay off if you simply pay the minimum amount due. In addition, paying the minimum will end up costing you thousands of dollars in interest over that period.
4. Saving for RetirementWith fewer companies offering full pension plans and the uncertainty of Social Security, it has become more important than ever to save and plan for your own retirement. Unfortunately many people feel that they simply don’t have enough money left over each month to save. Retirement savings needs to become a priority instead of an afterthought. The Internal Revenue Service has made saving for retirement even more attractive with special tax-advantaged accounts such as employer 401(k) plans, individual retirement accounts and special retirement accounts for the self-employed. These accounts allow for tax deductions, credits and even tax free earnings on some retirement savings.
5. InsuranceYou've created a budget, cut expenses, eliminated your credit card debt and, have started saving for retirement, so you are all set, right? While you've definitely come a long way, there is one more important aspect of your finances that you need to consider. You've worked hard to build a solid financial footing for you and your family, so it needs to be protected. Accidents and disasters can and do happen and if you aren’t adequately insured it could leave you in financial ruin. You need insurance to protect your life, your ability to earn income, and to keep a roof over your head.
Best Moves in a Bad Economy
Make the most of your money despite troubling financial times.
Thursday, February 19, 2009
Thursday, February 12, 2009
Calculating the real cost of software defects
Using data from a well-established software metrics database and an industry profit loss model, a method is developed that computes the real cost of dealing with software defects.
In response to the HP corporate-wide 10 x software quality improvement initiative, much attention has been focused on improving the quality of software products developed throughout HR The motivation for software quality improvement is most often expressed in terms of increased customer satisfaction with higher product quality, or more generally, as a need to position HP as a leader in quality software development.
A more fundamental motivation to support the initiative for higher software quality can be developed when software defect cost data is considered. The data presented in this paper is drawn from an extensive software project database maintained at the HP Waltham Division for product releases over the past five years. When software defect cost calculations are performed on this data, a very compelling bottom line" perspective on software quality emerges; software defects are very expensive and early defect prevention and removal techniques can substantially enhance the profit realized on software products. This paper will present a general model that can be used to calculate software defect cost data for any software or firmware product. Data from actual HP Waltham projects will be used to provide examples of software cost calculations.
The Need for Metrics
As an example of the need for substantive software quality cost data, consider the situation a project manager might encounter when attempting to justify the purchase and use of a new software development tool such as a static code analyzer. If the cost of the tool is $20,000 and if there is reliable data to suggest that the tool will uncover 50/o of the total number of software defects during typical use, is the project manager justified in acquiring and using the tool?
To provide answers to this type of question, it is important to have access to a reliable database of software quality metrics. Such a database is maintained by the software quality engineering group at the clinical systems business unit of HP's Waltham Division. This database has become an essential component of software quality activities at HP Waltham and is invaluable for such tasks as project scheduling, resource planning, project and product quality status reporting, and software defect cost calculations.
In addition to maintaining the metrics database, the software quality engineering group works with R&D in testing and process improvement activities.
Software Quality Metrics Database
Fig. 1 indicates the development phases of a typical software project, with the phases indicated in which metrics are collected and stored into the software quality database. Data is gathered from a variety of sources including software defect logging, product comparison studies, project post-mortem studies, code complexity and size analysis, and project schedule and resource plans. The physical data resides mainly in a standard HP STARS* database, which has been augmented with additional fields, files, and reporting utilities. All of the products represented in the metrics database are firmware-based medical devices such as critical care monitors, arrhythmia analysis computers, and clinical databases.
Figs, 2, 3, and 4 represent various types of useful data that can be extracted from the database. Fig. 2 documents the steps that are typically required to find, fix, and retest a defect discovered by the software quality engineering group during integration and system or acceptance testing. The engineering effort for this activity, which is shown as 20 hours, represents the average effort for finding and fixing one typical software defect. This value has been calculated using hundreds of data points from multiple software projects that have been tracked with the software quality database. Mg. 3 is an example of how an accurate schedule for the integration through the release phases can be developed using historical project data from the database. In this case, it is clear that a stable and linear relationship exists between product code size and resultant calendar time. Finally, Fig. 4 tabulates various software metrics from multiple software projects. This data can be very useful for developing project comparison studies.
The data presented in these figures is a small subset of the data that exists in the database. This specific data has been presented because of its applicability to software defect cost calculations.
Looking for Software Defect Costs
Software defect costs can be investigated using a variety of different approaches. For example, costs can be calculated on a prerelease or a postrelease basis, or costs can be determined per defect or per project phase, or costs can be weighted based on code size or programmer productivity. The software defect cost data developed in this paper focuses on the cost per prerelease software defect that is found and fixed during the integration through the release phases of project development. This approach is used because of the abundance of reliable data points available for study and because of the potential utility of the results.
In response to the HP corporate-wide 10 x software quality improvement initiative, much attention has been focused on improving the quality of software products developed throughout HR The motivation for software quality improvement is most often expressed in terms of increased customer satisfaction with higher product quality, or more generally, as a need to position HP as a leader in quality software development.
A more fundamental motivation to support the initiative for higher software quality can be developed when software defect cost data is considered. The data presented in this paper is drawn from an extensive software project database maintained at the HP Waltham Division for product releases over the past five years. When software defect cost calculations are performed on this data, a very compelling bottom line" perspective on software quality emerges; software defects are very expensive and early defect prevention and removal techniques can substantially enhance the profit realized on software products. This paper will present a general model that can be used to calculate software defect cost data for any software or firmware product. Data from actual HP Waltham projects will be used to provide examples of software cost calculations.
The Need for Metrics
As an example of the need for substantive software quality cost data, consider the situation a project manager might encounter when attempting to justify the purchase and use of a new software development tool such as a static code analyzer. If the cost of the tool is $20,000 and if there is reliable data to suggest that the tool will uncover 50/o of the total number of software defects during typical use, is the project manager justified in acquiring and using the tool?
To provide answers to this type of question, it is important to have access to a reliable database of software quality metrics. Such a database is maintained by the software quality engineering group at the clinical systems business unit of HP's Waltham Division. This database has become an essential component of software quality activities at HP Waltham and is invaluable for such tasks as project scheduling, resource planning, project and product quality status reporting, and software defect cost calculations.
In addition to maintaining the metrics database, the software quality engineering group works with R&D in testing and process improvement activities.
Software Quality Metrics Database
Fig. 1 indicates the development phases of a typical software project, with the phases indicated in which metrics are collected and stored into the software quality database. Data is gathered from a variety of sources including software defect logging, product comparison studies, project post-mortem studies, code complexity and size analysis, and project schedule and resource plans. The physical data resides mainly in a standard HP STARS* database, which has been augmented with additional fields, files, and reporting utilities. All of the products represented in the metrics database are firmware-based medical devices such as critical care monitors, arrhythmia analysis computers, and clinical databases.
Figs, 2, 3, and 4 represent various types of useful data that can be extracted from the database. Fig. 2 documents the steps that are typically required to find, fix, and retest a defect discovered by the software quality engineering group during integration and system or acceptance testing. The engineering effort for this activity, which is shown as 20 hours, represents the average effort for finding and fixing one typical software defect. This value has been calculated using hundreds of data points from multiple software projects that have been tracked with the software quality database. Mg. 3 is an example of how an accurate schedule for the integration through the release phases can be developed using historical project data from the database. In this case, it is clear that a stable and linear relationship exists between product code size and resultant calendar time. Finally, Fig. 4 tabulates various software metrics from multiple software projects. This data can be very useful for developing project comparison studies.
The data presented in these figures is a small subset of the data that exists in the database. This specific data has been presented because of its applicability to software defect cost calculations.
Looking for Software Defect Costs
Software defect costs can be investigated using a variety of different approaches. For example, costs can be calculated on a prerelease or a postrelease basis, or costs can be determined per defect or per project phase, or costs can be weighted based on code size or programmer productivity. The software defect cost data developed in this paper focuses on the cost per prerelease software defect that is found and fixed during the integration through the release phases of project development. This approach is used because of the abundance of reliable data points available for study and because of the potential utility of the results.
Wednesday, February 11, 2009
‘Don’t Know’ and ‘No’ answers Responses
Frequently a question will elicit responses that can only be classified as “don’t know” or “no answers” responses. Such responses are even encountered when using multiple choice and dichotomous questions. Such responses must be properly coded, and researchers should be prepared to include them in the tabulation procedure.
Some projects may contain so few “don’t know” and “no answer” responses that they are included only to show complete statistical tables. In other studies, it might not be possible to state what the most prevalent or common answer was if a large number of ‘don’t know’ was received.
Example: In a study concerned with which type of retail outlet was most important in the purchase of a microwave oven, researchers asked the question: At which type of outlet did you purchase your microwave oven? (Check one of the following store types).
The results are shown below, where the percentage of “don’t know” is so large that researchers were unable to draw any sound conclusions about which type of outlet is most important. The high percentage of “don’t know” may have resulted from question wording. Many respondents may not have known what was meant by the different outlet terms and, therefore, may have replied that they did not know the type of outlet at which they purchased their microwave ovens.
Ways of Handling “Don’t Know” Answers: There are three ways of handling the “don’t know” problem – none of which represents a fully satisfactory solution.
Percent of respondents Purchasing Microwave Ovens at Types of Outlets:
Type of Outlet Percent of respondents
Appliance store 26Furniture store 16Mail order house 6Department store 6Discount store 3All others 15Don’t know 28Total 100(Base = 231 respondents)
1. Show the “don’t knows” as a separate category. This is the best procedure for it does not mislead anyone about what happened.2. Estimate answers from other data contained in the questionnaire. Occasionally the “don’t know” answer can be inferred by studying other information contained in the questionnaires. For example, family income might be estimated by referring to the number of individuals in the family who are working and the occupations of each.3. Distribute the “don’t knows” proportionately among the other categories. This procedure assumes that the remainder of the sample (those who gave an answer other than “don’t know”) will be representative of the universe. This assumption may not be correct, and therefore if the extent of the “don’t knows” is not shown the reader may be misled.
Dichotomous or Multiple Choice Questions That allow only one answer:
Each of these questions types has predetermined response categories – usually pre-coded that have been established in accord with the overall objectives of the study. As a consequence, the tabulation of responses to such questions is predetermined and consists merely of counting the number of responses falling into each category. The two most common approaches to tabulating the responses to multiple-choice questions: (A) showing both quantities and percentages for each response category, and (B) showing percentages for each responses category, but only total quantity. The two approaches can be applied to both scale and dichotomous questions as well.
Open Questions that allow only one answer:
As mentioned above, categories must be established for responses to open questions and individual responses to such questions must be read and coded according to these pre-established categories. If an open question elicits only a single answer, tabulation procedures will be similar to those described in the previous paragraph. An example of such a question is, what one characteristics is most important in deciding which brand of after shave lotion you purchase? (If the question asked, what characteristics are important in deciding which brand of after shave lotion you purchase? More than one response would be possible.
Some projects may contain so few “don’t know” and “no answer” responses that they are included only to show complete statistical tables. In other studies, it might not be possible to state what the most prevalent or common answer was if a large number of ‘don’t know’ was received.
Example: In a study concerned with which type of retail outlet was most important in the purchase of a microwave oven, researchers asked the question: At which type of outlet did you purchase your microwave oven? (Check one of the following store types).
The results are shown below, where the percentage of “don’t know” is so large that researchers were unable to draw any sound conclusions about which type of outlet is most important. The high percentage of “don’t know” may have resulted from question wording. Many respondents may not have known what was meant by the different outlet terms and, therefore, may have replied that they did not know the type of outlet at which they purchased their microwave ovens.
Ways of Handling “Don’t Know” Answers: There are three ways of handling the “don’t know” problem – none of which represents a fully satisfactory solution.
Percent of respondents Purchasing Microwave Ovens at Types of Outlets:
Type of Outlet Percent of respondents
Appliance store 26Furniture store 16Mail order house 6Department store 6Discount store 3All others 15Don’t know 28Total 100(Base = 231 respondents)
1. Show the “don’t knows” as a separate category. This is the best procedure for it does not mislead anyone about what happened.2. Estimate answers from other data contained in the questionnaire. Occasionally the “don’t know” answer can be inferred by studying other information contained in the questionnaires. For example, family income might be estimated by referring to the number of individuals in the family who are working and the occupations of each.3. Distribute the “don’t knows” proportionately among the other categories. This procedure assumes that the remainder of the sample (those who gave an answer other than “don’t know”) will be representative of the universe. This assumption may not be correct, and therefore if the extent of the “don’t knows” is not shown the reader may be misled.
Dichotomous or Multiple Choice Questions That allow only one answer:
Each of these questions types has predetermined response categories – usually pre-coded that have been established in accord with the overall objectives of the study. As a consequence, the tabulation of responses to such questions is predetermined and consists merely of counting the number of responses falling into each category. The two most common approaches to tabulating the responses to multiple-choice questions: (A) showing both quantities and percentages for each response category, and (B) showing percentages for each responses category, but only total quantity. The two approaches can be applied to both scale and dichotomous questions as well.
Open Questions that allow only one answer:
As mentioned above, categories must be established for responses to open questions and individual responses to such questions must be read and coded according to these pre-established categories. If an open question elicits only a single answer, tabulation procedures will be similar to those described in the previous paragraph. An example of such a question is, what one characteristics is most important in deciding which brand of after shave lotion you purchase? (If the question asked, what characteristics are important in deciding which brand of after shave lotion you purchase? More than one response would be possible.
Forecasting (OM)
Planning is a fundamental activity of management. Forecasting forms the basis of planning. Be it planning for sales and marketing or production planning or manpower planning forecasts are extremely important.
What is forecasting?
Forecasting is a scientifically calculated guess. It is basic to all planning activity –
(1) whether it is national, regional, organizational, or functional planning; and(2) whether it is long range plan or a short range plan.
My salesman looks out of the window and gives me the sales forecast for the next year said one senior manager. This salesman may be quite effective in his job, but he is only predicting and not forecasting. Forecasting is a little more scientific than looking into a crystal ball. The scientific basis of forecasting lies in studying past, present and future trends, present and future actions and their effects. What happened in the past is relevant to what is happening now and what could happen in the future. Thus, forecasting takes into account al the three dimensions of time — past, present and future. In spite of all the calculations, forecasting remains a calculate guess. Errors are bound to be there, but it remains the foundation of management planning.
One point needs a little emphasis. Many tend to think that forecasting is important only for marketing planning and not for production because the figures for production planning are received from marketing planning any way. This is erroneous view. Production planning need not necessarily follow marketing planning. There are many situations where production planning and marketing planning have to be done together and many other situations where production planning may be done separately from marketing planning. Therefore, forecasting is a very important activity for production planning be it strategic or tactical.
Elements of Forecasting:
Forecasting consists basically of analysis of the following elements:
Internal Factors
1. Past2. Present3. Proposed or future
External factors:
1.Controllable: (1) Past (2) Present (3) Future
2. Non-controllable: (1) Past (2) Present (3) Future
Forecasting is essentially the study of internal and external forces that shape demand and supply. The shape of the things to come will depend partially upon how one shapes the controllable factors. With different strategies, the forecasting will be different offering multiple scenarios for management decision making.
If previous data is all linear, there is no problem in extrapolation. But if the previous data shows upward swings as well as downward swings then how is one to extrapolate? Many a time the upwards and downwards swings quite random or one time effects. For instance, in one particular year, a company may have received a substantial government order which may not be repeated again for many years to come. It is, therefore better not to consider such one time or random phenomena for forecasting purposes. And that is why an average taken over a number of past years or time periods is more reliable as a forecast for the future year. This is what is done in the averaging techniques. One can have a continuous average or an average only over a certain number of years or periods in time. Both continuous and discrete averaging methods are used, which we discuss below.
Moving Averages Method:
The moving average is a discrete averaging method, where periods in the past beyond a certain number are considered irrelevant for the analysts. Suppose a company wants to use a 10 week moving average for forecasting sales of a particular item; they will add sales for the last 10 weeks and divide by 10 to get the average. A week later, they would add the newest weeks’ sales and discard the oldest so that once again they have a current total of the past 10 weeks of sales. Again this needs to be divided by 10 to get the new moving average.
What is forecasting?
Forecasting is a scientifically calculated guess. It is basic to all planning activity –
(1) whether it is national, regional, organizational, or functional planning; and(2) whether it is long range plan or a short range plan.
My salesman looks out of the window and gives me the sales forecast for the next year said one senior manager. This salesman may be quite effective in his job, but he is only predicting and not forecasting. Forecasting is a little more scientific than looking into a crystal ball. The scientific basis of forecasting lies in studying past, present and future trends, present and future actions and their effects. What happened in the past is relevant to what is happening now and what could happen in the future. Thus, forecasting takes into account al the three dimensions of time — past, present and future. In spite of all the calculations, forecasting remains a calculate guess. Errors are bound to be there, but it remains the foundation of management planning.
One point needs a little emphasis. Many tend to think that forecasting is important only for marketing planning and not for production because the figures for production planning are received from marketing planning any way. This is erroneous view. Production planning need not necessarily follow marketing planning. There are many situations where production planning and marketing planning have to be done together and many other situations where production planning may be done separately from marketing planning. Therefore, forecasting is a very important activity for production planning be it strategic or tactical.
Elements of Forecasting:
Forecasting consists basically of analysis of the following elements:
Internal Factors
1. Past2. Present3. Proposed or future
External factors:
1.Controllable: (1) Past (2) Present (3) Future
2. Non-controllable: (1) Past (2) Present (3) Future
Forecasting is essentially the study of internal and external forces that shape demand and supply. The shape of the things to come will depend partially upon how one shapes the controllable factors. With different strategies, the forecasting will be different offering multiple scenarios for management decision making.
If previous data is all linear, there is no problem in extrapolation. But if the previous data shows upward swings as well as downward swings then how is one to extrapolate? Many a time the upwards and downwards swings quite random or one time effects. For instance, in one particular year, a company may have received a substantial government order which may not be repeated again for many years to come. It is, therefore better not to consider such one time or random phenomena for forecasting purposes. And that is why an average taken over a number of past years or time periods is more reliable as a forecast for the future year. This is what is done in the averaging techniques. One can have a continuous average or an average only over a certain number of years or periods in time. Both continuous and discrete averaging methods are used, which we discuss below.
Moving Averages Method:
The moving average is a discrete averaging method, where periods in the past beyond a certain number are considered irrelevant for the analysts. Suppose a company wants to use a 10 week moving average for forecasting sales of a particular item; they will add sales for the last 10 weeks and divide by 10 to get the average. A week later, they would add the newest weeks’ sales and discard the oldest so that once again they have a current total of the past 10 weeks of sales. Again this needs to be divided by 10 to get the new moving average.
Quality and cost control in field work in Data Collection
Careful supervision of the field work is necessary if accurate data to be collected. The supervision problems are much the same for telephone and for personal interviews, but these problems can be managed better and more easily telephone projects.
Control: Monitoring equipment permits a small number of specialized supervisors to listen to ongoing telephone interviews and to provide any needed corrective action as soon as the interview is over. The sample is identified by telephone numbers. The status of each number is maintained in the computer, which generates a daily report showing interviews completed, the number left to do, response rates, and work completed by each interviewers.
Quality control by the supervisor usually is based on verification that the sampling procedure is being followed insofar as telephone numbers addresses, names, and demographic characteristics can show this. Questionnaires are examined to see if all appropriate questions have been completed, if questions have been omitted when called for by respondent answers, if unsatisfactory or incomplete answers have been accepted without sufficient probing and if writing is legible.
Supervisors keep daily records on the number of calls, number of not-at-homes, numbers of refusals and number of completed interviews for each interviewer and the total for all interviewers under their control. In addition, they record hours worked. These permit them to determine the cost per completed interview, whether the job is moving on schedule and which interviewers if any are having trouble.
For personal interview studies geographically larger than one metropolitan area, local supervisors are necessary. In most instances they work for more than one research organization. It is important that they close contact with the central research office, that they be trained for work with the organization, that they receive periodic visits from representatives of the central organization to review their work and that they have written instructions and forms for each specific job.
Local supervisors have personal contact with the field force under their supervision. It is they who, typically receive the completed questionnaires daily and check them to insure that instructions are being followed and that the quality is good. They maintain the same types of daily records as to telephone supervisors but to the case of door-to-door interviewers there may be many supervisors spread throughout the country. This requires a second level of supervision to coordinate the local supervisors and to provide a regular progress report at a central point.
Detection of cheating: A special aspect of quality control is that of validation or detection of cheating. Since interviewers work independently it is not always easy to detect cheating or to distinguish cheating from honest misunderstandings as to procedure. All well run field surveys check a sample of each interviewer’s work to see if it represents actual interviewers with the individuals shown. The close supervision provided in centralized telephone studies makes cheating a very small problem, but checks are typically made anyway. In personal interview surveys local supervisors do this by phoning sample of respondents and asking if they were interviewed. When interviewers are spread over too wide an area for this to be feasible, postcards are mailed asking acknowledgment of the interview. This is usually done by saying the interview has been reported and asking if the interviewer was polite and efficient. An opportunity to report that no interview took place is provided. The number of such postcards returned is usually so low that reports of no interview can only be taken as suggestion for further investigation.
Control: Monitoring equipment permits a small number of specialized supervisors to listen to ongoing telephone interviews and to provide any needed corrective action as soon as the interview is over. The sample is identified by telephone numbers. The status of each number is maintained in the computer, which generates a daily report showing interviews completed, the number left to do, response rates, and work completed by each interviewers.
Quality control by the supervisor usually is based on verification that the sampling procedure is being followed insofar as telephone numbers addresses, names, and demographic characteristics can show this. Questionnaires are examined to see if all appropriate questions have been completed, if questions have been omitted when called for by respondent answers, if unsatisfactory or incomplete answers have been accepted without sufficient probing and if writing is legible.
Supervisors keep daily records on the number of calls, number of not-at-homes, numbers of refusals and number of completed interviews for each interviewer and the total for all interviewers under their control. In addition, they record hours worked. These permit them to determine the cost per completed interview, whether the job is moving on schedule and which interviewers if any are having trouble.
For personal interview studies geographically larger than one metropolitan area, local supervisors are necessary. In most instances they work for more than one research organization. It is important that they close contact with the central research office, that they be trained for work with the organization, that they receive periodic visits from representatives of the central organization to review their work and that they have written instructions and forms for each specific job.
Local supervisors have personal contact with the field force under their supervision. It is they who, typically receive the completed questionnaires daily and check them to insure that instructions are being followed and that the quality is good. They maintain the same types of daily records as to telephone supervisors but to the case of door-to-door interviewers there may be many supervisors spread throughout the country. This requires a second level of supervision to coordinate the local supervisors and to provide a regular progress report at a central point.
Detection of cheating: A special aspect of quality control is that of validation or detection of cheating. Since interviewers work independently it is not always easy to detect cheating or to distinguish cheating from honest misunderstandings as to procedure. All well run field surveys check a sample of each interviewer’s work to see if it represents actual interviewers with the individuals shown. The close supervision provided in centralized telephone studies makes cheating a very small problem, but checks are typically made anyway. In personal interview surveys local supervisors do this by phoning sample of respondents and asking if they were interviewed. When interviewers are spread over too wide an area for this to be feasible, postcards are mailed asking acknowledgment of the interview. This is usually done by saying the interview has been reported and asking if the interviewer was polite and efficient. An opportunity to report that no interview took place is provided. The number of such postcards returned is usually so low that reports of no interview can only be taken as suggestion for further investigation.
The two factor theory of Motivation
In the late 1950s, Frederick Herzberg and his associates conducted a study of the job attitudes of 200 engineers and accountants. Herzberg placed responses in one of 16 categories: the factors on the right side of the figure were consistently related to job satisfaction; those on the left side to job dissatisfaction. From this research, Herzberg concluded that job dissatisfaction and job satisfaction arose from two separate sets of factors. This theory was termed the two factor theory.
Dis-satisfiers (which he called “hygiene” factors) included salary, working conditions, and company policy – all of which affected the context in which work was conducted. The most important of these factors is company policy, which many individuals judge to be a major cause of inefficiency and ineffectiveness. Positive ratings for these factors did not lead to job satisfaction but merely to the absence of dissatisfaction.
Satisfiers (motivating factors) include achievement, recognition, responsibility, and advancement – all related to the job content and the rewards of work performance.
Herzberg’s work was influential in the growth of job enrichment programs. This more complicated model of needs – whereby both satisfiers and dissatisfiers can be present for a person – underscores how important it is that managers understand differences between human beings when designing motivational approaches. For evidence of how needs vary among people and over time, talk to your classmates, friends, colleagues at work, and professors about satisfiers and dissatisfiers in their lives and then do it again a year from now.
Summary of need theory: Each of the need theories we have summarized emphasizes the satisfaction of some important personnel needs that people have acquired over time. Each theory also emphasizes that people decide on their degree of satisfaction by consciously comparing their circumstances with their needs. Finally, each theory leaves room considerable variation from person to person and within a person over time.
Wal-Mart managers consistently act as if they eave studied these various versions of need theory. Giving associates responsibility in their store areas is responsive to self-actualization needs. Some Wal-Mart policies seemed to be aimed at potential job dissatisfiers. Achievement, affiliation, and power needs can all be met by Wal-Mart policies. “Lower needs” such as financial security are part of the motivation equation at Wal-Mart.
TQM and needs Theory:
An effective quality program depends on motivated employees. Fortunately, when we think about needs theory we can see elements of a TQM program itself might build that motivation. Such a program engages everyone in the organizations in the quality effort and seeks to reward people on a number of levels. For employees, developing creative approaches to once routine work, having your ideas respected and implemented, contributing to a high quality product and being valued as an expert in your field are all factors that can meet needs and build motivation. Add financial incentives that mix and a dedicated motivated employee group can develop.
When Fort sanders Health System, based in Knoxville, Tennessee decided to establish a quality program, an 11-week pilot program was developed to get people involved once the organization had sense of how and where quality improvements were needed. A team alliance program was established to test how the employees felt about the potential changes in the organization. Voluntary teams were established throughout the organization, and a procedure was defined for the teams to follow when creating and submitting ideas on improving patient care and increasing savings and revenues. If a suggestion was implemented the team members received cash awards. Fully 90 percent of the company’s 2800 employees participated in the program generating $3.2 million worth of ideas.
The program had several other benefits. First, it became clear to managers that employees wanted to share their ideas. The program also pinpointed important areas where training was needed, including training of managers who were not supporting the quality effort. Indeed, the company spent ten months working with unenthusiastic managers and developing training programs to support their quality efforts. The quality approach at Fort Sanders Health Systems was devised to enhance the needs of the organization members and to reach quality goals through motivation directed at quality.
Dis-satisfiers (which he called “hygiene” factors) included salary, working conditions, and company policy – all of which affected the context in which work was conducted. The most important of these factors is company policy, which many individuals judge to be a major cause of inefficiency and ineffectiveness. Positive ratings for these factors did not lead to job satisfaction but merely to the absence of dissatisfaction.
Satisfiers (motivating factors) include achievement, recognition, responsibility, and advancement – all related to the job content and the rewards of work performance.
Herzberg’s work was influential in the growth of job enrichment programs. This more complicated model of needs – whereby both satisfiers and dissatisfiers can be present for a person – underscores how important it is that managers understand differences between human beings when designing motivational approaches. For evidence of how needs vary among people and over time, talk to your classmates, friends, colleagues at work, and professors about satisfiers and dissatisfiers in their lives and then do it again a year from now.
Summary of need theory: Each of the need theories we have summarized emphasizes the satisfaction of some important personnel needs that people have acquired over time. Each theory also emphasizes that people decide on their degree of satisfaction by consciously comparing their circumstances with their needs. Finally, each theory leaves room considerable variation from person to person and within a person over time.
Wal-Mart managers consistently act as if they eave studied these various versions of need theory. Giving associates responsibility in their store areas is responsive to self-actualization needs. Some Wal-Mart policies seemed to be aimed at potential job dissatisfiers. Achievement, affiliation, and power needs can all be met by Wal-Mart policies. “Lower needs” such as financial security are part of the motivation equation at Wal-Mart.
TQM and needs Theory:
An effective quality program depends on motivated employees. Fortunately, when we think about needs theory we can see elements of a TQM program itself might build that motivation. Such a program engages everyone in the organizations in the quality effort and seeks to reward people on a number of levels. For employees, developing creative approaches to once routine work, having your ideas respected and implemented, contributing to a high quality product and being valued as an expert in your field are all factors that can meet needs and build motivation. Add financial incentives that mix and a dedicated motivated employee group can develop.
When Fort sanders Health System, based in Knoxville, Tennessee decided to establish a quality program, an 11-week pilot program was developed to get people involved once the organization had sense of how and where quality improvements were needed. A team alliance program was established to test how the employees felt about the potential changes in the organization. Voluntary teams were established throughout the organization, and a procedure was defined for the teams to follow when creating and submitting ideas on improving patient care and increasing savings and revenues. If a suggestion was implemented the team members received cash awards. Fully 90 percent of the company’s 2800 employees participated in the program generating $3.2 million worth of ideas.
The program had several other benefits. First, it became clear to managers that employees wanted to share their ideas. The program also pinpointed important areas where training was needed, including training of managers who were not supporting the quality effort. Indeed, the company spent ten months working with unenthusiastic managers and developing training programs to support their quality efforts. The quality approach at Fort Sanders Health Systems was devised to enhance the needs of the organization members and to reach quality goals through motivation directed at quality.
Subscribe to:
Posts (Atom)