Minimising IT Project Management Failure

Minimising IT Project Management Failure 2.0 REVIEW OF EXISTING KNOWLEDGE The following sections will provide a critical review of the research work that had been undertaken. This information is relevant to the project and most importantly is associated with the project aims and objectives. A variety of sources were analysed in order to achieve a better understanding in some of the areas considered for this research project. 2.1 Project Management The fundamental aspect of this research is project management as it focuses on how IT project management failure can be minimised. There are numerous definitions of project management; one definition given by (The Project Management Institute, 2009) states; â€Å"The application of knowledge, skills, tools and technique to project activities to meet project requirements† According to (Lewis, 1995) however, project management is the planning, scheduling, and controlling of project activities to achieve project objectives. The first definition of project management focuses more on the soft skills of project management. The definition of soft skills given by the (Oxford Dictionary, 2010) is â€Å"Personal attributes that enable someone to interact effectively and  harmoniously with other people† In comparison to Lewis this is more specific to what actually is required. Although Lewiss description is not invalid, it gives a more generalised approach to project management highlighting the fundamental points. These two definitions contain different characteristics that are important to project management but what both of these definitions have in common is completion of the project requirements or activities. To generalise project management is to apply certain personnel management skills and the application of knowledge, planning and scheduling to achieve a desired objective. 2.2 Project Methodologies and Frameworks Yardley (2002) identifies it is overwhelming why many IT projects fail. Yardley (2002) states that if something was to fail and keep on failing then at some point there would be gradual improvements to why failure occurs so often in the particular area. Gradual improvements should have been made from the lessons learnt from the failure of IT projects over a period of time. However this has not been the case as there have been many failures in IT, with the same problems reoccurring. For example, common reasons for IT failure given by (Computer Weekly, 2010) are; Commencing work too early Ambiguous contracts Inadequate estimation of work Breaking the contract Lack of engagement Al-Ahmed et al (2009) suggests that the IT industry is still young compared to other industries such as manufacturing but still attributes failure to the project management methodologies. Therefore the IT industry is still yet to formulate the needed operational standards and procedures. However as the following sections will clarify, there are â€Å"guidelines, frameworks, rules, methods† in place to counter such argument. These will be identified and critically evaluated in the following. With all these clarification in place it is overwhelming to understand the amount of failure in IT as stated by (Yardley, 2002). 2.2.1 Managing a project Lewis (2007) in his book, Fundamentals of Project Management, gave a generalised approach to what a project contains. At each relevant step, questions are to be asked by a project manager for them to consider. Lewis gives a brief indication on these steps that are considered for managing a project as illustrated below in Fig.1 Figure 1 above illustrates a general approach to project management which consists of six main areas. The illustration identifies how the project is to be started up, planned, controlled and how the project is to close. On this basis of managing a project can seem simple enough however the accomplishment of each area is a different matter, hence the number of failures within IT. Al Neimat (2005) identifies the reason for failure is due to project management processes and the aligning of IT within the organisational structure. This view is also agreed by (Al-Ahmad et al.,2009) as project management discipline in most organisations are minimal they do not have the infrastructure to provide; education, training, or management disciplines in order to allow projects to achieve successful completion. Both these authors views are correct to some extent; this is because the project management processes are not followed exactly. For example, the reasons for failure as previously mentioned by (Computer Weekly, 2010) states project work is commenced too early and highlighting some do not plan the project effectively. Al-Ahmad et al (2009) view is correct to some degree. This is because some companies may not have sufficient resources to provide training and education in project management. However (Archbold, 2008) states that over the past ten years there had been a rise in interest in project management. Archbold (2008) states the reason for the rise in interest is because there are more projects then there were ten years ago. Archbold (2008) goes on to state organisations are becoming more successful and growing very quickly and recognising that staffs are managing projects without having the project manager title. 2.2.2 Project Management Body of Knowledge (PMBOK) The PMBOK guide provides the fundamental framework which is an industry standard to managing a project. Saladis and Kerzner (2009) state the real use of the PMBOK guide is to provide companies how to manage project irrespective of the characteristics. It provides the minimum knowledge that is required of a manager in order for the manager to be effective. Stackpole (2010) agrees that the PMBOK is a standard but also goes on to say it defines what is to be best practice on most of the project most of the time. The PMBOK guide is created from individuals who are affiliated with the Project Management Institute (PMI). The members of the PMI meet every few years to update and input their intellectual knowledge into the PMBOK Guide. There have been a number of guides produced over the years with the latest version in 2008. The following sections are a brief description of the two subject areas of PMBOK which are project processes and knowledge areas adapted from (The PMBOK Guide, 2008). This is to provide managers an overview and critical review of these areas; Project Processes There are five main processes to the PMBOK that are used to manage projects. In comparison to the general guideline mentioned in 2.2.1 the PMBOK covers five out of the six areas already identified; Initiating The initiating process is where the project is defined, project sponsor is on board, project manager, the team and the requirements are identified. Planning Times scales are drawn up, scope of the project is defined in detail, risks and resources are also identified. Executing The team executes the work that needs to be done in order to achieve its objectives. The project manager in this process co-ordinate the activities within the project, some of these include managing the resources and contractors. Monitoring and Controlling Monitoring the situation and analysing what stage it should be against the project plan. The controlling of the project is achieved by comparing what the project has achieved against what was outlined in the project plan. If it not according to plan then corrective actions is taken to bring it back to target if not going according to plan. Closing Ensure all objectives are met and stakeholders are happy with a review for lessons learnt for future projects. Knowledge Areas Project managers should also be familiar with the following knowledge areas to be considered as a professional. Each knowledge area contains a set of project management processes (Abdomerovic, 2008). Knowledge Areais aimed at promoting and sharing with some of the best scholarly literature material and available tools in the management, executive education, organizational behaviour and organizational psychology fields (Delegate Management Services, 2010). Project Integration Management Integration ensures that the project is planned properly, executed and controlled. The project manager must co-ordinate and integrates each activity in order to achieve the objectives of the project. Saladis and Kerzner (2009) agree with the definition given by (The PMBOK Guide, 2008) but also add the project manager must have overall vision of the project and must understand the technical as well as the human side of planning. Project Scope Management Schwalbe (2009) definition of project scope is to define in detail the scope or work required for the project, a view also shared by (Phillips, 2007; Nokes and Kelly, 2007). Phillips (2007) states the project manager and the project team must have clear vision of what is expected from the project. This is where one of the key components of project failure arises when people on the project team are not striving for the same goals, which includes the stakeholders of the project. However Phillips agrees with the PMBOK guide but also adds to create a scope, several inputs are required. The PMBOK Guide (2008) defines project scope management to include the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully. Scope management as identified, only focuses on the output of the project and what is required to achieve the project deliverables. It does not have any concerns as to the time it takes to achieve the objectives or how much it costs (Phillips, 2007). For example, The National Insurance Recording System (NIRS2) was to be developed to replace the previous system in 1997. However one of the underlying problems was as the project commenced it became clear the system size and project scope was bigger and more complex than originally thought. This eventually led to the delay of the system at a cost of  £38 million (www.parliament.the-stationery-office.co.uk, 2010). PMBOK identifies there to be 5 areas of project scope which are: collecting the requirements, defining the scope, creating a Work break-down structure (WBS), verifying the scope and control or monitoring the scope. WBS is the process of subdividing project deliverables and project work into smaller and more manageable tasks (The PMBOK Guide, 2008). Haugan (2002) gives a detailed explanation of WBS as follows; â€Å"A deliverable-orientated grouping of project elements that organises and defines the total work scope of the project. Each descending level represents an increasingly detailed definition of the project work† WBS allows the project manager to integrate each activity and prioritise certain tasks over others. An example of a WBS is given below in Fig. 2 Project Time Management A schedule is developed to achieve the objectives, estimating the time for each task, determining the critical path and then controlling the work actually does happen. There are a number of project management tools that could be used to manage time. OConchuir (2011) identifies the simplest form of time management would be to use Milestone List which illustrate when each stage is to be completed. OConchuir (2011) also identifies that The Gantt Chart to be a widely used tool to display the milestones in a visual format. Figure 3 illustrates a Gantt Chart. Marmel and Muir (2011) state the Gantt Chart was developed by Henry Gantt in 1910, however (Parviz and Anantatmula,2005; Schwalbe, 2009; www.ganttchartmac.com, 2011) state it was developed in 1917. Chiu (2010) does not specify a specific year, however states that it was developed during the First World War. Therefore it can be assumed it was produced in between the years of 1910 to 1918. The Gantt Chart is easy to understand, modify and is a simple way to depict progress status (Westcott, 2006). However as a planning tool, there are some notable limitations as described by (Springer, 2004). The limitations are that the chart is potentially subjective, interrelationships among the schedule activities are not depicted and no follow-on implications from schedule movement. Project Cost Management Schwalbe (2009) states project cost management includes the processes required to ensure that a project team completes a project within an approved budget. Schwalbe (2009) also states it is the project managers duty to satisfy stakeholders of the project as well as striving to reduce and control costs. It is here the costing of the project is calculated: this involves estimating the resources needed, staff and materials. As the project is conducted, costs are controlled and kept on track to make sure it is kept under or on budget. There have been many projects that have been completed but failed to meet the budget due to the project spiralling out of control. A notable IT project failure was the Wessex Regional Health Authoritys (WRHA) Regional Information Systems Plan (RSIP) in 1984. This project was an initiative to improve the provision of clinical and health services. It was to cost  £25.8 million and be completed in five years. However the project was not even completed and ab andoned with the eventual cost rising to  £43 million. The reason for this high increase was because of overspending, high cost of implementation and lack of funds (Chua, 2009). Project Quality Management Saladis and Kerzner (2009) identifies the main objective of quality management is customer satisfaction. However (Stackpole, 2010) states quality management is applied to the project and product. Although in essence both these authors are correct, as providing quality throughout the project and the products will provide customer satisfaction. Schwalbe (2009) argues project quality management is a difficult knowledge area to define. This is because there are many definitions to quality management and the definitions are still vague. Schwalbe (2009) also identifies some that experts base quality on â€Å"Conformance to requirements† which means project processes and products meeting written specification. In relation to these views of the authors (The PMBOK Guide, 2008) defines project quality management as the degree to which a set of inherent characteristics fulfil requirements. Below Fig. 4 is the PMBOK guides quality management process. The PMBOK Guide (2008) identifies managers have to grasp three aspects of quality management which includes processes and activities as shown in Fig. 4; 1) Plan Quality Schwalbe (2009) states in the planning aspect of quality it involves identifying the standards that are relevant to the projects and how to satisfy these standards. Saladis and Kerzner (2009) agrees and identifies a few standards that can be used; ISO 9000/2000: The International Organisation of Standardisation (IOS) this is to provide a framework around which a quality management system can effectively be implemented www.bsi-emea.com, 2011. Saladis and Kerzner (2009) agree and explain adhering to the processes approved by the IOS will produce a consistent output. Six Sigma: Pyzdek and Keller (2009) define six sigma as a rigorous, focused, highly effective implementation of proven quality principles and techniques. Its aim is to have virtually error-free business performance. Saladis and Kerzner (2009) state the methodology for meeting these performance levels is to follow a procedure referred to as DMAIC: define, measure, analyse, improve, control. Total Quality Management (TQM): a comprehensive and integrated way of managing any organisation to meet the needs of customers consistently and continuous improvement in every aspect of the organisations activities (Evans et al.,1996). It is an approach where everyone is responsible for quality. It is designed to enable an organisation to gain competitive advantage by striving to meet 100% customer satisfaction (Yardley, 2002) 2) Perform Quality Assurance The PMBOK Guide (2008) defines quality assurance as the process of regularly evaluating the overall performance of the project to ensure the project will satisfy quality standards. Francis and Horine (2003) agree and explain quality assurance involves making sure everything is done correctly and fulfils the requirements of the project. 3) Perform Quality Control Monitoring and recording the results to see if they meet the requirements (The PMBOK Guide, 2008). This is to be achieved by statistical process control and Pareto analysis as stated by (Barkley and Saylor, 2001) and identify that this an important factor of quality even though these tools are inspection based. For example in 1992 BAE Automated System was awarded a $175.6 million contract by the city of Denver to build an airport with an integrated baggage handling system for the new Denver International Airport (DIA). This system was supposed to route and deliver luggage in the airport using unmanned carts. However it was a catastrophic failure due to the following reasons as stated by (Chua, 2009); One of the reasons for failure was the sheer expanse of the DIA it was twice the size of Manhattan, New York. Overly ambitious, as it was asked to be built in one year, but was estimated to take four years. No experience of dealing with such a large project, Conflicts with contractors, Poor management of user expectation, Continuous changes. Eventual cost was close to $2 billion over budget and sixteen months behind schedule. This example stipulates the importance of having quality aspects imbedded into the project. The project should have followed some quality guidelines such as TQM where this approach identifies everyone responsible for the quality. Project Human Resource Management Identifying the personnel needed to do the job by giving their roles and responsibilities within the team, managing and motivating that team. Also the identification of key stakeholders within the project is made here. Project Communications Management Communication is vital to any project; (The PMBOK Guide, 2008) acknowledges that the communication knowledge area involves planning and disseminating information relevant to the project. Project Risk Management Kerzner (2009) defines risk management as the act or practise of dealing with risk. This includes planning for risk, identifying potential project risk, analysing and prioritising risk, developing risk response strategies and monitoring and controlling risks to determine how they have changed. Dinsmore et al (2010) agrees and makes a valid point identifying that all projects will have a certain element of risk. This is because no two projects are the same as some are characterized by the following: Uniqueness, Complexity, Change, Assumptions, Constraints, Dependencies and most importantly People. Project Procurement Management Determining which goods and services are necessary for the project and how they are to be acquired. The PMBOK provides a great platform for understand how to manage a project. The PMBOK is a framework that covers proven techniques and practices given by existing project managers. The framework is used in major organisation such as Fujitsu and Boeing Aircraft (Blokdijk, 2008). It is more associated as knowledge based framework as it identifies â€Å"What† the project might require rather than â€Å"How† to manage a project. It does not show in great detail exactly how to go about managing a project which is why it is mentioned also as a framework and more as a guideline. The reason for identifying the method as knowledge based is because every few years PMI meet to update and input their intellectual knowledge. This can be an advantage as members input the knowledge of successful proven practices needed to manage the life-cycle of a project. For each process it outlines which necessary tools and techniques are needed. The PMBOK however has its disadvantages; PMBOK poin ts out human resource management as important but fails to miss out the need to document the processes. The reason why it is a disadvantage is because by not documenting the process, it fails to provide information for anyone else to come into the project at a later date, or when re-evaluating the project at the end why such action was taken or needs to be taken. Another disadvantage is it provides minimal amount of coverage of various project management techniques such as WBS or Gantt Chart. Managers would therefore need to consult specialised texts to grasp the subject further. It is also complex for smaller projects and has to be adapted specifically to the industry area (www.theprojectmanagement.com, 2008). 2.2.3 PRINCE2 Methodology Hedeman et al (2010) identifies PRINCE2 as an acronym for PRoject IN Controlled Environments and is a structured method for managing projects. Hedeman et al (2010) also states that PRINCE2 is a de facto standard that is used by the United Kingdom (UK) Government and is widely recognised in the private sector. Van Bon and Verheijen (2006) also agree the PRINCE2 methodology as a de facto standard in the UK and widely used in the Netherlands and Australia. Lock (2007) identifies that the PRINCE2 methodology was at first intended for use on IT projects, however it has since emerged to be effective in any given project. PRINCE2 is a set of activities to achieve its business product with the organisation structure defining responsibilities to manage the project. PRINCE was established and launched in 1989 and was based on an earlier model called PROMPT; PRINCE took over from PROMT within Government projects. PRINCE2 was published in 1996 and is the trade mark of the Office of Government Commerce (OGC) PRINCE2 Process Model In the following section is a brief overview of the process model which has been summarised from the (Managing Successful Project with PRINCE2, Office of Government Commerce, 2002) The PRINCE2 Process model consists of a number of distinctive management processes. Graham (2010) states most people fall into the trap of following this model exactly as a standard approach. It is therefore in the best interest of the project manager not to blindly follow the exact approach stated in the model. Depending on the experience of the project manager and what the project needs elements of the model can be taken and applied to a particular project. Figure 5 shows the different levels of management; Directing a Project (DP) DP is aimed at the Project Board: the board manage and monitor the projects by reports and controls through a number of decision points. Key decision points are initiating the project on the right track, commitment of more resources after checking results and project closure. This process does not cover the day to day activities of the project manager. Starting up a Project (SU) A pre-project process designed to ensure the basic elements are in place. In this process the project team is assembled and a project brief is prepared. This process also brings out the Project Mandate which defines the reason for the project and what the outcome is to be. Initiating a Project (IP) The team decides whether it is feasible for them to proceed with the project and if feasible then a business Case is produced. Other key activities here are setting up project files, encouraging the Project Board to take ownership of the project, assembling the Project Initiation Document (PID), ensuring the investment and time required is considered wisely. Portman (2009) identifies different steps to this process in comparison to (Managing Successful Project with PRINCE2, Office of Government Commerce, 2002). Portman (2009) focuses more on the people aspect as it states that all parties are to be aware of the product that is to be delivered, at what time, and quality aspects. Also management and responsibilities are made clear. Both these texts identify valid points which will enable a project manager to clarify what is to happen at this stage. But raises questions as to why the people aspects are not covered or examples given as it only states a large portion of documentation in the Managing Successful Project with PRINCE2. It gives indication that theory and actual practise is different. Controlling a Stage (CS) The Project Manager monitors and controls the day to day activities and forms the core role of the Project Manager. Other key activities include authorising, gathering progress information, reviewing stages and reporting. Managing Product Delivery (MP) Ensure planned products are created and delivered by the project. The process makes sure that the work is being done, ensuring that products meet quality criterias set. It makes sure that the work on products allocated to the team is effectively authorised and agreed. Other key activities include assessing work progress and forecasts regularly, obtaining approval for the completed products. Managing Stage Boundaries (SB) This process dictates what should be done towards the end of the stage. The objectives for this process are to assure the Project Board that all deliverables have been completed for the current stage plan, provide information for the Project Board to asses on whether to continue with the project or not, provide enough information to approve the current stage and authorise the start of the next stage and record any lessons to be learned for later projects. Closing the Project (CP) Portman (2009) states this process are the activities required to close the project and release the project manager. The project could either be the actual project end or a premature end. Objectives here are to check to see if the PID objectives or aim have been met, confirm acceptance of the product, and make recommendation for future work. Resources are freed up for allocation to other activities and prepare end project report. Planning (PL) Planning is a repeatable process and plays an important role in other processes. A few are mentioned below: Planning for an Initiation Stage Planning for a Project Planning a Stage Producing an Exception Plan As previously stated PRINCE2 is the de facto standard for the UK Government and the reason for this is the attention to detail, documentation, business justification and emphasis on dividing the project into manageable and controllable stages (www.prince2.com, 2011). There are many documentation points which enable everyone to know what has happened and how they can improve for the future. Although this methodology may be unsuitable for smaller projects, elements of this methodology can be taken out such as area of control (Bentley, 2005) and implemented into managing a project. However, the question is that if this is such a widely used methodology and is the de facto standard used by the Government, then why are IT projects still failing? And why do IT projects really fail or is it just a widely used perception of IT always failing? These are some of the questions which are going to be explored as the literature review is conducted. Analysing PRINCE2, it is evident why managers and the UK Government use this methodology. This is because it allows the manager to build on experience and the manager to be proactive and not reactive (Harris, 2010). It ensures the project process is viable to senior management (Yardley, 2002). By identifying early warning signs of potential problems and allowing proactive measures to be taken to help alleviate them. The advantages and disadvantages are identified in Table 2. The key point to consider is some project managers fail to differentiate that this is a methodology and does not need to be followed exactly to each and every point, process or technique. Project managers become too inflexible and fixed on the idea that they have to follow each and every step which can make the project long and with unnecessary processes (Charvat, 2003). Another key point regarding PRINCE2 in comparison to the Project Management Body of Knowledge (PMBOK) is the PRINCE2 misses the importance of th e need of soft skills (Charvat, 2003). PRINCE2 also misses out on areas such as human resources, leadership and management techniques, health and safety. This is different to the PMBOK which focuses on soft skills such as people management. There are numerous benefits for using a structured approach to managing a project. Below are the advantages and disadvantages given by (Office of Government Commerce (OGC), 2002) are; 2.2.4 Waterfall Methodology The waterfall method was developed by Winston W. Royce in the 1970 and is considered to be a traditional approach. This was one of the first formal approaches for information system analysis and design as stated by (Johns, 2002; Carkenord, 2009). The method is a process followed in a sequence where a task is completed before moving on to the next in a sequential manner. Figure 6 shows the waterfall methodology, (Rainardi, 2007) illustrates the approach of the waterfall when one task is completed after another. The advantages and disadvantages to the waterfall methodology according to Charvat (2003) are illustrated in Table 3 Although this is for a software development or information system methodology, the same approach can be applied to a project in completing one section and then moving on to the other. The waterfall however does not always reflect on how a project is undertaken and is rarely done in such a sequential manner. However as (Charvat, 2003) identifies, it does produce a phase by phase checkpoint. This will allow the project to stay on the right track in meeting its objectives. 2.2.5 Structured Systems Analysis and Design Method (SSADM) SSADM is a structured approach into the analysis and design of developing an Minimising IT Project Management Failure Minimising IT Project Management Failure 2.0 REVIEW OF EXISTING KNOWLEDGE The following sections will provide a critical review of the research work that had been undertaken. This information is relevant to the project and most importantly is associated with the project aims and objectives. A variety of sources were analysed in order to achieve a better understanding in some of the areas considered for this research project. 2.1 Project Management The fundamental aspect of this research is project management as it focuses on how IT project management failure can be minimised. There are numerous definitions of project management; one definition given by (The Project Management Institute, 2009) states; â€Å"The application of knowledge, skills, tools and technique to project activities to meet project requirements† According to (Lewis, 1995) however, project management is the planning, scheduling, and controlling of project activities to achieve project objectives. The first definition of project management focuses more on the soft skills of project management. The definition of soft skills given by the (Oxford Dictionary, 2010) is â€Å"Personal attributes that enable someone to interact effectively and  harmoniously with other people† In comparison to Lewis this is more specific to what actually is required. Although Lewiss description is not invalid, it gives a more generalised approach to project management highlighting the fundamental points. These two definitions contain different characteristics that are important to project management but what both of these definitions have in common is completion of the project requirements or activities. To generalise project management is to apply certain personnel management skills and the application of knowledge, planning and scheduling to achieve a desired objective. 2.2 Project Methodologies and Frameworks Yardley (2002) identifies it is overwhelming why many IT projects fail. Yardley (2002) states that if something was to fail and keep on failing then at some point there would be gradual improvements to why failure occurs so often in the particular area. Gradual improvements should have been made from the lessons learnt from the failure of IT projects over a period of time. However this has not been the case as there have been many failures in IT, with the same problems reoccurring. For example, common reasons for IT failure given by (Computer Weekly, 2010) are; Commencing work too early Ambiguous contracts Inadequate estimation of work Breaking the contract Lack of engagement Al-Ahmed et al (2009) suggests that the IT industry is still young compared to other industries such as manufacturing but still attributes failure to the project management methodologies. Therefore the IT industry is still yet to formulate the needed operational standards and procedures. However as the following sections will clarify, there are â€Å"guidelines, frameworks, rules, methods† in place to counter such argument. These will be identified and critically evaluated in the following. With all these clarification in place it is overwhelming to understand the amount of failure in IT as stated by (Yardley, 2002). 2.2.1 Managing a project Lewis (2007) in his book, Fundamentals of Project Management, gave a generalised approach to what a project contains. At each relevant step, questions are to be asked by a project manager for them to consider. Lewis gives a brief indication on these steps that are considered for managing a project as illustrated below in Fig.1 Figure 1 above illustrates a general approach to project management which consists of six main areas. The illustration identifies how the project is to be started up, planned, controlled and how the project is to close. On this basis of managing a project can seem simple enough however the accomplishment of each area is a different matter, hence the number of failures within IT. Al Neimat (2005) identifies the reason for failure is due to project management processes and the aligning of IT within the organisational structure. This view is also agreed by (Al-Ahmad et al.,2009) as project management discipline in most organisations are minimal they do not have the infrastructure to provide; education, training, or management disciplines in order to allow projects to achieve successful completion. Both these authors views are correct to some extent; this is because the project management processes are not followed exactly. For example, the reasons for failure as previously mentioned by (Computer Weekly, 2010) states project work is commenced too early and highlighting some do not plan the project effectively. Al-Ahmad et al (2009) view is correct to some degree. This is because some companies may not have sufficient resources to provide training and education in project management. However (Archbold, 2008) states that over the past ten years there had been a rise in interest in project management. Archbold (2008) states the reason for the rise in interest is because there are more projects then there were ten years ago. Archbold (2008) goes on to state organisations are becoming more successful and growing very quickly and recognising that staffs are managing projects without having the project manager title. 2.2.2 Project Management Body of Knowledge (PMBOK) The PMBOK guide provides the fundamental framework which is an industry standard to managing a project. Saladis and Kerzner (2009) state the real use of the PMBOK guide is to provide companies how to manage project irrespective of the characteristics. It provides the minimum knowledge that is required of a manager in order for the manager to be effective. Stackpole (2010) agrees that the PMBOK is a standard but also goes on to say it defines what is to be best practice on most of the project most of the time. The PMBOK guide is created from individuals who are affiliated with the Project Management Institute (PMI). The members of the PMI meet every few years to update and input their intellectual knowledge into the PMBOK Guide. There have been a number of guides produced over the years with the latest version in 2008. The following sections are a brief description of the two subject areas of PMBOK which are project processes and knowledge areas adapted from (The PMBOK Guide, 2008). This is to provide managers an overview and critical review of these areas; Project Processes There are five main processes to the PMBOK that are used to manage projects. In comparison to the general guideline mentioned in 2.2.1 the PMBOK covers five out of the six areas already identified; Initiating The initiating process is where the project is defined, project sponsor is on board, project manager, the team and the requirements are identified. Planning Times scales are drawn up, scope of the project is defined in detail, risks and resources are also identified. Executing The team executes the work that needs to be done in order to achieve its objectives. The project manager in this process co-ordinate the activities within the project, some of these include managing the resources and contractors. Monitoring and Controlling Monitoring the situation and analysing what stage it should be against the project plan. The controlling of the project is achieved by comparing what the project has achieved against what was outlined in the project plan. If it not according to plan then corrective actions is taken to bring it back to target if not going according to plan. Closing Ensure all objectives are met and stakeholders are happy with a review for lessons learnt for future projects. Knowledge Areas Project managers should also be familiar with the following knowledge areas to be considered as a professional. Each knowledge area contains a set of project management processes (Abdomerovic, 2008). Knowledge Areais aimed at promoting and sharing with some of the best scholarly literature material and available tools in the management, executive education, organizational behaviour and organizational psychology fields (Delegate Management Services, 2010). Project Integration Management Integration ensures that the project is planned properly, executed and controlled. The project manager must co-ordinate and integrates each activity in order to achieve the objectives of the project. Saladis and Kerzner (2009) agree with the definition given by (The PMBOK Guide, 2008) but also add the project manager must have overall vision of the project and must understand the technical as well as the human side of planning. Project Scope Management Schwalbe (2009) definition of project scope is to define in detail the scope or work required for the project, a view also shared by (Phillips, 2007; Nokes and Kelly, 2007). Phillips (2007) states the project manager and the project team must have clear vision of what is expected from the project. This is where one of the key components of project failure arises when people on the project team are not striving for the same goals, which includes the stakeholders of the project. However Phillips agrees with the PMBOK guide but also adds to create a scope, several inputs are required. The PMBOK Guide (2008) defines project scope management to include the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully. Scope management as identified, only focuses on the output of the project and what is required to achieve the project deliverables. It does not have any concerns as to the time it takes to achieve the objectives or how much it costs (Phillips, 2007). For example, The National Insurance Recording System (NIRS2) was to be developed to replace the previous system in 1997. However one of the underlying problems was as the project commenced it became clear the system size and project scope was bigger and more complex than originally thought. This eventually led to the delay of the system at a cost of  £38 million (www.parliament.the-stationery-office.co.uk, 2010). PMBOK identifies there to be 5 areas of project scope which are: collecting the requirements, defining the scope, creating a Work break-down structure (WBS), verifying the scope and control or monitoring the scope. WBS is the process of subdividing project deliverables and project work into smaller and more manageable tasks (The PMBOK Guide, 2008). Haugan (2002) gives a detailed explanation of WBS as follows; â€Å"A deliverable-orientated grouping of project elements that organises and defines the total work scope of the project. Each descending level represents an increasingly detailed definition of the project work† WBS allows the project manager to integrate each activity and prioritise certain tasks over others. An example of a WBS is given below in Fig. 2 Project Time Management A schedule is developed to achieve the objectives, estimating the time for each task, determining the critical path and then controlling the work actually does happen. There are a number of project management tools that could be used to manage time. OConchuir (2011) identifies the simplest form of time management would be to use Milestone List which illustrate when each stage is to be completed. OConchuir (2011) also identifies that The Gantt Chart to be a widely used tool to display the milestones in a visual format. Figure 3 illustrates a Gantt Chart. Marmel and Muir (2011) state the Gantt Chart was developed by Henry Gantt in 1910, however (Parviz and Anantatmula,2005; Schwalbe, 2009; www.ganttchartmac.com, 2011) state it was developed in 1917. Chiu (2010) does not specify a specific year, however states that it was developed during the First World War. Therefore it can be assumed it was produced in between the years of 1910 to 1918. The Gantt Chart is easy to understand, modify and is a simple way to depict progress status (Westcott, 2006). However as a planning tool, there are some notable limitations as described by (Springer, 2004). The limitations are that the chart is potentially subjective, interrelationships among the schedule activities are not depicted and no follow-on implications from schedule movement. Project Cost Management Schwalbe (2009) states project cost management includes the processes required to ensure that a project team completes a project within an approved budget. Schwalbe (2009) also states it is the project managers duty to satisfy stakeholders of the project as well as striving to reduce and control costs. It is here the costing of the project is calculated: this involves estimating the resources needed, staff and materials. As the project is conducted, costs are controlled and kept on track to make sure it is kept under or on budget. There have been many projects that have been completed but failed to meet the budget due to the project spiralling out of control. A notable IT project failure was the Wessex Regional Health Authoritys (WRHA) Regional Information Systems Plan (RSIP) in 1984. This project was an initiative to improve the provision of clinical and health services. It was to cost  £25.8 million and be completed in five years. However the project was not even completed and ab andoned with the eventual cost rising to  £43 million. The reason for this high increase was because of overspending, high cost of implementation and lack of funds (Chua, 2009). Project Quality Management Saladis and Kerzner (2009) identifies the main objective of quality management is customer satisfaction. However (Stackpole, 2010) states quality management is applied to the project and product. Although in essence both these authors are correct, as providing quality throughout the project and the products will provide customer satisfaction. Schwalbe (2009) argues project quality management is a difficult knowledge area to define. This is because there are many definitions to quality management and the definitions are still vague. Schwalbe (2009) also identifies some that experts base quality on â€Å"Conformance to requirements† which means project processes and products meeting written specification. In relation to these views of the authors (The PMBOK Guide, 2008) defines project quality management as the degree to which a set of inherent characteristics fulfil requirements. Below Fig. 4 is the PMBOK guides quality management process. The PMBOK Guide (2008) identifies managers have to grasp three aspects of quality management which includes processes and activities as shown in Fig. 4; 1) Plan Quality Schwalbe (2009) states in the planning aspect of quality it involves identifying the standards that are relevant to the projects and how to satisfy these standards. Saladis and Kerzner (2009) agrees and identifies a few standards that can be used; ISO 9000/2000: The International Organisation of Standardisation (IOS) this is to provide a framework around which a quality management system can effectively be implemented www.bsi-emea.com, 2011. Saladis and Kerzner (2009) agree and explain adhering to the processes approved by the IOS will produce a consistent output. Six Sigma: Pyzdek and Keller (2009) define six sigma as a rigorous, focused, highly effective implementation of proven quality principles and techniques. Its aim is to have virtually error-free business performance. Saladis and Kerzner (2009) state the methodology for meeting these performance levels is to follow a procedure referred to as DMAIC: define, measure, analyse, improve, control. Total Quality Management (TQM): a comprehensive and integrated way of managing any organisation to meet the needs of customers consistently and continuous improvement in every aspect of the organisations activities (Evans et al.,1996). It is an approach where everyone is responsible for quality. It is designed to enable an organisation to gain competitive advantage by striving to meet 100% customer satisfaction (Yardley, 2002) 2) Perform Quality Assurance The PMBOK Guide (2008) defines quality assurance as the process of regularly evaluating the overall performance of the project to ensure the project will satisfy quality standards. Francis and Horine (2003) agree and explain quality assurance involves making sure everything is done correctly and fulfils the requirements of the project. 3) Perform Quality Control Monitoring and recording the results to see if they meet the requirements (The PMBOK Guide, 2008). This is to be achieved by statistical process control and Pareto analysis as stated by (Barkley and Saylor, 2001) and identify that this an important factor of quality even though these tools are inspection based. For example in 1992 BAE Automated System was awarded a $175.6 million contract by the city of Denver to build an airport with an integrated baggage handling system for the new Denver International Airport (DIA). This system was supposed to route and deliver luggage in the airport using unmanned carts. However it was a catastrophic failure due to the following reasons as stated by (Chua, 2009); One of the reasons for failure was the sheer expanse of the DIA it was twice the size of Manhattan, New York. Overly ambitious, as it was asked to be built in one year, but was estimated to take four years. No experience of dealing with such a large project, Conflicts with contractors, Poor management of user expectation, Continuous changes. Eventual cost was close to $2 billion over budget and sixteen months behind schedule. This example stipulates the importance of having quality aspects imbedded into the project. The project should have followed some quality guidelines such as TQM where this approach identifies everyone responsible for the quality. Project Human Resource Management Identifying the personnel needed to do the job by giving their roles and responsibilities within the team, managing and motivating that team. Also the identification of key stakeholders within the project is made here. Project Communications Management Communication is vital to any project; (The PMBOK Guide, 2008) acknowledges that the communication knowledge area involves planning and disseminating information relevant to the project. Project Risk Management Kerzner (2009) defines risk management as the act or practise of dealing with risk. This includes planning for risk, identifying potential project risk, analysing and prioritising risk, developing risk response strategies and monitoring and controlling risks to determine how they have changed. Dinsmore et al (2010) agrees and makes a valid point identifying that all projects will have a certain element of risk. This is because no two projects are the same as some are characterized by the following: Uniqueness, Complexity, Change, Assumptions, Constraints, Dependencies and most importantly People. Project Procurement Management Determining which goods and services are necessary for the project and how they are to be acquired. The PMBOK provides a great platform for understand how to manage a project. The PMBOK is a framework that covers proven techniques and practices given by existing project managers. The framework is used in major organisation such as Fujitsu and Boeing Aircraft (Blokdijk, 2008). It is more associated as knowledge based framework as it identifies â€Å"What† the project might require rather than â€Å"How† to manage a project. It does not show in great detail exactly how to go about managing a project which is why it is mentioned also as a framework and more as a guideline. The reason for identifying the method as knowledge based is because every few years PMI meet to update and input their intellectual knowledge. This can be an advantage as members input the knowledge of successful proven practices needed to manage the life-cycle of a project. For each process it outlines which necessary tools and techniques are needed. The PMBOK however has its disadvantages; PMBOK poin ts out human resource management as important but fails to miss out the need to document the processes. The reason why it is a disadvantage is because by not documenting the process, it fails to provide information for anyone else to come into the project at a later date, or when re-evaluating the project at the end why such action was taken or needs to be taken. Another disadvantage is it provides minimal amount of coverage of various project management techniques such as WBS or Gantt Chart. Managers would therefore need to consult specialised texts to grasp the subject further. It is also complex for smaller projects and has to be adapted specifically to the industry area (www.theprojectmanagement.com, 2008). 2.2.3 PRINCE2 Methodology Hedeman et al (2010) identifies PRINCE2 as an acronym for PRoject IN Controlled Environments and is a structured method for managing projects. Hedeman et al (2010) also states that PRINCE2 is a de facto standard that is used by the United Kingdom (UK) Government and is widely recognised in the private sector. Van Bon and Verheijen (2006) also agree the PRINCE2 methodology as a de facto standard in the UK and widely used in the Netherlands and Australia. Lock (2007) identifies that the PRINCE2 methodology was at first intended for use on IT projects, however it has since emerged to be effective in any given project. PRINCE2 is a set of activities to achieve its business product with the organisation structure defining responsibilities to manage the project. PRINCE was established and launched in 1989 and was based on an earlier model called PROMPT; PRINCE took over from PROMT within Government projects. PRINCE2 was published in 1996 and is the trade mark of the Office of Government Commerce (OGC) PRINCE2 Process Model In the following section is a brief overview of the process model which has been summarised from the (Managing Successful Project with PRINCE2, Office of Government Commerce, 2002) The PRINCE2 Process model consists of a number of distinctive management processes. Graham (2010) states most people fall into the trap of following this model exactly as a standard approach. It is therefore in the best interest of the project manager not to blindly follow the exact approach stated in the model. Depending on the experience of the project manager and what the project needs elements of the model can be taken and applied to a particular project. Figure 5 shows the different levels of management; Directing a Project (DP) DP is aimed at the Project Board: the board manage and monitor the projects by reports and controls through a number of decision points. Key decision points are initiating the project on the right track, commitment of more resources after checking results and project closure. This process does not cover the day to day activities of the project manager. Starting up a Project (SU) A pre-project process designed to ensure the basic elements are in place. In this process the project team is assembled and a project brief is prepared. This process also brings out the Project Mandate which defines the reason for the project and what the outcome is to be. Initiating a Project (IP) The team decides whether it is feasible for them to proceed with the project and if feasible then a business Case is produced. Other key activities here are setting up project files, encouraging the Project Board to take ownership of the project, assembling the Project Initiation Document (PID), ensuring the investment and time required is considered wisely. Portman (2009) identifies different steps to this process in comparison to (Managing Successful Project with PRINCE2, Office of Government Commerce, 2002). Portman (2009) focuses more on the people aspect as it states that all parties are to be aware of the product that is to be delivered, at what time, and quality aspects. Also management and responsibilities are made clear. Both these texts identify valid points which will enable a project manager to clarify what is to happen at this stage. But raises questions as to why the people aspects are not covered or examples given as it only states a large portion of documentation in the Managing Successful Project with PRINCE2. It gives indication that theory and actual practise is different. Controlling a Stage (CS) The Project Manager monitors and controls the day to day activities and forms the core role of the Project Manager. Other key activities include authorising, gathering progress information, reviewing stages and reporting. Managing Product Delivery (MP) Ensure planned products are created and delivered by the project. The process makes sure that the work is being done, ensuring that products meet quality criterias set. It makes sure that the work on products allocated to the team is effectively authorised and agreed. Other key activities include assessing work progress and forecasts regularly, obtaining approval for the completed products. Managing Stage Boundaries (SB) This process dictates what should be done towards the end of the stage. The objectives for this process are to assure the Project Board that all deliverables have been completed for the current stage plan, provide information for the Project Board to asses on whether to continue with the project or not, provide enough information to approve the current stage and authorise the start of the next stage and record any lessons to be learned for later projects. Closing the Project (CP) Portman (2009) states this process are the activities required to close the project and release the project manager. The project could either be the actual project end or a premature end. Objectives here are to check to see if the PID objectives or aim have been met, confirm acceptance of the product, and make recommendation for future work. Resources are freed up for allocation to other activities and prepare end project report. Planning (PL) Planning is a repeatable process and plays an important role in other processes. A few are mentioned below: Planning for an Initiation Stage Planning for a Project Planning a Stage Producing an Exception Plan As previously stated PRINCE2 is the de facto standard for the UK Government and the reason for this is the attention to detail, documentation, business justification and emphasis on dividing the project into manageable and controllable stages (www.prince2.com, 2011). There are many documentation points which enable everyone to know what has happened and how they can improve for the future. Although this methodology may be unsuitable for smaller projects, elements of this methodology can be taken out such as area of control (Bentley, 2005) and implemented into managing a project. However, the question is that if this is such a widely used methodology and is the de facto standard used by the Government, then why are IT projects still failing? And why do IT projects really fail or is it just a widely used perception of IT always failing? These are some of the questions which are going to be explored as the literature review is conducted. Analysing PRINCE2, it is evident why managers and the UK Government use this methodology. This is because it allows the manager to build on experience and the manager to be proactive and not reactive (Harris, 2010). It ensures the project process is viable to senior management (Yardley, 2002). By identifying early warning signs of potential problems and allowing proactive measures to be taken to help alleviate them. The advantages and disadvantages are identified in Table 2. The key point to consider is some project managers fail to differentiate that this is a methodology and does not need to be followed exactly to each and every point, process or technique. Project managers become too inflexible and fixed on the idea that they have to follow each and every step which can make the project long and with unnecessary processes (Charvat, 2003). Another key point regarding PRINCE2 in comparison to the Project Management Body of Knowledge (PMBOK) is the PRINCE2 misses the importance of th e need of soft skills (Charvat, 2003). PRINCE2 also misses out on areas such as human resources, leadership and management techniques, health and safety. This is different to the PMBOK which focuses on soft skills such as people management. There are numerous benefits for using a structured approach to managing a project. Below are the advantages and disadvantages given by (Office of Government Commerce (OGC), 2002) are; 2.2.4 Waterfall Methodology The waterfall method was developed by Winston W. Royce in the 1970 and is considered to be a traditional approach. This was one of the first formal approaches for information system analysis and design as stated by (Johns, 2002; Carkenord, 2009). The method is a process followed in a sequence where a task is completed before moving on to the next in a sequential manner. Figure 6 shows the waterfall methodology, (Rainardi, 2007) illustrates the approach of the waterfall when one task is completed after another. The advantages and disadvantages to the waterfall methodology according to Charvat (2003) are illustrated in Table 3 Although this is for a software development or information system methodology, the same approach can be applied to a project in completing one section and then moving on to the other. The waterfall however does not always reflect on how a project is undertaken and is rarely done in such a sequential manner. However as (Charvat, 2003) identifies, it does produce a phase by phase checkpoint. This will allow the project to stay on the right track in meeting its objectives. 2.2.5 Structured Systems Analysis and Design Method (SSADM) SSADM is a structured approach into the analysis and design of developing an

