Showing posts with label standard. Show all posts
Showing posts with label standard. Show all posts

Sunday, July 5, 2009

Application Area Knowledge, Standards and Regulations

Application areas are categories of projects that have common elements significant in such projects, but are not needed or present in all projects. Application areas are usually defined in terms of:
  • Functional departments and supporting disciplines, such as legal, production and inventory management, marketing, logistics, and personnel
  • Technical elements, such as software development or engineering, and sometimes a specific kind of engineering, such as water and sanitation engineering or construction engineering
  • Management specializations, such as government contracting, community development, and new product development
  • Industry groups, such as automotive, chemical, agriculture, and financial services.
Each application area generally has a set of accepted standards and practices, often codified in regulations. The International Organization for Standardization (ISO) differentiates between standards and regulations as follows:
  • A standard is a document established by consensus and approved by a recognized body that provides, for common and repeated use, rules, guidelines or characteristics for activities or their results, aimed at the achievement of the optimum degree of order in a given context. Some examples of standards are computer disk sizes and the thermal stability specifications of hydraulic fluids.
  • A regulation is a government-imposed requirement, which specifies product, process or service characteristics, including the applicable administrative provisions, with which compliance is mandatory. Building codes are an example of regulations.
There is an overlap in the concepts of standards and regulations that cause confusion. For example:
  • Standards often begin as guidelines that describe a preferred approach and later, with widespread adoption, become generally accepted as if they were regulations
  • Different organizational levels can mandate compliance, such as when a government agency, the management of the performing organization, or the project management team establishes specific policies and procedures.
Reference: A Guide to the Project Management Body of Knowledge (PMBOK ® Guide)

Wednesday, May 27, 2009

Dealing with Performance Problems

Leaders can help their employees improve their performance by using a progressive discipline system.

To help an employee with a performance problem, you should:
  • get to the heart of the problem
  • respond to the problem by preparing an action plan
  • use discipline to deal with the problem.
Get to the heart of the problem
When there is a problem with an employee's performance, you should get to the heart of the problem before you attempt to correct it. This is important because the cause of a performance problem is not always apparent.

To correct the problem, you need to address the cause. To determine what is causing a performance problem, you should ask the following questions:
  • Does the employee understand the goals and standards of the job?
  • Does the employee get timely feedback on his or her performance?
  • Did the employee get adequate training for the job?
  • Does the employee demonstrate competency in other tasks?
  • Is the employee capable of doing the work?
  • Does the employee have the resources to do a good job?
Respond to the problem by preparing an action plan
Once you have determined the cause of a performance problem, you should meet with the employee involved to discuss possible solutions.

When you do this, don't get personally involved in the problem or apologize for having to deal with it. You want to help the employee succeed. Find out what the employee would like to see as an outcome. Then set up a plan of action.

Begin with the assumption that any corrective action you take should first and foremost help improve an employee's performance.

The following gives more about preparing an action plan:
  • Make sure that employees with performance problems have a clear understanding of their jobs.
  • Present clear information about how the job should be done, clarify each step, and emphasize the major responsibilities.
  • Provide training if necessary.
  • Make your employees responsible for the outcome of this process. Ask them to check back with you frequently.
  • Encourage your employees.
Use discipline to deal with the problem
When it becomes necessary to take disciplinary measures, you should use a four-step procedure. Because these steps sometimes lead to termination, you should ensure that you have all of the facts and use the same procedure for all employees.
It's also important that you do not allow your judgment to be clouded by prior, unrelated problems. There is more information on the steps below:
  • In step one, verbally remind the employee about the problem, and state that the problem is now in the formal disciplinary stage.
  • Go to step two if the problem continues. Give the employee formal written notification of the continuing problem.
  • If these steps fail, move to step three, in which the employee is given one day of paid leave to decide whether to stay and improve or leave. This demonstrates the organization's desire to give the employee control over whether to stay or leave.
  • Step four is termination. Having documented all the previous steps in the employee's file, set a specific time for an interview. Inform the employee of your decision. Keep the meeting simple and short. The employee had every opportunity to improve. There is no need for further discussion.
By following well-thought-out steps in correcting performance problems, a leader can keep employees motivated and effective. Do you have procedures in place that make discipline a progressive measure?

Sunday, May 24, 2009

Identifying Performance Standards

Performance standards are target measurements for achieving quality in work. The guidelines for setting performance standards follow these three perspectives:
  1. establishing criteria for quality-performance standards
  2. clarifying quality-performance standard
  3. providing positive reinforcement and recognition for quality-performance standards
Establishing criteria for quality-performance standards
Before you set performance standards, it's important to establish your criteria. You should consider quality, quantity, time, and customer requirements as criteria for establishing performance standards.

