Project Controls: Managing And Controlling The Project

provides a structured approach to proposing a project. In the controlling/monitoring phase, an appropriate methodology offers the timeline and includes regular milestones for project development by monitoring the associated risk in the project. In closing process, a perfect project methodology evaluates the customer’s review on the final project and its quality criteria, costs, duration and tolerance. The primary objective of this approach is to monitor whether the user's requirement have been fulfilled or not as projects are not closed after the closing proves and will continue to consume resources. In this phase, project management and maintenance of the used resource is important and further developments ideology is being applied in this phase.

Waterfall and Agile project methodology

Two of the most common used project methodologies for developing a project are Waterfall and Agile project methodology.

Compare and contrast

Image 2: Waterfall and Agile project methodology

Waterfall model is used when project manager knows the structure of the final project and when the clients will not have the ability to change the scope of the project once the designing of the software is started. Agile project methodology is used to overcome the disadvantage of the waterfall model that is to develop a simplistic project design and divide the entire software in modules. Agile project methodology enables the user to modify the stage of a software development life cycle in the middle of the software development.

Similarities and differences

The similarity between the waterfall model and agile project methodology is that these methodologies are used for developing software for customers for their business or fulfil objectives. Moreover, these processes need time, resources and budget to complete the project.

	Waterfall	Agile
Differences	Waterfall project methodology manage activities	Agile project methodology manages time
	The customer cannot be involved in the process for adding any further modifications and hence lessons are learned from previous mistakes.	The customer can be included in the process for adding modifications and hence is flexible project methodology.
	Waterfall model is highly structured and well documented	Agile project methodology is highly collaborative and offers continuous improvements.
	This project methodology comprises of planning of the software, release the resources and then document the process	This project methodology consists of the development of the project.
	This methodology emphasizes on quality focus changes from analysis to design to code and then test.	This methodology emphasis on SDLC at any stage of the software
	Prior risk cannot be identified without experience of the project manager in development of the software during the testing phase.	Early risk identification can be possible and can be mitigated in every module.
	The project owner will decide the project scope.	The team member of the software development decides the formulation of each module as per as the resource availability and product backlog.
	The final delivery of the product is done phase by phase.	The final delivery of the project is based on demo feedback so that the final output can be error free and perfect.

Table 1: Difference between waterfall and agile project methodology

Relation with the project life cycle

In a project life cycle, waterfall model for departmentalization and control the entire software development by formulating schedule and deadline to accomplish the software. Waterfall project methodology is easy to manage due to its rigidness and specify each project requirement from the first phase to last. The software is produced in module format and integrates all the moduleq for developing the software.

Agile project methodology involves in iterations, analyzing, designing, developing and testing of the software model and is based on customer’s interactions for developing the software This methodology helps in a feasibility study with user’s requirements and checks whether the program is financial, practically and technologically feasible. Team developers decide a roadmap of the plan and then implement the entire software based on the developed codes and estimate the error present in the program. In the last phase, the operation and maintenance of each phase of the software developed are carried out and handed over to the customer for use in their business or for the actual purpose the business software is being developed.

Reference List

Balaji, S., and M. Sundararajan Murugaiyan. "Waterfall vs. V-Model vs. Agile: A comparative study on SDLC." International Journal of Information Technology and Business Management 2, no. 1 (2012): 26-30.

Bassil, Youssef. "A simulation model for the waterfall software development life cycle." arXiv preprint arXiv:1205.6904 (2012).

Burke, Rory. "Project management: planning and control techniques." New Jersey, USA (2013).

Dalcher, Darren. "Going Beyond The Waterfall: Managing Scope Effectively Across the Project Life Cycle." Project Management Journal 46, no. 1 (2015): e2-e2.

Elghondakly, Roaa, Sherin Moussa, and Nagwa Badr. "Waterfall and agile requirements-based model for automated test cases generation." In 2015 IEEE Seventh International Conference on Intelligent Computing and Information Systems (ICICIS), pp. 607-612. IEEE, 2015.

Gottipalla, Ashok Kumar, N. M. S. Desai, and M. Sudhakar Reddy. "Software Development Life Cycle Processes with Secure." The International Journal of Scientific and Research Publications 3 (2013): 1-3.

Kerzner, Harold R. Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons, 2013.

Marchewka, Jack T. Information technology project management. John Wiley & Sons, 2014.

Moniruzzaman, A. B. M., and Dr Syed Akhter Hossain. "Comparative Study on Agile software development methodologies." arXiv preprint arXiv:1307.3356 (2013).

Pedersen, Mitra. "A Quantitative Examination of Critical Success Factors Comparing Agile and Waterfall Project Management Methodologies."ProQuest LLC (2013).

Raval, Ratnmala R., and Haresh M. Rathod. "Improvements in Agile Model using Hybrid Theory for Software Development in Software Engineering."International Journal of Computer Applications 90, no. 16 (2014): 26-31.

Stoica, Marian, Marinela Mircea, and Bogdan Ghilic-Micu. "Software Development: Agile vs. Traditional." Informatica Economica 17, no. 4 (2013): 64.

Turk, Dan, Robert France, and Bernhard Rumpe. "Assumptions underlying agile software development processes." arXiv preprint arXiv:1409.6610(2014).