Order 1105093: Project Management

Project Management 11

TESCO PROJECT MANAGEMENT

By []

Course

Professor’s Name

Institution

Date

Executive Summary

Project management is an essential element in project initiation, planning, development, execution, and control. It involves the use of tools and techniques to ensure project success promptly. Tesco company, in its quest to improve the customers’ security and satisfaction, incorporated Agile methodology to develop Club card which became efficient, more straightforward and more accessible for users. This paper discusses project management in a broad perspective, agile methods, and principles, management theory, the application of the Agile methodology to Tesco project, impacts of the model, solutions to problems and a detailed conclusion.

Project Management

Project management refers to the organizational practice of initiating, planning, executing and control of a project to meet the desired organizational goals and objectives set by the management team. It involves the initiation of a plan to produce a unique product or service for a scheduled period, with minimal cost and high quality (Maylor 2010). For a project to be successful, technical skills, as well as strong management strategies, are required. Projects’ nature differs from usual business operations as they do not involve repetitive or rather permanent activities or services.

Project Management Objectives

Project management is an essential discipline which aids in project development, and it also helps an organization achieve its success through the creation of new services and products (Atkinson 1999, p.339). However, project managers are required to deliver high quality services or products consistently by following specific objectives such as Cost, time, scope and quality. These are discussed below;

The Triple Constraint Concept

This is the most crucial concept in project management unfolding the objectives of a task. This constraint is significant because it provides a suitable framework to be adhered to by the project team thus driving the project forward (Burke 2010). It also offers room for adjustment whenever the project framework needs to be modified. It enables managers to know the direction of the project as well as get an insight on trade-offs and their impact on other managerial aspects. Moreover, constraints such as cost, scope and time can be easily tracked and monitored thus contributing to the success of the project.

Cost

This refers to resources, materials, labor costs, fixed and variable costs that are required for project development. Cost management involves total estimation and calculation of all financial commitment necessary for project development and completion. The cost estimated should be effective and efficient. For instance, budgeting helps in controlling cost baseline whereas techniques such as cost control help manage and control cost fluctuations that may arise throughout the development process. There are several methods of cost estimation and power such as the use of historical data for project comparison, resource costs in determining labor rate and reserve costs technique among others (Koo 2004, p.,155).

Scope

This deals with the requirements necessary for project completion. It is essential for project managers to timely manage the scope of the project to deliver it on time and under the desired cost budget (Koo 159). Project scope can be managed by the use of software such as agile or waterfall. Effective scope management involves task prioritizing as well as handling stakeholder expectations that may arise during project implementation. It also involves managing change requests that are in line with the project goals.

Time

This is the estimated period for project completion. It involves monitoring and noting tasks movement or progress from the start to the end. Efficient time management involves the use of a Work Breakdown Structure(WBS) to break the project into simple manageable and workable tasks which are then prioritized and placed on work timeline (Serrador 2015, p. 1049). For project visualization, a Gantt chart can be used showing the task timeline, dependencies, and durations. A project schedule can be managed through the following time management processes: Plan schedule management, the sequence of activities, estimation of activity resources and durations as well as scheduled development among others.

Quality

The quality of any project is constrained by the cost estimates of the project, time frame, and scope.

Differences Between Project Management and General Management

Project management refers to the initiation, planning, execution and controlling the work of a project team to achieve desired organizational goals to meet specific success cities at a specified period. On the other hand, general management refers to the overall planning, executing, delegating, staffing, organizing and decision making of all operations of a company or organization to ensure profit maximization (Sayles 1979, p. 6).

A project manager’s role is temporary while that of a general manager is wider in scope and involves more responsibility. The operations of general management require the team members to report directly to the team manager while the team members of a project team may even report to departmental managers and current project managers (Lewis and James 2005). A general manager has the duty and mandate of creating and enhancing good teamwork, setting group norms, ethics and behaviors, encouraging a joint decision making as well as setting target appraisals on the performance of team members. This is contrary to a project team which is composed of people from diverse departments across different organizational sites. General management practices involve product/service delivery while those of project management majorly lies in project execution. Also, general management involves a broad scope of objectives whereas project management involves a single and clear objective, that is, project implementation.

Project Management Model

This is a simple process model managers use in executing projects. These are briefly discussed below;

Define; It involves a clear definition of the project background, setting project intervention aims, development of objectives and determination of timescale and milestones.

Design; This involves efficient planning to achieve desired project objectives, value addition and track preparation to capture the details of working events.

Deliver; This entails carrying out of events or activities, capturing and recording data as well as providing timely feedbacks and reviewing progress against the drawn plan.

Develop; After the project is delivered, development is done to test its service/product, refining the project for the next cycle and operational improvements.

Agile Methodology

