Project Completion

By -

Project Completion

Significant events have rousing conclusions. Symphonies, fireworks displays, and mystery novels all end spectacularly, signifying a clear, definable, and absolute finish. Projects, particularly those that are intense or that demand extreme effort, are significant events in the lives of all the team members. They require, no less than does a concert, a sense of finality and a celebration of achievement.

Most projects fizzle out. Even the successful ones wind down slowly as the level of work tapers off, until one day only a handful of people are left to wrap things up. Those who leave before the end of the project are removed from the team and transplanted elsewhere while the work to which they have committed themselves is still in progress. These people need a distinct point of transition and closure.

Some project managers attempt to bring the team together when the project is over. But the spirit and the chemistry are not the same. The people are now involved in different projects, and you will not be able to reconstruct the atmosphere of your project. It might be nice to get together, but it will be a reunion, not a celebration.

Therefore, celebrate the milestones. In particular, schedule a celebration for the completion of the point when many of your people will be dispersing. For example, once the development work is done and only the integration team will be left, hold a party. Call for nominations for the person who overcame the toughest problem, who showed the most tact, who was the best dresser, who maintained the best humor, who was most helpful, who bought the most muffins. Make sure that you let people know how proud you are of them. List and extol their achievements. Present them with project mementos such as T-shirts or pens with the project logo.

You may argue, "How can we celebrate when the project is not over? We still need to complete integration and implementation."

Project Completion

Significant events have rousing conclusions. Symphonies, fireworks displays, and mystery novels all end spectacularly, signifying a clear, definable, and absolute finish. Projects, particularly those that are intense or that demand extreme effort, are significant events in the lives of all the team members. They require, no less than does a concert, a sense of finality and a celebration of achievement.

Most projects fizzle out. Even the successful ones wind down slowly as the level of work tapers off, until one day only a handful of people are left to wrap things up. Those who leave before the end of the project are removed from the team and transplanted elsewhere while the work to which they have committed themselves is still in progress. These people need a distinct point of transition and closure.

Some project managers attempt to bring the team together when the project is over. But the spirit and the chemistry are not the same. The people are now involved in different projects, and you will not be able to reconstruct the atmosphere of your project. It might be nice to get together, but it will be a reunion, not a celebration.

Therefore, celebrate the milestones. In particular, schedule a celebration for the completion of the point when many of your people will be dispersing. For example, once the development work is done and only the integration team will be left, hold a party. Call for nominations for the person who overcame the toughest problem, who showed the most tact, who was the best dresser, who maintained the best humor, who was most helpful, who bought the most muffins. Make sure that you let people know how proud you are of them. List and extol their achievements. Present them with project mementos such as T-shirts or pens with the project logo.

You may argue, "How can we celebrate when the project is not over? We still need to complete integration and implementation."

Comments

Post a Comment

Popular posts from this blog

The Conversion Cycle:The Traditional Manufacturing Environment

By -
Image
The Traditional Manufacturing Environment The conversion cycle consists of both physical and information activities related to manufacturing products for sale. The context-level data flow diagram (DFD) in Figure 7-1 illustrates the central role of the conversion cycle and its interactions with other business cycles. Production is triggered by customer orders from the revenue cycle and/or by sales forecasts from marketing. These inputs are used to set a production target and prepare a production plan, which drives production activities. Purchase requisitions for the raw materials needed to meet production objectives are sent to the purchases procedures (expenditure cycle), which prepares purchase orders for vendors. Labor used in production is transmitted to the payroll system (expenditure cycle) for payroll processing. Manufacturing costs associated with intermediate work-in-process and finished goods (FG) are sent to the general ledger (GL) and financial reporting system. Dependin
Read more

The Revenue Cycle:Manual Systems

By -
Image
Manual Systems The purpose of this section is to support the system concepts presented in the previous section with models depicting people, organizational units, and physical documents and files. This section should help you envision the segregation of duties and independent verifications, which are essential to effective internal control regardless of the technology in place. In addition, we highlight inefficiencies intrinsic to manual systems, which gave rise to modern systems using improved technologies. SALES ORDER PROCESSING The system flowchart in Figure 4-12 shows the procedures and the documents typical to a manual sales order system. In manual systems, maintaining physical files of source documents is critical to the audit trail. As we walk through the flowchart, notice that in each department, after completion of the assigned task, one or more documents are filed as evidence that the task was completed. Sales Department The sales process begins with a customer cont
Read more

HIPO (hierarchy plus input-process-output)

By -
Image
HIPO (hierarchy plus input-process-output) 64.1 Purpose The HIPO (Hierarchy plus Input-Process-Output) technique is a tool for planning and/or documenting a computer program. A HIPO model consists of a hierarchy chart that graphically represents the program’s control structure and a set of IPO (Input-Process-Output) charts that describe the inputs to, the outputs from, and the functions (or processes) performed by each module on the hierarchy chart. 64.2 Strengths, weaknesses, and limitations Using the HIPO technique, designers can evaluate and refine a program’s design, and correct flaws prior to implementation. Given the graphic nature of HIPO, users and managers can easily follow a program’s structure. The hierarchy chart serves as a useful planning and visualization document for managing the program development process. The IPO charts define for the programmer each module’s inputs, outputs, and algorithms. In theory, HIPO provides valuable long-term documentation. However
Read more