Within this chapter I show the feasibility of a project up to the approval of the project. These managers must be held accountable to the company for the success of the project. It is essential that the results of the project analysis are captured, as a formal expression of business needs.
Effective and efficient policies and procedures must be in place for the execution of the project commitment.
Becoming an IT Project Manager
On most projects, it is unlikely that the project manager will be someone who works for the company. Ensuring that the individual can maintain the project manager role throughout the project lifecycle. To promote the success of the virtual team, the project manager must establish certain criteria.
The project manager must ensure that effective electronic means of communication are used.
Project Concepts
It is a step-by-step, linear methodology that guides a project manager to complete one phase of the project before moving on to the next. These risks include threats to the project budget: the danger of unforeseen events causing cost overruns. They are also known as business risks and are beyond the control of the project manager.
There is a need to involve other parties that were not previously part of the project or requirements definition.
Medium Projects
The organization of the supplier is unclear or changes frequently. There is a deviation from the agreed target dates for the delivery of any part of the solution.
Small Projects
I have found on numerous projects that project managers neglect to properly manage the configuration of the project (1) documentation, (2) software version, or (3) specific baseline. Project managers share the responsibility for strictly enforcing the rule that a configuration identification process is established on the project, in order to identify all project baselines. The emphasis here is that only approved baseline documents with associated version control will be used on the project.
The risk of using unapproved project documents is directly related to the project team using those documents to develop specific deliverables. Finally, the project manager must insist on and develop a method for effective distribution and controlled release of documentation and source code to the project group's individuals or groups. What happens when the customer decides to change a requirement after the team has started work on the project.
The solution to this scenario is for the project manager to insist on establishing a project change control process for these change requests, and the entire team must be familiar with how this change control process works. It is important that the project manager is aware that all project change documentation is maintained at the project level. Many projects go disastrously wrong when the project management method is abandoned in order to respond to pressure from senior management to accelerate the project.
The project plan does not take into account the risks of integration with existing systems. Interfaces with existing systems are becoming an issue during the final stages of the project.
The Project Analysis
Depending on the scale and complexity of the project, the project manager must consider who will do the actual business analysis. The project analysis team should include the client as part of the team in order to verify that the scope is correctly defined. What the project is not How will it be managed Scope change risks.
Business documentation is usually co-authored or written by the project manager and then managed. The project manager must ensure that the documentation is consistent and does not conflict with any other requirements. The way they become aware of the project and commit to it is through the business case.
If the ROI were 100 percent, the benefits would equal the costs of the project—. The project team must nevertheless validate that the customer's requirements justify the adaptation as being realistic. What is the likely ROI and estimated profitability that can be expected on the project.
Please note that it is up to the project manager to ensure that the business analysis of the proposed solution is completed and reaches decision makers in the organization for a go/no go decision. The most effective way to limit risks during the start-up phase of the project is to use experienced and knowledgeable people.
Planning for Success
Once this has been completed, the project manager estimates the costs for each task (see figure 5.2). The project manager must identify the technical, interpersonal and organizational skills necessary to complete the project. The project manager is the focal point for identifying the required skill levels.
A useful technique to help the project manager is the linear responsibility diagram (LRC) or matrix. Document the project WBS in a linear fashion on the left side of the matrix. This risk works well if the project manager has superior knowledge of the type of solution being undertaken.
The project manager must establish procurement requirements to determine which resources should be procured externally versus internally. Effective logistical support must be organized and included in the overall project planning phase. One of the most important mandatory steps that the project manager must take is to ensure proper.
The project manager must remain involved with the technical team during the design of the entire solution. This may mean that the project manager obtains separate cost and time estimates from these contractors.
Executing the Project
A project manager's job is to ensure that the project follows the development time estimates that were given during the planning phase. The project manager should be actively involved during development, even though the developers on the team will do most of the work. It sounds strange, but the project manager needs to keep track of the progress of these development tasks.
The project manager should establish frequent development meetings with team leaders and developers to. If the project is running late, the project manager should arrange for additional working hours. At this stage, the project manager should already inform the testing team about the upcoming testing.
The project manager should be informed of the results and be able to review them with the team. The project manager should select an individual (one who was involved in training and acceptance testing) to be responsible for collecting bug reports and change requests. The project manager must be involved with the test team to resolve any possible inconsistencies that may exist.
The project manager should understand that the budget is fixed and that no additional funds will be allocated to the project. The result of the audit will allow the project manager to implement the necessary corrective actions.
Controlling the Project
It is necessary that these costs are captured in the project system that the project manager is using. This indicates that the project manager is well within budget and under budget for project tasks or activities. A vital part of any project manager's responsibilities is to take charge of the day-to-day activities on the project.
Once quantified, each risk must be prioritized by the project manager on a risk matrix. It is important to control the change requests that are proposed during the course of the project. Communicate with the project team so that all members understand the effect of the scope change.
Project managers must track all proposed changes to the project on an ongoing basis. They meet regularly to review the change requests or when requested by the project manager. In this case, the project manager must determine the process of functions within the CCB.
The project manager must proactively work with all staff to avoid potential conflicts that may arise. Throughout the project's life cycle, the project manager must generate reports related to quality issues and.
Implementing the Project
The planning and preparation of the solution infrastructure prior to the actual implementation is an important step. It is important that the required hardware and software are (1) shipped, (2) delivered, (3) installed, and (4) properly configured to reflect the requirements of the solution prior to the start date. The new IT solution should be configured to accept each authorized user of the new solution.
It is important that users of the system receive all the training and support they need to use the new system effectively. Training staff can require significant resources, often a significant portion of the total cost of the project. Project managers must realize that proper training must be provided to the users of the solution, which could include the following types of training.
Before implementing a project for a client, the project manager must be sure that the client's IT operational support staff is adequately trained and knowledgeable about the technical support issues of the system being deployed. The IT help desk is aware of the start date and has been informed of the possible volume and nature of calls that can be expected. The project manager must properly plan the live period, and he or she cannot assume that it is the test team's duty to prepare the next step in the implementation.
The purpose of the readiness check is to clearly communicate the status of the system before the system test begins. At the end of the system testing phase, the project manager should conduct a readiness review meeting.
