Project Management Methodology Rule and Guidance

Question: Discuss about the Project Management Methodology Rule and Guidance. Answer: What a methodology is and the role it serves in project management The project management methodology is a set of rule and guidance for the project team through which they can accomplish a project. The methodology makes the project easy for the manager to understand and overcome any kind of project trouble if arrive during the project. The methodology generally contains the definitions, guidelines and different templates for the successful completion and delivery of the project. The3 methodology is generally used by all kind of project development whether the project is related to the Information technology or from any other domain (Michels, 1986). In a project development, the project management methodologies generally applied by the managers for the planning and design and implementation of the project. Each project generally uses different methodologies which can be different for a different project. As an example, the NASA applies a different methodology for a different project and Navy apply a different methodology for their projects. Type of m ethodologies, which generally applied by the organizations and teams for the project developments are, Agile Adaptive project Framework Crystal method SDLC Waterfall methodology PRINCE 2 Spiral Scrum 2. Familiarize yourselves with the various methodologies in the list below. Choose two methodologies from this list to compare and contrast, analyzing the similarities and differences between them both. There are different methodologies which are generally applied by the project management teams for the project development. The Agile and the Waterfall project development methodologies are two of them which are used by the managers in most of the project development cases. The project development methodologies like Agile and Waterfall have their own characteristics which become beneficial for the project development. The selection of the methodology depends on upon the type of the project which is under in the development phase. To compare to methodologies I have chosen the Agile and t4he waterfall project development methodologies. These two methodologies are widely used and accepted by the project development teams. Similarities between the Waterfall and Agile methodologies: The similarity between the Agile and the Waterfall or the traditional method is the same Goal. In both of the cases, the Goal of the project management is the delivery of a well planned and developed project. Agile and waterfall both of these generally uses the same kind of principle in project development. The two methodologies generally prefer planning throughout the project before the development. Both of these methodologies lock down the requirements before the starting of the project. Both project development methodologies use same building block methodologies. The Agile, as well as traditional methodology, generally proceed with projects in same building blocks method. They generally create Scope, cost, schedule and performance criteria for the project management (Ed, 2006). The picture shows the agile project development stages. The above picture describes the stages in Waterfall methodology steps. Difference: There are some differences in the Agile and Waterfall project Development methodologies which are aimed towards planning and creating a project. The traditional and the Agile project management methodologies generally dont use the same The traditional and the agile project development phase generally use the same kind of project development principle and building blocks but they are not placed in the same place. They are put in different place in terms of performance and design considerations. Agile project development methodology is flexible in terms of changes but the waterfall project development methodology is not flexible with the change in the project. In the present day, the change in the project requirements is the common thing which is needed to be completed during the development of the project. A developer can change in the ongoing project development whereas in the waterfall the change is not allowed during the development. This is the reason behind the popularity Agile project development over the traditional project development methodology. Agile project development methodology is more transparent whereas the waterfall project development methodology is not transparent. The transparency in the project development helps the developer team to recognize the loopholes present in the project development plan (Mathaisel, 2013). 3: Finally, identify how your chosen methodologies and processes relate to the project life cycle (PLC): The agile methodology and the waterfall methodology are two methodologies which I have chosen for the project development. The agile has different stages in the project development life cycle. The project development life cycle in the both of the methodology consists of different stages in the project development life cycle. These are; Brainstorming- In this approach the developer team generally analyze the situation for which they have to create the software. The project team consults with the stakeholder about the situation for which the software is being developed. Planning: The planning stage is one of the important stage in the product development in which the project team generally plan about the project which is needed to develop the team. The teams analyze the situation and construct the requirement list for the project development. Design: In this case, the team designs the blueprint of the software. After being analyzed by the team and all requirements are met, the teams generally design the software outline for the further development. Build: The developer team builds the software as per the requirement of the client and the outline they have created for the development of the software. Test: This is the testing phase of the software which was created by the team and tested in the real environment to check whether the software is as per the client's expectation or not. Installation: The installation phase is the next stage in which the team installs the software in the place where it has to work. The tested software the installed in the real environment so that the client can take the softwares help in the work. Support : Its is the last stage of the software project life cycle in which the software development team and the company are responsible for any kind of support which is needed in case of any software problem (IEEE, 2006). The project development lifecycle generally consists of these steps which start with the brainstorming and reach and end with the installation of the software. Reference: Michels, J. B. (1986). A Software Planning and Development Methodology with Resource Allocation Capability. Ft. Belvoir: Defense Technical Information Center. Ed, K. A. (2013). Agile methodology for developing measuring learning: Training development for today's world. Place of publication not identified: Authorhouse. Mathaisel, D. F., Manary, J., Criscimagna, N. H. (2013). Engineering for sustainability. Boca Raton, FL: CRC Press. IEEE Standard for Developing a Software Project Life Cycle Process. (n.d.). doi:10.1109/ieeestd.2006.219190