This refers to a skilled approach to managing Information Technology and software development for projects. It is a powerful tool that helps in streamlining the project development process, software creation and enhancing customer satisfaction (Michael et al. 2004, p. 8).

Principles of Agile Methodology

· Effective collaboration between developers and business stakeholders which lead to an enhanced decision-making process.

· Enhanced customer satisfaction through the use of updated software delivery. For instance, customers become happy upon receiving working software continuously at regular time intervals unlike waiting for long periods.

· Face-to-face Interactions; This principle revolves around effective and efficient communication among the stakeholders and developers to achieve success.

· Motivation, support, and trust among the people involved; Individuals who are motivated are much likely to deliver to their level best, unlike unhappy team.

· Enhanced attention to technical detail and design; This helps in delivering a quality product as well as continuous product development and improvement in customer satisfaction and company success.

The effectiveness of the Methodology

· The model is flexible to change thus accommodating implementation of new changes at a low cost.

· It saves time; The model can be easily implemented in a short timeframe or period.

· The process involves limited planning to get started with a project.

· The model also gives the business stakeholders and developers more time freedom because of its rigid sequential manner.

Management Theory

This is a concept of science and art involving the collection of ideas used to plan, execute, control and run a business project. It addresses the relationship between managers and stakeholders of an organization on how to effectively accomplish the desired goals and objectives as well as employee motivation to enhance employee delivery and performance to the highest standard levels (Meredith 2012). Management theory is divided into four parts;

Scientific Management Theory

According to Frederick Taylor (1995), the scientific management theory uses measurements and data to improve the operations of an organization. For instance, managers observe and evaluate the project processes in numerical terms to acquire vital information to help them run the business operations efficiently and profitably.

Human Relations Theory

This theory emphasizes the importance of aligning employee needs to achieve higher levels of performance. It is human-centered and covers the welfare of employees in an organization (McGhee and McAliney 2007, p. 74). Employees should be treated fairly; they should be entitled to wages and salaries, motivated and provided with a good working environment for good health and safety condition.

Systems Theory

This involves an integrated and holistic pattern in the scientific and metaphysical context. It aims in achieving a balanced business operation through identification of organizational goals or objectives, a clear understanding of operation cycles and outcomes as well as leveraging a company’s flow of operations (Kostelac et al. 2001).

Bureaucratic Management Theory

According to Max Weber (2010), this theory emphasizes on employee roles and those of the management based on a system of hierarchy that helps streamline authority of responsibility of different tasks.

Management Theory Objectives

· Motivation; This objective involves employee engagement in the decision-making process and incorporating their ideas into the goal-setting process. This helps improve employee involvement, empowerment, and commitment resulting in job satisfaction.

· Efficient and effective communication; This helps maintain interactions and relations among the developers and stakeholders.

· There should be a precise clarification of organizational goals.

· A common goal for the benefit of the organization as a whole.

Introduction of Agile Methodology

Automated software testing is one of the efficient modes of testing today. It helps eliminate or rather reduce human labor in test processes. In 2001, the Agile methodology was developed by a group of individuals with the aim of improving and managing software projects. Its manifesto was to increase customer collaboration, respond to systematic changes and to replace comprehensive documentation (PMBOK 2004, p. 165).

Components

Scrum Methodology; This framework helps control the iterations and increments of all project types. They are proven to have a higher productivity rate and are more popular.

Crystal Methodology: This is composed of several Agile processes such as crystal yellow, crystal orange. They are unique with lightweight and adaptable approaches. Due to this, the methodology focuses on the realization of diverse projects with unique characteristics.

Dynamic Systems Development Method(DSDM); This methodology was developed in 1994 as Rapid Application Development(RAD) but later on its operating system improved. Currently, the model provides an extensive foundation in planning, execution, management as well as scaling of the entire Agile process (Shenhar et al. 1997, p.9).

Pros and Cons of the Agile Methodology.

The methodology is useful in enhancing the delivery of useful software. It also enhances interactions between customers, testers, and developers. The working software is delivered continuously, and frequently thus it is time efficient. It is flexible enough to accommodate changing circumstances. However, this model poses some disadvantages such as inadequate assessment of large deliverables, lack of a clear emphasis on project documentation and design and lastly, it lacks a new place for newbie programmers.

Application of Agile Methodology to Tesco Project

Tesco is one of the world’s largest online website experiencing growth of about $2 billion annually. In 2010, the company accustomed and build online orders where customers could place their orders on their mobile platforms such as Nokia, IPad, Windows7 among others. The agile model was adopted to ensure success by integrating offshore teams and third parties. The model made it possible for the company to set up tools and backlogs used for integration, collaboration, and incorporation. It was easy to adopt the model with a relatively high proportion of external and expertise (Gentile et al. 2005, p. 172).

Pros of Agile Methodology

· The model helped in synchronizing advert campaigns thus streamlining the business development process as well as time management of scope.