Flexicurity a Relevant Approach in Central and Eastern Europe Essay

Flexicurity Introduction   Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚   Flexicurity is an integrated approach for endorsing security and flexibility in the labor market. Flexicurity endeavors to merge employers’ call for for a flexible labor force with workers’ call for for security. Employee call for security implies the confidence that the employees will not go through stretched periods of joblessness. Flexicurity is a new policy that is called upon because of the increased nee of security and flexibility faced by national governments, European Union, individual workers and companies, as well as sectors of industry. Legislators, policy-makers, employers and trade unions organizations have a strong call for new flexicurity policy concepts and models that guarantee to reunite the strategies of endorsing security and flexibility at the same time.   Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚   Flexibility and security has for a long time seen as incompatible, thus this new policy will be very significant in industrial relations. The EU aim of enhancing security and flexibility in the labor market is to achieve a competitive advantage and open knowledge-based economy across the world that is proficient of sustainable economic expansion with immense cohesion and more and superior job opportunities. The new flexicurity approach is common within the European Employment strategy. The European Employment Guideline 13 formulated in 2001, under the Adaptability pillar, clearly tackle both security and flexibility strategies and also welcomes social stakeholders to mediate and implement appropriate agreements to update the how work is organized, incorporating flexible working programs, with an objective of achieving high productivity, required balance between security and flexibility as well as competitiveness.   Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚   Flexicurity is very vital since appropriate balance between security and flexibility will increase productivity and quality of work, competitiveness and help corporations to adapt to changes in the economy. Flexicurity is important to European employment policies and update of EU labor law especially in the recent economy which is faced by increasing globalization, financial and economic crisis. The position of social dialogue and social partners is greatly emphasized in flexicurity. Swedish industrial relations and labor laws system is based on cooperation between stakeholders, self-regulation and collective bargaining. Collective bargaining is estimated to be 90% and trade unionization is estimated to be about 70 percent. Salaries and other job conditions and terms are set by collective bargaining. European Union member states apply different approaches to flexicurity depending on industrial relations, their labor laws, and social securi ty systems.   Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚   Countries implement the new flexicurity policy with an aim of cutting down market segmentation and enhance changes. Equal treatment of all employees can be attained via values of equal treatment and non-discrimination and appropriate reforms to the guideline of employment security and fixed-term occupation. Flexicurity policies call upon enterprises to make reforms on their existing laws and police in order to accommodate security and flexibility. Functional flexibility has led to a heated debate in the labor markets. In order to come up with effective flexicurity firms should examine the existing internal and external flexibility. Internal flexibility help employees to adjust labor input in case of transitory fall in demand while conserving jobs which are feasible in the long run. Flexicurity poicy can account for the resilience in many European nations especially helping them maintain low and stable unemployment rate. This is because fle xicurity protect employees from income losses connected to key lay-offs and plant closures. However, external flexibility of many firms remained unchanged for the last three decades. Research reveals that income losses of misplaced workers have reduced since the workers can get swift re-employment.   Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚   Flexicurity has faced many criticisms from the people who proposed that flexicurity was developed with an aim of eliminating employment protection legislation, but it encourages a suitable blueprint of employment protection legislation. Open-ended contract between an employee and the employer would be redesigned to incorporate gradual development of job security. The job protection would gradually build-up with the job term, until full job security is attained. The tenure track approach is very significant since it reduces the incidents of employees being trapped in less protected contracts. Reforms of the employment due to economic crisis are aimed at addressing length of procedure, bureaucracy, improve lucidity and make the procedure more dependable. The starting job protection policies may take into consideration notification periods, the procedural phase of dismissal protection and the amount of severance pay.   Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚   European Expert Group on Flexicurity propose that use of fixed-term agreement should be reduced and undeclared work should be cut short as swiftly as possible by raising valuable inspections. It is crucial to acknowledge that outside the sphere of the European Employment plan, the open technique of coordination and Europe 2020 Strategy, the flexicurity policy has not yet brought up fresh legal suggestions associated to employment security. Flexicurity slightly regulate the employment security at EU level with an aim of achieving their main objectives and meet the requirement of member states in areas such as protection of workers whose employment contract is abruptly terminated. EU agreement of Fundamental Rights state that every employee has the right to safety from groundless dismissal as per the national and union laws and policies.   Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚   Flexicurity has been able to increase flexibility in the labor market while at the same time maintaining security via promotion of more employment opportunities and enough ground of employment benefits. Counties with solid employment protections tend to go through fewer incidents of labor market disruptions as compared to nations with weaker employment security. Flexicurity has dominated over the famous Commission’s labor market policy prescriptions. The interest of flexicurity in labor market originated from Netherlands and Denmark which serve as an example. These countries enjoyed the lowest unemployment rates in the global economy crisis in Europe while maintaining adequate unemployment benefits. The main reason was that Denmark and Netherlands emphasized on active labor market measures accompanied by modest employment protection. European Commission has gradually incorporated flexicurity policies when developing its labor market policy instructions and has persuaded the EU members to develop labor market laws that conform to flexicurity plan. In endeavors to direct development of national policy, the commission highlighted four pillars of flexicurity which include: flexible and dependable contractual agreement between employer and employees, comprehensive long-lasting learning scheme to enlighten the workers, successful active labor market policies and updated social security systems.   Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚  Ã‚   In conclusion, flexicurity is a very significant strategy that will help countries to cope up even during economic hardship. Flexicurity also offer the employee allows flexibility at work and at the same time maintaining security. This ensures firms acquire competitive advantage, increase productivity and quality of work and help employees and corporations to adapt to changes in the economy. Nations are called upon to incorporate flexicurity policy in their labor markets so that they can enjoy various benefits associated with this new strategy. However, appropriate measures must be undertaken to ensure there is the required balance between security and flexibility. References Cazes, S., & Nesporova, A. (2006). Flexicurity a Relevant Approach in Central and Eastern Europe.. Geneva: International Labour Office. Flexicurity: perspectives and practice.. (2010). Dublin: European Foundation for the Improvement of Living and Working Conditions. Source document

