Project Management

Project management is the profession of planning, organizing and managing resources to achieve the success of achieving specific goals and objectives of the project.

According to research, in line with the analysis conducted by FEDERATION OF EWOVICO COMPANIES, we have agreed with these that:

Projects can be long-term or short-term.  In practice, the management of these two systems is often found to be completely different, and therefore requires the development of different technical skills and embrace different management.

A project is a short-term endeavor, with a known beginning and end (usually tied to a date, but can be tied to money or expected results), made to achieve certain goals, usually to bring about beneficial or value-added changes.  The nature of projects to be short-lived is the opposite of a regular business (or operation) that is repetitive, with permanent or non-permanent performance to manufacture a product or service.

The basic challenge of project management is to achieve all the project objectives and project objectives while respecting the previously identified project constraints is crucial.  Common constraints are scope, time, and budget.  An insignificant challenge — and with the highest goals — is the challenge of balancing the sharing and integration of inputs to achieve previously set goals.

 

PROJECT MANAGEMENT HISTORY

Project management has been implemented since the beginning of civilization. By 1900 the engineering projects associations were generally managed by the creative architect s and the engineer s themselves, among them for example Vitruvius (1st century BC), Christopher Wren (1632-1723), Thomas Telford (1757-1834) and the Isambard Kingdom . Brunel (1806 – 1859)  It was in the 1950s that organizations began projecting systemically using management tools and techniques and complex projects.

 

As a subject, Project Management grew from a variety of application areas including construction, engineering, and defense activities. The founders of project management are Henry Gantt, the so-called father of strategic planning and management who is renowned for his use of the Gantt chart as a project management tool; and Henri Fayol for his creativity of five management activities that form the basis of a series of knowledge related to project and program management. Gantt and Fayol were students of Winslow Frederick Taylor’s theory of scientific management. His work is the forerunner of modern project management tools as well as the breakdown structure (WBS) and resource allocation.

The 1950 decade marks the beginning of the modern Project Management era. Project management was officially recognized as a special subject derived from the management subject. In the United States, prior to the decade of 1950, projects were managed through a fast-tracking system specifically for the use of Gantt Charts, informal methods and tools. At that time, two mathematical models for project planning were created. The “Two-Way” (CPM) was formed as a joint venture between DuPont Corporation and the Remington Rand Corporation to oversee industrial construction projects. “Program Evaluation and Repetition Method” or PERT, developed by Booz-Allen & amp; Hamilton as part of a submarine and missile program called Polaris of the US Navy (in partnership with the Lockheed Agency);

PERT network chart of project with five major successes

Meanwhile, as project planning models were developed, project cost-cutting technology, project management, and economic engineering were changing, thanks to the earlier works of Hans Lang and others. In 1956, the United States Association of Cost Engineers (called AACE International; Development and Cost Engineering Agency) was formed by early project management executives and specialized agents of planning, costing, and cost / schedule control. (Project management). AACE continued its founding work and in 2006 released the first integrated procurement, programming and project management plan (Integrated cost management strategy).

The International Project Management Association (IPMA) was established in Europe in 1967, as a federation of several international project management associations. To date IPMA has maintained its federal structure and now includes relevant parties in every continent except Antarctica. IPMA provides four-level Program Guarantee based on IPMA (ICB) Competitiveness https://www.ipma.ch/publication/Pages/ICB-IPMACompetenceBaseline.aspx Archived 6 December 2009 at the Wayback Machine .. ICB includes technical principles, completeness of contextual norms and completeness of ethical principles.

In 1969, the Project Management Institute (PMI) was created in the United States. PMI publishes a Knowledgeable Project Management Guide (PMBOK Guide), which outlines project management practices that are common in “many projects, most of the time.” PMI also provides many previews.

Project management techniques

There are several approaches to managing project activities including flexible, interactive, scalable, and multi-step approach.

Regardless of the method used, it is imperative to take into account the overall purpose of the project, the time, and the cost, as well as the roles and responsibilities of all stakeholders.

Traditional approach 

The traditional multi-step approach includes steps that need to be completed. In the “traditional approach”, we can distinguish 5 project components (4 steps and add control) in project implementation:

Common phases in project implementation