· It enabled the company to come up with new solutions outside the entire business.

· It works well with an integrated group of individuals: third parties, onshore and offshore teams as well as business stakeholders.

· It increases collaboration and interaction among the development and marketing team thus leading to enhanced exploration of new technological opportunities.

· The Agile development approach has helped in mobile application development leading to increased product marketing and definition.

Cons of Agile Methodology

· Performance and reliability problem; This aroused when the API systems developed through innovation were not properly tested thus causing poor performance.

· The was poor management of the varied and multiple stakeholders which resulted in clashes between them on task prioritization.

· The Agile model lacks flexibility. The Tesco team was faced with difficult while trying to anticipate from the innovation project to a development one.

The methodology is good for the project because the club card helped improve and increase customer' security and loyalty. It enabled the firm to monitor the response of their customers.

Recommendations

· The company should work on its management structure to ensure continued operations among the parties.

· Tesco company should work on its integration and legacy software to improve on the performance of the mobile platforms when tested.

· The management team should ensure a backlog task priority based on a clear and transparent criterion to avoid clashes among the team members.

· Further improvements should be made to the Agile model to allow anticipation and movement from an innovation project to a development project.

Conclusion

Project management is essential in task planning, initiation, execution and controlling. Project managers should ensure a well-planned schedule is adhered to while implementing projects. Important aspects such as cost, scope, time and quality are essential for project success. For instance, Tesco company implemented the Agile model in preparation for club cards which improved their customers’ satisfaction level as well as enhancing security and loyalty. The agile model was effective and successful; however, there is need to fix further the challenge of transitioning the mobile projects through innovation to more business practices such as Business as Usual(BAU) process which integrates less urgent works. Another challenge arises where the organization Lacks appropriate budgeting within the mobile projects thus leading to a wider project portfolio (Ralph et al. 2014). The integration tool used by the quality assurance team remains a challenge to many mobile platforms.

It Is Havard style referencing so this should be in alphabetical order and where the information was accessed from.

References

Sayles, Leonard (1979). Leadership. New York: McGraw-Hill, Inc. P. 6. ISBN 0-07-055012-3.

APM, (2013), APM Body of Knowledge, 6th Ed.

PMI (2013), A Guide to Project Management Body of Knowledge (PMBoK Guide) 5th Edition

PMI (2017), A Guide to the Project Management Body of Knowledge, PMBoK Guide, 6th Edition (E-book)

 Burke, R., (2010), Fundamentals of Project Management, Burke Publishing

Meredith, J. R., and Mantel, S. J., (2012), Project Management – A Managerial Approach, 8th Ed., Wiley International.

Serrador, P. & Pinto, J. K., (2015) Does Agile work? — A quantitative analysis of agile project success, International Journal of Project Management Vol 33, pp 1040–1051.

Maylor, H., (2010), Project Management, 4th Ed., Prentice Hall

Atkinson, Roger (December 1999). "Project management: cost, time and quality, two best guesses and a phenomenon, it’s time to accept other success criteria." International Journal of Project Management. 17 (6): 337–342. doi: 10.1016/S0263-7863(98)00069-6.

Erik Bethke (2003). Game Development and Production. p.65.

Michael W. Newell, Marina N. Grashina (2004). The Project Management Question and Answer Book. p.8

Pamela McGhee, Peter McAliney (2007). Painless Project Management. p.74.

Michael Gentile, Ronald D. Collette, Thomas D. August (2005). The CISO Handbook. p.172

Ralph, Paul; Kelly, Paul (2014). "The Dimensions of Software Engineering Success." Proceedings of the 36th International Conference on Software Engineering. ACM: 24–35.doi: 10.1145/2568225.2568261.

Shenhar, A.; Dvir, Dov (1997). "Mapping the dimensions of project success." Project Management Journal. 28 (2): 5–13.

Lewis, James P. (2005). Project Planning, Scheduling & Control, 4E. McGraw Hill.

ISBN 978-0-07-146037-8.

PMBOK Third Edition 2004 p.165

Project Management Institute (2009). A Guide to the Project Management Body of Knowledge: PMBOK Guide. Chapter 1

Koo, B. 2004. “Formalizing Construction Sequence Constraints for the Rapid Generation of Scheduling Alternatives," CIFE Technical Report No. 155, January 2004.

Kelsey, J. Winch, G, Penn, A. 2001. “Bartlett Research Understanding the Project Planning Process: Requirements Capture for the Virtual Construction Site, VIRCON, Paper 15.

Kostelac, L. and Howell, G. A. 2001. “Reforming project management: the role of planning, execution and controlling.”

Sriprasert, E. and Dawood, N. 2002. “Requirements identification for 4D constraint-based construction planning and control system. “Proceedings of CIB w78 Conference, Aarhus, Denmark.