Clarifying quality-performance standard
You should clarify your performance standards once you have established your criteria for setting them. It's important to involve your employees in this process. The following provide more information on how to do this:
  • Once you establish your criteria for setting performance standards, you should describe your criteria to your employees. You should work with your employees to prioritize the tasks according to the customer requirements, and the time, quantity and level of quality needed.
  • You should meet with your employees to record all the tasks and standards that are required to meet your criteria. To make your standards meaningful, they should be measurable.
  • You should develop a tracking system and hold regular one-on-one discussions with your employees about work in progress. Don't wait until you have problems to establish a tracking system.
Providing positive reinforcement and recognition for quality-performance standards
After you establish your criteria and clarify your performance standards, it's important to encourage your employees to follow them. You should:
  • provide positive reinforcement for following standards
  • recognize those who adhere to the standards.
Performance standards are target measurements for achieving quality in work. You can use them to help your organization.

Friday, October 10, 2008

Incorporating Policies, Procedures, and Regulations

Safety nets ensure that the work environment is secure. Human resource practices work as a safety net to ensure that the employment practices you use in forming a project team are above board.

You can ensure that the integrity of your project is beyond reproach by following the policies and guidelines set by your company, your industry, and the government.

Organizations have a variety of policies, procedures, and regulations that help the project management team with various aspects of organizational planning. These human resource practices give guidance on planning team benefits, incorporating company initiatives, and following government stipulations.

The sources of influence which govern employment practices can be divided into internal sources and external sources. Internal sources are policies set forth by the organization. External sources are decisions made outside of the company which affect company policy. Together, these internal and external sources make up the policies, procedures, and regulations governing your project.
  • Company policies - include information addressing issues like vacation time, maternity leave, sick leave, and medical benefits.
  • Regulations - deal with safety standards, minimum wage laws, and hiring discrimination.
  • Procedures - vary from company to company. Your company chooses procedures based on what works best in its industry and what has proven to provide a sense of continuity and balance.
Corporate policies and procedures are at the discretion of individual companies. These are based on what each company deems fair and what it finds produces the most productive and loyal employees. On the other hand, the laws set forth by government are unwavering standards which must be met by each and every company. While project managers should abide by the human resource practices of the organizations in which they work, the laws set by government are binding and aren't optional.

The government has placed regulations upon different industries for the benefit of the public, as well as for those who work in these industries. The regulations differ for each industry, and you should become aware of how they affect your project.

Complying with company policies, regulations, and procedures will help to ensure project success. As you build and develop your project team, remember to:
  • follow organizational procedures when assigning new jobs
  • ensure the same level of project information gets to all team members
  • provide similar training for all team members
  • ensure senior management approves any guarantee made to an employee about future roles or positions
  • inform team members why they were selected.
Company policies, regulations, and procedures are the safety nets that guide you to make sound decisions when it comes to planning the human resource aspect of your project. When you follow your company's human resource practices you stand a better chance of keeping your team members happy, the government satisfied, and your organization running smoothly.

Monday, July 7, 2008

Standards, Regulations, and Project Quality Planning

Rules are everywhere. People are bombarded by rules in the form of standards and regulations. Do you know the difference between the two?

Quality planning requires you to be familiar with the standards and regulations that affect your project. For many projects, these are well known and your planning will reflect them. The difference between standards and regulations is explained below.
  • Standards. Although standards are approved by a recognized body, compliance with them is not mandatory. They are documents of rules, guidelines, or characteristics for projects, and will shape a project's product.
  • Regulations. These documents outline the products, processes, or service characteristics of a project. Compliance to regulations is mandatory.
Standards and regulations are inputs to quality planning that can have a great effect on projects. As a project manager or member of a project team, you need to be certain your quality system is "up to code."

As with most things in life, rules are not always clear cut. There's a definite "gray area" between standards and regulations. A standard will sometimes begin as a guideline and then become a regulation. This happens when a standard becomes well-known and is widely used.

Another example of the "gray area" between standards and regulations is when each one is authorized at different levels. For example, the government requires pilots to have a national-level license for flying. At a company level, however, a pilot may be required to have a national-level pilot's license, 1,000 hours of flying time, 600 hours multi-engine flight experience, and 150 hours of night flying time.

Standards can help companies meet their quality goals. The International Organization for Standardization is an establishment that helps companies accomplish this with the ISO 9000 series. Companies that use the ISO 9000 standards follow documented procedures for the work they perform. It does not guarantee organizations will always produce good products. Instead, the ISO 9000 standards act as a tool for helping organizations meet quality goals and confirm they have a set of quality standards in place.

In summary, standards and regulations are important inputs to quality planning. Following them helps ensure that a project product is of good quality and meets stakeholder requirements.