Fermentation of Carbohydrates: Ethanol from Sucrose Essay

Objective: To demonstrate a fermentation process, isolate the ethanol produced by fractional distillation, determine the composition of the ethanol solution recovered, and make stoichiometric and yield calculations. Procedures: Fermentation Weigh out 20.0 g of sucrose and place it into a 250-mL Erlenmeyer flask. Add 100 mL of water and gently shake until all the sucrose has dissolved. To this solution add 0.60 g of dipotassium hydrogen phosphate (K), 1.8 g of sodium phosphate hydrate (Na3PO4ï‚ ·12HO) and 2.0 g of dried baker’s yeast. Vigorously shake the contents to mix them thoroughly. The Erlenmeyer flask is fitted with a one-hole rubber stopper containing a short piece of glass tubing. Latex tubing (8 -12 in.) is attached to the glass tubing. An overhand knot is loosely tied in the tubing. The low part of the loop is filled with just enough water so that the passage is blocked, but gas from the fermenting chamber will be able to push the water out of the way and escape (brewers call this an airlock). This setup excludes air (and oxygen) from the system (which allows anaerobic oxidation) and prevents further oxidation (by aerobic oxidation) of the ethanol to acetic acid. Label the fermentation setup with you r name and place the flask in the incubator chamber Isolation by Fractional Distillation Do not shake the flask; avoid disturbing the sediment on the bottom! Get your flask from the incubator bath or chamber. Carefully remove the rubber stopper from the 250-mL Erlenmeyer flask. Prepare a vacuum filtration assembly using two 250-mL side-arm filter flasks, a 5.5-cm Buchner funnel (with a Filtervac or neoprene adapter), and two lengths (each 12 in.) of vacuum tubing. [N.B. We use the second flask so between the aspirator and our filter flask so that the filtrate will not become contaminated if tap water is pulled back through the hose.] Place a piece of filter paper into the Buchner funnel so that it covers all the holes and lies flat. Into a  250-mL beaker, place 100 mL of water and one tablespoon of Celite. Stir vigorously and pour the mixture into the Buchner funnel while the water is running and a vacuum is applied. A thin layer of the Celite Filter Aid will form on the filter paper. Discard the water collected in the filter flask. Do not suck too much air through the filter pad; if it dries, it may crack and be unusable. Carefully decant the liquid in the fermentation flask above the sediment through the Celite Filter Aid, using suction. This technique traps the small yeast particles in the Celite Filter Aid but lets through water, ethanol, and any other liquid impurities. This liquid filtrate will be distilled. Obtain a distillation setup and assemble the glassware for distillation. Note the placement of the thermometer bulb in the adapter take-off to the condenser. Securely clamp the apparatus and condenser, and secure joints with plastic clips. Use a small dab of silicone grease on all the standard-taper joints as you connect them. Collect the distillate in a graduated cylinder. Use a round-bottom distilling flask that will be filled approximately one-half to twothirds full; a 250-mL round-bottom flask should do. Add 2-3 boiling stones to the flask. Use a heating mantle for the heat source and a Variac to control the heat. Your mantle may have a built in voltage controller. Gradually turn up the heat until the liquid in the distillation flask begins to boil. As the vapors rise in the head, you will see liquid condensing; this ring of condensate will rise in the column. Control the setting on the Variac so that the condensate rises slowly through the column and at an even rate. (If the rate is too fast, the column will flood.) The temperature readings at the distillation head will rise; when the temperature reaches (about) 78 °C, begin to collect the liquid that distills. Discard any liquid distilling before this temperature is reached. Collect liquid distilling between 78 and 90 °C. Collect 10-15 mL of distillate. Turn off the heat source and remove the heating mantle from the distillation flask. Weigh a 50-mL beaker to the nearest 0.001 g. With a 10-mL volumetric pipet, transfer 10 mL of distillate to the beaker (V). Do not pipet with your mouth; use a pipet bulb. Reweigh the beaker and liquid (5), and by difference, determine the weight of the distillate. Determine the density,  and by referring to the graph, determine the percent composition of the ethanol.

