Best practices in project quality management/leadership for IT Essay

1. 0 Introduction Most people plainly accept scurvy persona from many reading technology (IT) products. So what if ones laptop crashes a couple of times a week? Just ensure there is back up for data. So what if one can non log in to the business intranet or the earnings right now? Just attempt a little after when it is less busy. So what if the latest version of word-processing software product was shipped with several bugs? One may like the softwares new features, and all new software has bugs.Is quality a real problem with information technology spews? Yes, it is IT is not just a luxury available in some offices, homes, or schools. Firms end-to-end the world provide employees with access to computers. The majority of people in the US use the internet, and usage in opposite countries continues to expand rapidly. It took save six years for 60 million people to use the internet compared to 20 years for 60 million to use cell phones (Kathy, 2008, p. 292). Many issues of indivi dual and or crowd lives search on high-quality IT products.Food is produced and distributed with the help of computers vehicles have computer chips to monitor performance students use computers to attending them learn in school disposals depend on technology for many business functions and millions of people depend on technology for entertainment and individual communications (Kathy, 2008). Many IT reckons develop mission-critical systems that are utilized in life-and-death circumstances. Such as navigation systems on aircraft and computer components built into medical equipment.Financial institutions and their clients likewise depend on high-quality information systems. Clients get very upset when systems present inaccurate data or display information to unauthorized people that could result to identity theft. When any of these systems fails, it is much more than a mere inconvenience (Taguchi, 2004). 1. 1 Definitions Before one can enhance the quality of IT projects, it is n ot bad(predicate) to reckon the fundamental concepts of project quality charge. Indeed, it is hard to define project quality management.According to the international organization for standardization (ISO) quality can be defined as the totality of features of an organization that bear on its ability to satisfy stated or implied requirements (Kathy, 2008). It can also be defined as the accomplishment to which a set of inherent features fulfils needs (ISO9000). Other professionals define quality based on estimation to needs and fitness for use. Adherence to needs means projects products and processes meet laid conquer specifications. Fitness for use implies a product can be used as it was intended.The purpose of project quality management is to make sure that the project will fulfill the requirements for which it was undertaken. Project management involves among others things come across or surpassing stakeholder requirements and anticipations. The project group moldiness initiat e good relationships with core stakeholders, especially the elementary client for the project, to comprehend what quality implies to them. Many technical projects fail because the project management group aims only at meeting the written requirements for the project (Juran and Frank, 2002).Quality, therefore, must be on an equal basis with project scope, cost, and time. If the projects stakeholders are dissatisfied with the quality of the project management or the end products of the project, the management group will require adjusting time, cost, and scope to fulfill stakeholder needs. In which case meeting only authenticated requirements for time, cost, and scope is not sufficient. To attain stakeholder fulfillment, the project group must come up with a good working relationship with all stakeholders and comprehend their implied or stated requirements.Best practices over the years, organizations have draw mesmerized with the term- beaver practice-but after continued use, expert s began scrutinizing the expression and now better definitions exist. A high hat practice starts simply with an idea. Knowing that there is a process, tool, activity, or method that can deliver results effectively than any other method and provides one with the desired results with less barriers and predictable complexities is a welcome.As a result, one seemingly ends up with an efficient way of completing a task by use of a repeatable procedure that has stood the test of time for quite a large number of IT projects (Kathy, 2008). As project quality management evolved, so did the meanings of high hat practices. Some definitions of best practices are complicated while others are in some manner simple. Yet, they both address the same aim of encouraging project quality management throughout the organization. Firms must decide on the depth and extent of their best practices.Must it be at high train and generic or at a low level and detailed? A generic best practice may not attain the desired efficiencies whereas a detailed one may not have unlimited applicability. Basically, any firm can decide to have own definition of best practices and there might even be company quality requirements on the definition of such best practices. For example, a best practice can be defined as something that works, works healthful, works well on a repetitive basis, leads to a competitive advantage, can be identified in seeking to improve business, and prevents the firm from problems.