Wednesday, July 2, 2008

Developing a Project Quality Policy

A quality policy, which is an important input to project quality planning, is a collection of documents that are usually created by quality experts and supported by top management. These documents state the overall quality intentions and direction of an organization.

Not all projects require new quality policies. If a quality policy already exists, it can be adopted for a new project. If a quality policy does not exist or if the project is a joint venture, the management team will be required to develop a new quality policy for the project.

A quality policy must indicate the level of quality the organization considers acceptable and must be applied at all levels of a project. Communicating this information is a vital step for quality planning. Project management teams need to distribute quality policy information in a timely manner to everyone involved with the project. As a project manager, you can communicate quality policies in the following ways.
  • Use written communication, in the form of formal reports, informal memos, and conversations, to send out clear and complete information to those working on the project and to outside parties.
  • You can share information with your team members using information retrieval systems such as manual filing systems, project management software, and electronic text databases.
  • You can forward information electronically using fax, electronic mail, voice mail, video conferencing, and a company intranet or the Internet.
Quality policies state a company's quality goals. These policies help a company create a sound reputation for good quality. Key goals should include continuous improvement of the product or service, customer satisfaction, and effective delivery of the service. In addition, quality policies should:
  • promote consistency throughout the project
  • include quality objectives
  • describe how organizations view quality
  • detail guidelines for all important quality matters
  • state principles of what will take place during the project, rather than how it will take place
  • state requirements for updating the policy
  • be understood, implemented, and maintained at all levels of an organization.
Quality objectives are important elements of a quality policy. Some typical quality objectives are:
  • clearly defined statement of customer needs
  • specific statements about deadlines
  • commitment to avoid harmful effects on the environment and society
  • reviews to identify opportunities for quality improvements
  • commitment to quality throughout the organization.
Quality policies are essential inputs to quality planning. Top-level managers implement quality policies throughout the duration of projects. It can be challenging for managers to stay focused on quality and avoid getting sidetracked by other matters. Ultimately, the best way for a project manager to show support for quality is to "walk the walk."

Tuesday, October 23, 2007

Identifying Performance Standards

Performance standards are target measurements for achieving quality in work. The guidelines for setting performance standards follow these three perspectives:
  1. establishing criteria for quality-performance standards
  2. clarifying quality-performance standard
  3. providing positive reinforcement and recognition for quality-performance standards
Establishing criteria for quality-performance standards
Before you set performance standards, it's important to establish your criteria. You should consider quality, quantity, time, and customer requirements as criteria for establishing performance standards.

Clarifying quality-performance standard
You should clarify your performance standards once you have established your criteria for setting them. It's important to involve your employees in this process. The following provide more information on how to do this:
  • Once you establish your criteria for setting performance standards, you should describe your criteria to your employees. You should work with your employees to prioritize the tasks according to the customer requirements, and the time, quantity and level of quality needed.
  • You should meet with your employees to record all the tasks and standards that are required to meet your criteria. To make your standards meaningful, they should be measurable.
  • You should develop a tracking system and hold regular one-on-one discussions with your employees about work in progress. Don't wait until you have problems to establish a tracking system.
Providing positive reinforcement and recognition for quality-performance standards
After you establish your criteria and clarify your performance standards, it's important to encourage your employees to follow them. You should:
  • provide positive reinforcement for following standards
  • recognize those who adhere to the standards.
Performance standards are target measurements for achieving quality in work. You can use them to help your organization.

Saturday, October 20, 2007

Identifying Performance Problems

In most organizations, it's essential that employees maintain certain performance standards in order for the department to meet its quotas.

When quotas are not met, you must determine why. What are the reasons for poor performance that you must understand?

There are a number of reasons for poor performance. You'll approach these reasons from three different perspectives:
  • the reasons for performance problems
  • the elements of performance
  • the attitude behind performance.
The reasons for performance problems
Most performance difficulties arise for four different reasons. These reasons are explained below:
  • Employees' lack of knowledge prevents them from knowing what to do.
  • Employees lack the aptitude to do what is required of them and therefore are not capable of completing tasks.
  • Excessive interferences from processes, people, or technology can create a situation where employees are not allowed to do what is required of them.
  • Finally, some performance problems are caused by employees refusing to do what's required of them. When there are no safety issues involved, this is usually a result of attitude problems.
The elements of performance
When you discover performance problems, what are you actually measuring these results against? There are seven elements of performance that help you target employees' achievements. These elements of performance are:
  1. Goals: What do they need to achieve?
  2. Standards: How are their achievements quantified?
  3. Feedback: Do they have the guidance they need?
  4. Competence: Have we properly trained them?
  5. Opportunity: Do they have chances for advancement?
  6. Means: Do they have the tools to do their job?
  7. Motive: Do they have good reasons to want to do this?