• Step to start a project;
• The process of planning or drafting a project;
• Action stage or project implementation.
• Project monitoring and control systems;
• Steps to complete a project.

Not all projects will go through every step because projects can be interrupted before they are completed. Some projects do not follow the planned structure and / or monitoring stage. Some projects will go through stages 2, 3 and 4 multiple times.

Many industries make small changes in these stages of the project. For example, when the work of drafting and making bricks and building mortar is done, projects usually go through developmental stages such as Preliminary Plans, Draft Ideas, Draft Decisions, Development Bureau, Construction Drawings (or Contract Documents), and Construction Management. In the manufacture of, software, this technique is often referred to as a waterfall pattern i.e., a sequence of tasks, one after the other in sequence. In software development many organizations are developing a Unity Thinking Movement (RUP) to complement this approach, although RUP does not need or explicitly recommend this exercise. The waterfall technique in manufacturing works well for small identified projects, but they often fail in large-scale projects that are unpredictable and of mystical origin. Uncertainties explain some of this as the planning done in the initial phase of the project suffers from a high degree of uncertainty with the effect of uncertainty. This is especially true because software development is often the realization of a new product or novel. In projects where requirements are not met and can be changed, demand management is used to promote accurate and complete software characterization that can be used as a basis for software development Although issues may vary from one manufacturing sector to another, a good guide follows the usual problem solving – “defining a problem, evaluating options, choosing methods, implementation and evaluation.” Uncertainties explain some of this as the planning done in the initial phase of the project suffers from a high degree of uncertainty with the effect of uncertainty. This is especially true because software development is often the realization of a new product or novel. In projects where requirements are not met and can be changed, demand management is used to promote accurate and complete software characterization that can be used as a basis for software development although issues may vary from one manufacturing sector to another, a good guide follows the usual problem solving – “defining a problem, evaluating options, choosing methods, implementation and evaluation.” Uncertainties explain some of this as the planning done in the initial phase of the project suffers from a high degree of uncertainty with the effect of uncertainty. This is especially true because software development is often the realization of a new product or novel. In projects where requirements are not met and can be changed, demand management is used to promote accurate and complete software characterization that can be used as a basis for software development although issues may vary from one manufacturing sector to another, a good guide follows the usual problem solving – “defining a problem, evaluating options, choosing methods, implementation and evaluation.”

Key Project Management Necklace 

The Key Project Management Framework (CCPM) is a project planning and management process that places more emphasis on the resources (physical and human) needed to carry out project activities. It is the use of Objective Theory (TOC) in projects. The goal is to accelerate the implementation of activities (or completion standards) in organizational projects. The use of the first three of the five steps targeted by the TOC, recognizes the systemic constraint of all projects as well as resources as well. In order to make good use of a particular barrier, activities on the necklace are given priority over all other activities. Finally, projects are planned and managed to ensure that resources are ready when key chain responsibilities must begin, and to direct all other resources to the key chain.

Regardless of the type of project, project planning must go through resource balancing, and a long chain of resource-intensive tasks, identified as a key chain. In the context of most projects, resource balancing must be done between projects. However, it is often enough to identify (or simply appoint) one “barrel” of resources – a resource that is a barrier to all projects – and to plan projects based on the availability of that one resource.

Planning cycles and results fast software development (XP) and timely multiple cycles.

Small project management 

In key Project Management studies, it has been found that some of these PERT-based models are not suitable for many joint projects in today’s corporate environment. A large number of them focus on very large projects, which are temporary, and unusual, and nowadays all types of management are displayed in project form.

Using complex models for “projects” (or “Activities”) that last several weeks has been proven to result in unnecessary costs and limited flexibility in a number of cases. Instead, project management experts try to identify different “light” models, such as flexible Project Management techniques including Dubwana Software Writing and Scrum technique.

Integration of Software Writing Writing with other projects is a duplicate project management, which can be used in conjunction with examples of processes and principles of human relations management.

Event Necklace Method 

An event chain approach is another way to support key approaches to important project management techniques.

An event chain approach is used to create examples of uncertain events and scheduling network analysis methods that aim to identify and manage events and a chain of events that affect project schedules. The event chain approach helps to minimize the negative effects of psychological rules and preferences, as well as allows for the easy manufacture of models of uncertain events in the project schedule.