Interview Tucker Max dishes on the state of publishing

Interview Tucker Max dishes on the state of publishing "How I made Simon Schuster give me my own publishing company:" An Interview with Tucker Max As you probably know if you’re a frequent reader of this blog, there are now many ways to bring a book to market. Whether it’s in print or digital, self-published or through a publisher, with or without an agent, the choices available to a new author is almost mind-boggling. Tucker Max is different. As the author of I Hope They Serve Beer in Hell, he ignored all the options available to writers and made publishers do what they’d never done before - give an author their own publishing company.In these times of great change, it's possible for authors to forge their own path - as Tucker did by picking and choosing the elements of self-publishing and traditional publishing that make the most sense for his book.Watch our interview with Tucker - or read the transcript below - for some inspiration! How publishing worked 15 years agoHi Tucker, it’s great to have you with us today. Let’s start from the beginning - can you tell us from the early days when you started to write and wanted to get your stories out into books?Tucker: Yeah, I started in writing in a totally different era (2001). I used to send emails to my friends, and they thought they were really funny. They kept telling me, †you need to publish this. This needs to be a book." Question 3: Why is that audience going to care? What are you going to say that's interesting and valuable to them?If you cannot answer those three questions clearly, then don't write a book.Now let's say you can answer those three questions. I would say that for almost all non-fiction, the best bet is to self-publish. That way you get to control the rights to the book, and you can use it to promote whatever it is you're trying to promote. As soon as you go traditional, you have now sold the rights and royalties to that book to someone else. So you can't give copies away. If you're trying to do speaking gigs with the book, you've got to buy the book at price from your publisher.If you want to do excerpts, if you want to use the content other places, you don't own the content anymore, the publisher does. And they don't care about your business at all. They care about selling actual copies of the book. So for most non-fiction authors, their goals are not aligned with a publisher’ s goals. So that's why going self-publishing is the better route, for almost all non-fiction authors.Photo credit:  Mac Danzig.If you're a non-fiction author, do you agree with Tucker's take on publishing? What has been your experience of working with a traditional publisher, if any? Let us know your thoughts in the comments below.