A useful tool for analyzing performance is to chart the reasons for performance problems against the elements of performance. This can help you figure out how to specifically address each performance problem.

The attitude behind performance
Attitudes are often part of vicious cycles in which an attitude provides a mental excuse to behave in a certain way. Quite often, this behavior creates a result that reinforces the original attitude.

Attitudes are not always easy to change because they can come from so many different sources. Some are brought to work by employees, and some are formed as a result of things that happen in the work setting. The following provide more about the source of attitudes:
  • personal background
  • self-esteem
  • prior experience
  • unclear goals
  • poor feedback
  • lack of recognition
  • nature of the work
  • inadequate compensation.
Consider the principal causes for performance problems for addressing the problem areas in your workplace.

Thursday, June 28, 2007

Monitoring IT Project Quality

Theodore Rubin once said, "The problem is not that there are problems. The problem is expecting otherwise, and thinking that having problems is a problem."

In IT project management, you need to prepare for possible problems and implement processes that will help you determine whether your project is producing quality results. The purpose of quality in project management is to ensure that the project accomplishes what it set out to do, despite any problems that may occur.

There are a number of international organizations that provide valuable information on the use of quality standards in project management. The International Organization for Standardization (ISO), one of these organizations, defines quality as "the totality of characteristics of an entity that bear on its ability to satisfy stated or implied needs."

There are three main processes that can help you monitor your project for quality and potential problem areas. The processes are quality planning, quality assurance, and quality control. Although these processes overlap, they each have their own particular role to fulfill in IT project management.

1. Quality planning
Quality planning is useful for identifying which quality standards are needed for the project, and ensuring those standards are achieved. In an IT project, quality planning could involve considerations for system growth, or making sure that consistent and concise information is being created.

The design of experiments is an instrument used in quality planning to determine which variables will have the most effect on the outcome of a process. You can use this instrument for determining cost and schedule trade-offs.

2. Quality assurance
The quality assurance process is used for evaluating the quality standards that have been previously identified during the quality planning process, and also at various stages throughout the project. Quality assurance will help to ensure that these standards will meet the needs of the project.

Benchmarking, an example of quality assurance, is used to determine the best ways to improve quality by doing comparisons to other projects in an attempt to meet or beat that level of quality.

3. Quality control
The quality control process is useful for observing project results to ensure they meet the standards you've set. You use the observations to improve the overall quality of the project.

The quality control process helps you determine whether products or services will be rejected or accepted. If rejected, it will be necessary to rework the product or service to meet requirements or specifications. If rejection occurs and rework is necessary, the team should make adjustments to the process to prevent future quality problems.

The Pareto Analysis/Diagram is a tool implemented during the quality control process to analyze and graphically display historical data for specific problems in a project.

Remember, by carefully implementing the quality management processes described above, your team can ensure quality in all of its IT projects.

Wednesday, June 27, 2007

Components of an IT Project Plan

A project plan is an essential part of any IT project. The project plan should be sensible, current, and receive frequent reviews. It can help you organize your documents while providing guidance on how the project is to be executed and controlled.
By breaking a project into manageable sections or components, an IT manager can maintain constant control over the project. Before embarking on a project, you must ensure that your project plan clearly does the following.
1. The plan must define the objective.Your project must have a clearly defined objective. This is the first thing you must do as an IT project manager. It is important to note that the project's objective must correspond to your company's overall objectives.
There are three points to consider when developing the objective for your project. First, you need to define what the finished product will do. Second, all parties must agree with the wording of the objective. Finally, the objective has to be documented.
2. The plan must estimate scope, time, and cost. Scope, time, and cost are prime components in any project. Each of these factors can work against the others, and it is the manager's job to ensure that these competing goals work cooperatively together. This limitation is known as the triple constraint.
The scope describes the tasks that must be completed to reach the objective. The time factor identifies the length of time estimated to complete the project. The cost includes all expenditures necessary to complete the project.
3. The plan must include details on project standards.You and your team should always develop an agreed-upon set of standards for your project. Standards will help you deliver steady, high-quality products to your sponsors or customers.
4. The plan must identify agreed-upon deliverables.Deliverables can help your team determine whether all tasks within a phase have been completed effectively. Developing a schedule for the completion of deliverables also can help you monitor your project and keep it on track.
5. The plan must establish change procedures. Change in an IT project is inevitable, and you need to plan for it. Change procedures are project-defining components that enable you to set guidelines on how and when changes will be made.
As a manager, you want to ensure that your project processes run smoothly. By understanding the components of your project, you will be able to plan and manage your IT projects more effectively.