Project Management OZ Assignments

Project Management OZ Assignments

Project Management OZ Assignments

Introduction

Project Management Methodology is a combination or set of logically interlinked processes, practices, techniques, and methods which determines or analyze how best to develop, control, plan and deliver any project with a regular implementation process till it terminates and completes successfully. In this task,I have shared my knowledge regarding project management methodology and the role they play in project management. I have even explained Waterfall methodology and compared it with Agile methodology. Finally, I have shown the relation between Waterfall Methodology and PLC.

Define what a methodology is and the role it serves in project management.

Project Management Methodology
This methodology is a combination or set of logically interlinked processes, practices, techniques,and methods which determines or analyze how best to develop, control, plan and deliver any project with a regular implementation process till it terminates and completes successfully. It is a disciplined, scientifically proven and systematic approach towards designing, launching, and completion of the project. It is a combination of rules and principals which are used to manage and execute some specific projects which have a definite end as well as the beginning.

Role of Methodology in Project Management

1.They allow the controlling of complete management process by effectively making decisions and solving problems.
2. They ensure or guarantee the success of some specific approaches, methods, processes, technologies, and techniques.
3. It is a backbone of every management as it provides the complete information about every step in full depth, which makes it easier for a project manager to understand what he has to do so as to implement and deliver the work on basis of schedule, client specification, and budget.
4. It prepares a framework for formulating, performing and delivering some projects which can possess any size, type, nature, and kind.
5. It provides a way to realize changes systematically in terms of cost, time and quality.

Achievements Gained using Methodologies

1. It fulfills the requirement of stakeholders.
2. One common understandable language is introduced for the team so to make them understand what the expectations are.
3. No mixing of methodologies means every task is performed using same methodological approach.
4. Most of the conflicts are identified and resolved quickly.
5. The team learns few lessons and solutions are implemented very quickly (McConnell, 2010).

Familiarise yourselves with the various methodologies in the list below. Choose two methodologies from this list to compare and contrast, analyzingthe similarities and differences between them both.

There are various types of approaches or methods which can be used for managing different projects in project management. The methodology I have chosen is:

Waterfall

The waterfall is a methodology in project management also known as SDLC (Software Development Life Cycle) that carries a simple approach which emphasizes on formulating or planning, performing it right at asingle time making decremented and non-iterative delivery. It is simple and easy to understand as it forms a good or simple plan and concentrates as well as execute on it. The project manager using this methodology plans the work, executes it strictly in a sequence focusing on the requirements and finally delivers the project in a single mainly very long cycle.
Figure 1: Waterfall Model
Source: (Buzzle, 2017)
In the very beginning, requirements are properly defined before getting started with any work at top of the waterfall. Then work cascades just like water flowing down from a waterfall through some phases of project. In the model of waterfall, no overlapping takes place in the phase means each phase should be completed before the beginning of next phase. In the waterfall approach, the output of 1 phase behaves as the input of the next upcoming phase in a sequence.

Once the plan is approved they provide scopes to modify, adapt or revise the plan thus the changes which are required are made. The project passes through a process starting from requirements leading towards implementation, design, testing and finally into maintenance. Waterfall methodology uses single cycle approach so here things can be revised once it has been completed but after reaching the testing stage it is really difficult to modify anything. When we have fixed requirements, well and clear documentation waterfall is the best approach to be used it provides far predictable results at the end of timeline, budget, and scope (Aston, 2017).

Agile is the methodology outlined by projectmanagement body of knowledge so comparison between Agile and Waterfall is given below:

Difference between Agile and Waterfall

Agile

Waterfall

Its function is to produce the killer application.

Its function is to certify or check the quality of a product.

It is completely dependent on automated testing.

It is not so much dependent on automated testing.

No separate team is there, integrated or combined with one team.

A complete separate team is there for development.

The architecture of agile is incremental and informal.

Architecture is well documented and is completed before any other phase or before coding gets started.

It performs the continuous integration.

Integration is performed at the end.

Light process and documentation.

Heavy process and documentation.

Developers share ownerships for a code.

Each developer is assigned one area and is responsible for that area.

Require more time and energy from developers (Flatworldsolutions, 2016).

Time management is easy for developers (Gutierrez, 2010).

Similarities between Agile and Waterfall methodology
1. In both the testing is performed usually in big batches.
2. In both architecture and designs are performed or made after analysis.
3. 
In both planning is performed at the very beginning of project.
4. In both at the very stage, approval is given (Gutierrez, 2010).

Finally, identify how your chosen methodologies and processes relate to the project life cycle (PLC).to

Relation of Waterfall methodology (SDLC) with PLC

 


Figure 2: Relation between SDLC and PLC
Source: (Sheehan, 2014)

Project Life Cycle (PLC) majorly provides attention to the tools, phases, knowledge, skills, and processes for the managing projects. It majorly has 5 steps:
1. 
Explaining the project goal.
2. Planning for the project.
3. Execution of project plan.
4. The closing of the product.
5. Evaluation of the project.

Waterfall Methodology or System Development Life Cycle (SDLC) has its relation with PLC in one of its steps which is the execution of the project plan. SDLC mainly focuses on implementing and creating project product. It is a part of PLC as all development activities take place during the execution step of PLC. Execution of project plan is one of the steps of PLC and for the execution, few steps are required which are done in SDLC. Those steps are:
1. Planning
2. Analysis
3. Designing
4. Implementation
5. 
Maintenance and support

The last two phases of PLC are closing of project and evaluation of project, these two steps can only take place after implementation of the system so for completion of PLC, Waterfall Methodology or SDLC plays a vital role (Sheehan, 2014).

Conclusion

I have efficaciously completed the task of Project Management Methodology. I enriched my skills and gained knowledge that by using project management methodology how can one best develop, control, plan and deliver any project with a regular implementation process till it terminates and completes successfully. I have discussed Waterfall Methodology its comparison with Agile methodology. I even discussed the steps included in PLC and how Waterfall Methodology is a part of PLC.

References
1. McConnell, E. (2010). Project Management Methodology. Retrieved from http://www.mymanagementguide.com/basics/project-methodology-definition/.
2. Aston, B. (2017). 9 Project Management Methodologies Made Simple. Retrieved from http://www.thedigitalprojectmanager.com/project-management-methodologies-made-simple/.
3. Gutierrez, A.(2010). Waterfall vs. Agile. Retrieved from https://dzone.com/articles/waterfall-vs-agile-qa-management.

4. Gutierrez, A.(2010). Waterfall vs. Agile Can they be Friends. Retrieved from https://dzone.com/articles/combining-agile-waterfall.
5. Flatworldsolutions.(2016, January 28). 10 Differences between Agile and Waterfall Methodology [Blog Post]. Retrieved from https://blog.flatworldsolutions.com/10-differences-agile-waterfall-methodology.
6. Buzzle. (2017). Phases of the Waterfall Model Explicated With a Diagram. Retrieved from https://www.buzzle.com/articles/waterfall-model-diagram.html.
7. Sheehan, T.(2014). Conceptualization’s Nature of SOFTWARE (SW). Retrieved from http://slideplayer.com/slide/263900/.