Die Theory essays

Die Theory essays The industrial art of manufacturing consist of many catergories like stamping dies, plastics molds, and jigs and fixtures to be used in the mass production of solid objects. I have experienced working on a press with sheet metal. My job was to slide the sheet metal onto a pressworking die and place the palms of my hands on a sensor so that the press would then stamp the sheet metal into a predetermined shape. Next, I had to slide it onto the next die for the next shape to be made. The pressworking dies in the factory would range from extremely small to gigantic;but the press that stamps out the roof of a car is about three stories highand capable of exerting tons of force. The manufacturing of plastic molding is quite similar to that of stamping dies. The principal difference is that stamping requires force, while molding does not. I recently graduated from a machinist training program in Detroit: (Focus Hope Machinist Training Institute), and we worked on several different machines such as the Lathe, Grinder, CNC mills, and a software system called Auto Cad. After that program I began to understand the importance of machine tools in the industry; having the skill to operate machines and design parts on the computer (Auto Cad). I really enjoyed working on these machines such as the grinder machine which removes small chips from metal parts that are brought into contact with a rotating abrasive wheel called a grinding wheel or an abrasive belt. The sparks that the grinder generates from the part could be considered cool to look at if your not the person grinding. One machine that I did not enjoy working on was the Press. This large class of machines includes equipment used for forming metal parts byapplying the following processes: shearing, blanking, forming, drawing, bending, forging, flanging, squeezing, and ...