The chain necklace technique adheres to the following principles.

• Potential risk time: Activity (work) in many real-life processes is not a uniform ongoing process. Activity is affected by external events, which can occur at some point in the middle of a task.
• Event chains: Events can lead to other events, which will create an event chain. These event chains can significantly affect project progress. Statistical analysis is used to determine the increasing impact of these event chains on the project schedule.
• Key events or event chains: One event or event chain with the greatest potential to affect projects is “important events” or “important event chains.” They can be determined by analysis.
• Monitoring projects with events: Even if the project is relatively complete with data about project length, cost, and events available, it is still possible to get information about future events and helps predict project performance.
• Event Chain Reflection: Events and event chains can be visualized using the event chain diagrams on the Gantt chart.

PRINCE2 

PRINCE2 is a project management framework approach, introduced in 1996 as a flexible approach to project management. It combined the actual PRINCE technique with the MITP method (overseeing the implementation of an adequate project) by IBM. PRINCE2 provides a way to manage projects with a defined strategy. PRINCE2 describes the procedures for coordinating people and activities in a project, how to design and manage the project, and what to do if the project needs to be modified if it does not proceed as planned.

In this approach, each process is estimated by the inputs and outputs and the specific objectives and activities that need to be implemented. This allows automatic control of any query that avoids it from the set program. Divided into manageable measures, this process facilitates adequate resource management. On the basis of close monitoring, the project can be implemented in a controlled and planned manner.

PRINCE2 provides a common language for all project participants. The various Management roles and responsibilities involved in the project are fully defined and can be adjusted to suit the complexity of the project and organizational skills.

Process-based management

Example of Capacity and Maturity measurement, preceding the CMMI model

In developing the concept of project management there is the integration of process-based management. This area has been driven by the use of mature models such as CMMI (Integrated Mature Model Experimental Model) and ISO / IEC15504 (Spice – Program Process Improvement and Capacity Testing) .

Projects for Management Project evolving based on the management of human relations are fundamental to the process of viewing human cooperation. This is in stark contrast to traditional methods. In a software development approach using a flexible approach or a flexible product design approach, the project is seen as a series of small tasks considered and implemented as the situation demands in a flexible manner, rather than as a completely planned process.

Project Development Steps

Typically, project development involves a number of components: four or five steps, and a control system. Regardless of the method used, the process of implementing a project has major steps that are consistent.

Project implementation steps & lt; ref name = “VA03” & gt; VA Information and Technology Office (2003) Project Management Guide DEPARTMENT OF RETIRED ACTIVITIES ACTIVITIES. March 3, 2005. & lt; / Ref & gt;

Key steps usually include:

• Getting started
• Planning or development
• Manufacturing or implementation
• Monitoring and Verification
• Fasting

In a project environment with an important component that needs to be addressed (e.g., Research and development), these steps can be complemented by decision areas (go / go) where project continuity is discussed and decisions are made. An example is Stage-Gate Imitation.

Start

Process Establishment Process Groups & lt; ref name = “VA03” / & gt;

The starting point determines the nature and scope of development. If this step is not done properly, it is unlikely that the project will be successful in meeting the business needs. The key project controls required here are those to understand the business environment and to ensure that any key controls are included in the project. Any shortcomings should be reported and recommendations made to rectify them.

The Getting Started step should include a plan that revolves around the following areas:

• Examining business needs / requirements in measurable goals.
• Reviewing current operations
• Draft concept of final product operation
• equipment and requirements including long-term assessment of items
• Financial and cost analysis as well as budget
• Stakeholder analysis, as well as users, and project support staff
• Project schedule including costs, tasks, results, and schedules

Planning and Design

Group Activity Planning Process & lt; ref name = “VA03” / & gt;

After the start step, the system is drafted. Occasionally, a small sample of the final product is developed and tested. Tests are generally performed with a combination of testers and end users, and can be performed when a model is being developed or simultaneously. Control should be in place to ensure that the final product will meet the requirements contained in the project schedule specifications. The results of the bureaucratic action should include a draft product that:

• It satisfies the project sponsor, end user, and commercial needs
• It works as intended.
• It can be manufactured within the best acceptable standards
• It can be developed within time and budget constraints

Implementation

