Project Manager Of United Telecom Limited

risks and determine the likelihood and consequence of that risk occurring during the project. The

Perform high level project management 2. Ultimate authority and responsibility for the project 3. Provide funds for the project and manage the overall budget 4. Approve and continuously monitor the project 5. Schedule work with other project teams and initiate 6. Develop and maintain project charter

Cost and resource needs are higher for traditional than Agile due to Waterfall’s sequential development phase of all requirements determined in the beginning, software design and finally implementation of master design. The need for all information up front takes substantial time to gather and the sequential design does not allow for project changes as the flow enters into the programming stage. With Agile, costs remain low because there exists an incremental and iterative approach to the project, meaning less time is used to collect all requirements up front, the

The project is Agile, i.e. it can quickly adapt to changes in requirements. Hence, this method has high success rates.

The next step of activities in the execution process of this project will involve acquiring the project team and assigning task to

Successful achievement in a project, requires detailed understanding and capabilities of project management. Implementing the given task in the most appropriate ways will result in a successful project.

For the past years, waterfall process had been used by small and big companies as an approach to development process. This approach looks like a waterfall where it shows a steady downwards flow. This approach of development is the most mature and disciplined.

In order to perform project risk management effectively, the organization or the department must know the meaning of the risk clearly. With regards to a project, the management must focus on the potential effects on the objectives of the project, for example, cost and time (Loosemore, Raftery and Reilly, 2006). Risk is a vulnerability that really matters; it can influence the objectives of the project

Focus is kept on the recurrence of condensed work cycles and also at the functional product yielded by the outcome, but in waterfall technique only once chance is been given to the development team to keep the project aspects right. But under the agile technique each and every feature of development including the design, requirements, is thoroughly checked under its lifecycle (Mahfuj et al, 2012). There is always some time to steer in another direction if a team stops at regular interval say after every two weeks and re-evaluates the project done.

Several adaptations to the traditional approaches like agile, interactive, phased, extreme, etc have been made but each will be expected to meet the requirements of the project objectives, timeline, resources, and deliveries of the stakeholders. Other industry standard certifications like ISO9000 and regulations like the Sarbanes-Oxley have also influenced methodologies and processes used by several organisations (Kerzner, 2003). Generally, managing projects should involved five major process which include the project initiation, planning, execution, monitoring and controlling, and then project closing. See Fig. 2 below.

The other important aspect will be the methodology of quantify research, that will be used to reduce the different project failures and also schedule overruns while using statistical attributes that will help you monitor the project during its lifecycle, and also help you measure any type of data to formulate the different facts within the project and the parameters of the project scope, this will help with the project. The analysis can help you in many different ways, it could help you identify the risk or the different

The original Waterfall model has a foundation that is supported by two distinct characteristics. First, the methodology is rooted in the fact that that the software be developed in stages. “Originally created by Benington in 1956 and later modified by Royce in 1970, the quintessential Waterfall model is linear and sequential in evolution, typically with milestones at each phase of development. (Pavolka, 2005). As seen in figure 1 (Ruparelia, May 2010), the typical thresholds consisted of Evaluation, Requirements, Analysis, Design, Development, Validation, and ultimately Deployment. The evaluation phase, at the aggregate level, helps to reveal the situation at hand. The requirements phase is arguably the most important phase of the Waterfall plan as it lays out the project statement and sets the framework and expectations for the project. The next phase, Analysis, works as a comparison between what capabilities are needed versus what constraints currently exist. That leads into the Design phase in which the software developers determine the architecture required to meet the customer’s expectations taking into account the constraints previously identified. Development is the next phase that takes the inputs from the Design phase and outputs a tangible product ready for testing. The testing or Validation phase is the process in which the software is checked for two things: a) any and all bugs are identified and removed and b) the original scope of work including all

The Waterfall method was originally developed in 1970 by Dr. W Royce to assist with the development of software. It has survived to this day through adaption and revisions enabling it to be one of the most widely used models (Charvat 2003). Its namesake originates from the analogy of a waterfall flowing downwards with the model following suit, cascading towards completion (Balaji and Murugaiyan 2012) this is known as a serial lifecycle. Each phase (starting in the top left corner) within the serial lifecycle is completed before moving on to the next phase until the end goal is reached (see Figure 1). This kind of method suits projects that have clearly defined stage goals, outcomes or solutions that are highlighted in the initial strategy of

There are many ways to develop software. A very popular and preferred method of software development today is the Agile development methodology. One of the original development methods is the Waterfall method. When comparing the two software development methods, Agile fluid process are preferred to the rigid traditional Waterfall development methodology’s created back when computers were very large physical behemoths, taking up entire rooms.

Waterfall Model Development allows for Departmentalization and control as it's advantages. Stage of development can set a schedule with deadlines and the product can progress through the growth procedure model stages accordingly.