Making A Successful And Thus A Good Team Essay Example | Topics and Well Written Essays - 1000 words

Making A Successful And Thus A Good Team - Essay Example Mainly organizations understand that being principled is high-quality business performance and pays in the protracted run. To be moral needs taking care of others, which includes, consumers and staff, appropriately and moderately. An organization that is involved in expansion and profits must create dealings with customers and employees supported on faith. Development of the employer-employee affiliation is significant to both parties for quite a few motives (McShane & Glinow, 2004, Pp 415-417). Are you confronting your first team-building session Do you doubt what you will do How to start According to Biech (2001, Pg 72-73) Team building is an organization development involvement that provides teams an opportunity to silence in their daily work to examine what's working and what could be improved. The consultant's role in team building is one of process guide, not content expert. This article provides insight into that role. It helps the consultant understand the goals of team building and how it differs from team training. The activities and norms developed in team-building sessions are different but complementary to that characteristic of management-training and skill-building sessions. Concepts such as leadership styles, decision-making, communication patterns, motivation, competition, and morale are all relevant to the process of team development. Improved Communication The basis for almost any problem in any organization is usually communication. Good teamwork can widen the circle of communication. Teamwork goes a step beyond, however, and helps people understand each other's jobs and roles in the organization. This leads to an appreciation for colleagues and a desire to help make their jobs easier. Personal Satisfaction Team members generally report a sense of personal satisfaction. A team may provide a sense of security that allows individuals to take risks and make decisions that they would not make if they were working alone. This generally leads to growth for the organization as well as the individual. Because most of us spend about 25 percent of our lives at work, it should be a pleasant experience. Teamwork can lead the way to making work pleasurable by helping to develop personal relationships. In fact, you should not feel as if you are getting up to go to work, but instead that you are getting up to go to play each day! Clear Goals Clearly defined goals are essential so that everyone understands the purpose and vision of the team. You might be surprised at how many people do not know the reason they are doing the tasks that make up their jobs, much less what their team is doing. Everyone must be pulling in the same direction and be aware of the end goals. Clear goals help team members understand where the team is going. Clear goals help a team know when it has been successful by defining exactly what the team is doing and what it wants to

Brain-based Learning Essay Example | Topics and Well Written Essays - 500 words

Brain-based Learning - Essay Example Since the brain has a finite amount of storage space, it attempts to connect and reconcile new information with previous information. The ultimate result of this process is a blending into general concepts called schema. As we acquire, process, and store more information concerning a specific schema, the neural connection grows and learning takes place (Hardiman, 2003; Huitt, 2003). While the specifics of the schema-forming process are not yet known, research in language acquisition has shown that humans are genetically predisposed to process information in specific ways. Thus scientists have created several learning theories which attempt to better explain the specifics. One such prevailing theory is the levels of processing theory which says that "learners utilize different levels of elaboration as they process information. This is done on a continuum from perception, through attention, to labeling, and finally, meaning" (Huitt, 2003, p. 1). But what does this mean in the classroom Educators must realize that students come to them with perceptions about life and school already in place. Skillful teachers will attempt to find out where their students are coming from and what prior knowledge they have before introducing new information. Review activities should be provided so students with a chance to repeat a specific learning task.