Group Implementation Process & lt; ref name = “VA03” / & gt;

Implementation includes the procedures used to complete the work specified in the project management plan to meet the project requirements. Implementation involves coordinating people and resources, as well as co-coordinating and executing project activities in accordance with the project management plan. The results are reflected as a result of the processes carried out as outlined in the project management plan. Type of draft..

Monitoring and Verification 

Monitoring and Verification relates to the processes that take place to monitor project implementation to identify potential problems in a timely manner and remedial action should be taken, where necessary, to control project performance. An important benefit is that project performance is monitored and evaluated regularly to identify differences from the project management plan.

Monitoring and Control of Group processes & lt; ref name = “VA03” / & gt;

Monitoring and Verification includes:

• Evaluating ongoing project activities (where we are now);
• Monitoring of project components (cost, effort, scope, etc.) against the project management plan and the project performance base (where we should be);
• Identify corrective actions to resolve issues and risks effectively (How can we return to the right path);
• Influence of factors that may hinder the control of integrated change so that only approved changes can be implemented

In multi-phase projects, the Monitoring and Verification process also provides feedback between project phases, in order to implement corrective or preventative actions so that the project meets the requirements of the project management plan.

Project design is an ongoing process, and includes:

• Continue to support end users
• Correction of errors
• Software extensions over time

Cycle Monitoring and Verification

At this point, inspectors should consider how and when consumer problems are resolved.

In the course of any construction project, the scope of work can change. Changes are common and are an expected part of the construction process. Changes can be the result of significant changes in the draft, different local conditions, access to equipment, changes made by the contractor, value engineering and impacts from outsiders, to a lesser extent. In addition to implementing changes in the project area, changes need to be transcribed into a document showing exactly what was created. This is known as Change Management. Thus, the owner usually needs a final record to show all the changes or, more specifically, any apparent changes that the part of the finished work. References are made in the contract document – usually, but not necessarily, sealed with architectural drawings. The final product of this effort is what the manufacturing industry calls sketches built, or more simply, “built.” The requirement to provide these drawings is customary in construction contracts.

When changes are incorporated into a project, project feasibility must be considered. It is important not to lose sight of the original goals and objectives of the projects. When changes do accumulate, the predicted results may not justify the initial investment proposals in the project.

Closing 

The process of closing Group processes. & lt; ref Name = “VA03” / & gt;

Closing includes the official acceptance of a project and its completion. Management tasks include file storage and copying tutorials read.

This phase consists of:

• Project closure: Complete all process group activities to officially close the project or project phase
• Contract closure: Completion and completion of each contract (including the resolution of any open query) and closing each contract related to the project or project phase.

Project Management Systems 

Project management is the element of a project that puts the project in the right order, timed and within budget. Project management begins early in the project and planning and ends at the end of the project with post-implementation reviews, with involvement at every stage of the process. Each project should be evaluated for the appropriate level of control required: too much control is time consuming, too much, while too little control is too dangerous. If project management is not properly implemented, the cost of the business should be clear in terms of errors, adjustments, and additional inspection fees.

Control systems are needed for cost, risk, quality, communication, time, change, procurement, and human resources. In addition, auditors are required to consider how important projects are to financial reporting, to what extent stakeholders are subject to control, and how many controls are in place. Auditors must monitor the development process and the procedures for implementation. The process of development and quality of the final product can also be evaluated if needed or if requested. Businesses may require the audit firm to participate in the entire process in order to address problems early so that they can be easily resolved. The auditor may serve as a control consultant as part of the implementation team or as an independent auditor as part of the audit.

Businesses sometimes use formal manufacturing processes. This helps in ensuring that the systems are designed successfully. The formal process is most effective in building strong controls, and inspectors are required to monitor this process to ensure that it was properly designed and will be followed in practice. A good plan for the development of formal systems consists of:

• A strategy to compare development and broader organizational goals
• Standards for new systems
• Time management and budgeting policies
• Procedures to explain the process

Project Management Topics

Project Managers 

The project manager is an expert in the field of project management. Project managers may be responsible for planning, implementing, and installing any projects, usually related to the construction industry, Architecture, computer networks, telecommunications or software development. Many other fields in manufacturing, architecture and service industries also have project managers.

