Methodology In Project Management

1753 Words8 Pages
CHAPTER 3
METHODOLOGY
1. Introduction
This section will discuss the different types of methodologies.

1.1 Methodology
A methodology is a system of broad principles from which specific procedures maybe be derived to solve different problems within the scope of a project. The purpose of a methodology is to allow controlling of the entire management process through effective decision making as well as problem solving, on the other hand, ensuring the success of specific processes, approaches, methods and techniques(McConnell 2010).

1.2Traditional Software Development Methodology
This section will discuss some of the earlier software development models, for example:
1.2.1 Waterfall Model
“The waterfall model was introduced in the 1970s by Win
…show more content…
It was practiced before the announcement of the Agile Manifesto. Later it was included into agile methodology since it has the same underlying concept and rules of agile development. Scrum has been used with the objective of simplifying the control of a project through simple processes, easy to update documentation and higher teams iteration over exhaustive documentation (Malik Hneif 2009).
Scrum shares the basic concepts and practices with other agile methodologies, but it comprises project management as part of its practices. These practices guide the development team in finding out the tasks at ev iteration. One of the main mechanisms recommended by scrum is to build a backlog. A backlog is a prioritized list of all the features and functionally needed to complete a project. There is a simple sentence for each requirement which will be used by the team to start discussions and putting details of what is needed to be implemented by the team for the requirement (Malik Hneif
…show more content…
It fails to address usability needs of the users as product owners keep their focus mainly on business issues and forget about usability(Malik Hneif 2009).
There are some benefits of using the scrum methodology such as daily meetings makes it possible to measure individual productivity which therefore leads to the improvement in the productivity of each of the team members. It is a lightly controlled method, which insists on frequent updating of the progress in work through regular meetings, which means there is a clear visibility of the project development. It is through the regular meetings that issues are identified well; they are discussed and hence can be quickly resolved(Mahalakshmi & Sundararajan 2013).
It can be difficult for the scrum master to plan, structure and organize a project that lacks a clear definition. In addition, the daily scrum meetings and frequent reviews require substantial resources. A successful project depends on the maturity and dedication of all participants, as well as their ability to maintain consistently high levels of communication through each backlog(Mahalakshmi & Sundararajan

More about Methodology In Project Management

Open Document