A project manager is a person who is given the responsibility to achieve the stated project goals. Key responsibilities in project management are setting clear and achievable goals, building project requirements, and managing three barriers to projects, which are cost, time, and scope.

The project manager is usually the client’s representative and must determine and implement the client’s needs, based on the knowledge of the company he or she represents. The ability to adapt to the various internal processes of the representative party, and to form close links with representatives, is essential in ensuring that key issues of cost, time, quality and above all, customer satisfaction, can be met.

Project Management Triangle 

Project Management Triangle.

Like anything that is done by humans, projects need to be done and delivered within certain constraints. Initially, these constraints have been listed as “maximum,” “time,” and “cost”. These are known as the “Three Corners of Project Management” where each side represents an obstacle. One side of the triangle cannot be changed without affecting the other. Further barrier analysis separates product “quality” or “performance” from scope, and alters quality as a fourth barrier.

Time constraint refers to the amount of time available to complete a project. The cost limit refers to the amount budgeted for the project. The scope of the scope refers to the necessary things that need to be done to provide the final outcome of the project. These three constraints are often competing constraints: increase in scope means increasing time and cost overruns, Time reductions can mean increased costs and decreases in scope, and larger budgets can mean increased time and scope reduction.

The Project Management course is about providing tools and techniques that enable the project team (not just the project manager) to prepare their work to meet these barriers.

Job Allocation Structure 

An example of a dividing structure The function used in the NASA reporting structure. ^[3]

The Job Allocation Structure (WBS) is a tree structure, which indicates the allocation of effort required to achieve a particular goal; for example a plan, project, and contract. WBS can be equipment, products, services, or process-oriented.

WBS can be developed starting with the ultimate goal and furthering its division into components in terms of size, time, and responsibility (e.g., systems, sub-systems, components, functions, functions, and work packages), which includes all key steps in achieving the goal. [23]

The Job Allocation Framework provides a common basis for the natural development of general planning and contract management and is the basis for the division of labor into a known increase from which the job information can be developed by technical reports, schedules, costs, and hours. Work can be created.

Project Management Strategy 

Example of an IT Project Management Strategy.

Software Life Cycle (Investment) includes project management and life cycle manufacturing system directly and operations related to deployment and operation of the system. For Bureaucracy, management of system operations and related activities occurs after the completion of the project and fails to be copied in this guide.

For example, see the diagram, in the United States, the U.S. Department of Retirement Activities (VA) Program life cycle management program is illustrated and explained in the general VA IT Project Management framework to address the integration of project management activities (investment). ) of OMB Exhibit 300 and the overall project budget process. The VA IT Project Management Project Diagram describes Milestone 4 which occurs when the system is deployed to end users and during project installation. The closing phase of project activities in the VA proceeds through the deployment of system users to end users to system operations for the purpose of displaying and describing system operations that the VA assumes as part of the project.

International Code 

There have been several attempts to create Project Management code such as:

• Example of Competence and Maturity from the Software Engineering Institute.
• GAPPS, an International Community for the Evaluation of Project Outcomes-Principles whose application is free and describes the competence of program and project managers. [28]
• Guide to the Project Management Knowledge Body
• HERMES approach, a comprehensive project management approach from Switzerland, selected for use in Luxembourg by international organizations.
• ISO ISO 9000 regulations, a family of systems quality management principles, and ISO 10006: 2003, of best systems management systems and quality management guidelines in projects.
• PRINCE2, Projects in a Controlled Environment.
• Team Software Process (TSP) from the Software Engineering Institute.
• Basic Cost Management Foundation, International Methodology for Potential Combination, Software and Project Management Management (ACCE)
• V-Modell, a method for creating original systems.

Project portfolio management 

Increasing the number of organizations is using, what is known as, project portfolio management (PPM) as a fair way to select projects and project management then use the technique  as a way to deliver results in the form of personal performing profits or not-for-profit organization.

Project management uses the ‘do the right projects’ techniques and the PPM techniques used ‘do the right projects’. In effect PPM is becoming a selective mechanism for selection and prioritization among inter-resource resources related to industrial and multi-sect oral projects.

By

Your Narrator, President of the Federation of Ewovico Companies

Emperor Dr, Thabit L.F

info@ewovico.com

info@ewoviprojects.com