Agile project management methodology

From CEOpedia | Management online
Revision as of 20:52, 13 December 2019 by Ceopediabot (talk | contribs) (Typos, typos fixed: Therefore → Therefore,, However → However, , ill defined → ill-defined, , → ,)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Agile project management methodology
See also


Agile Project Management (APM) is found to be the most suitable for the present days unpredictable project environments, where the conventional methods’ approach of rigid project plans and designs cannot be supported. The key features of APM are flexibility, stakeholder engagement and value delivery which are based on the three principles underlying APM-embracing change, delivering part of functionality incrementally, reflecting and learning continuously.


Project management methodologies

The traditional focus of a Project Management has been the completion of a project within time constraints and cost limits with limited resources, delivering the outputs to the customers at the required standards of quality. Top Project Management Methodologies used are –

  • The Traditional, Sequential Methodologies
  • PMI/PMBOK “Method’
  • The Agile Family
  • The Change Management Methodologies

The Traditional Methodologies include – The Waterfall, The Critical Path Method (CPM),The Critical Chain Project Method (CCPM). The PMBOK Method is not a methodology but more of standards and conventions for managing the project. The Agile Framework includes –Scrum, Kanban, Extreme Programming and Adaptive Project Framework. The Change Management Methodologies include-Event Chain Methodology (ECM) and Extreme Project Management (EPM)

Agile projects are successful on the same level as the other methodologies but they face various challenges when being implemented. Some of them are:

  • Inadequate experience with the Agile methods
  • Organization structure and existing organizational borders
  • Procurement laws
  • Company values at odds with agile values
  • Scheduling the Project tasks
  • Monitor and control project scope
  • Improper Knowledge Management
  • People focused rather than process and plan focused.
  • Lack of predefined standards and requirements
  • Managing large projects and Distributed teams

Various actions can be considered to eliminate or reduce with the failures and challenges. These can be-

  • Selecting and Customizing the Right Methodology-Every Agile method has its own techniques. Some advocate iterative development and incremental release like Scrum and Extreme Programming. Lean and Kanban are continuous processes. The method should be used as per the organization and the project.
  • Use a Traditional Methodology with Agile Practice
  • Use Hybrid Agile approaches
  • Using Problem solving techniques as BART(Boundary Authority Role Task) to determine the root cause of problems that occur during Agile implementation.
  • The proper alignment of the different levels of management before any Agile Methodology is implemented.

An example of agile methodology in different projects

Project management methods can be used in all sectors; however, not every method can be used effectively and efficient in all projects. The same idea is with agile project management, it is mostly used in IT projects due to its flexibility and effective development process. It is easier to see the difference if we take two industries – IT and construction, and compare the usage of this technique.

The main issues and struggles are connected to the time of the projects and deadlines, budget, scope, involving of investor in the project. The problems occur right at the beginning, when we try to implement agile to construction projects, as in agile there is no deadline. In agile project management, the team has sprints, what is 2-4 weeks period of time, in which the team is working on the specific tasks and produces the outcomes. The idea is that every new sprint the team adds new features to an existing product and the process of developing is infinite, as we can develop the new functions every new sprint. In construction projects flexibility is lower, as every new movement may increase the price and the deadlines. The phase of planning in huge projects is created in such way that some tasks are connected and because we have to produce a specific outcome, there are steps which have to be followed and cannot be skipped or mixed. We cannot start installing the doors in the building, before we build the main building. That is why we have to follow the plan and deliver the results, which are in the scope. Everything what is out of the project scope should be transferred to the other project or to be discussed with the investor, as it increases the time and budget.

Also, in huge projects there is no need and not always possible to meet with the investor every two or three weeks to discuss the progress. Sometimes it takes one month to get one task done, for instance to receive only the certification and approval from the local government. However, in Agile it is crucial to meet with the owner often and receive the feedback.

Therefore, the agile approach would be very ineffective and costly, as the main agile beliefs do not cross with the reality of huge construction projects.

Agile aligns the needs of the business with the software development and its success is apparent. Its projects are focused on the customers. It also encourages their participation and guidance. Due to this, Agile Methods and its principles has become a comprehensive way for the software development in the whole industry.

In development of software, a reasonable approach is being offered by the Agile in this highly volatile environment. It has been proved by the Agile Methods that when they are being applied under certain circumstances with projects having lower risks, the quality and the productivity of the team and the project increases. When the other agile principles are combined with these Agile Methods, a combined effect is produced which is greater than the sum of their separate effects. This provides a more acceptance for the goals, the ideas and the projects.

Software changes which are generally ungoverned can be very costly sometimes. Agile methodology is very useful as it can address these changes. But these methods are not appropriate for every project. To check the approachability of the Agile Methods, the characteristics of the project must be considered. Its impact on the project, the people and the processes should also be considered.

A management and development methodology is provided by the Agile Methods in software management which provides a very good support if the requirements are rapidly changing or are ill-defined. Even if it is questionable to apply these methods on certain projects, the Agile principles may be still be very effective. If there is a team which is available, able as well as capable of using these principles and applying them, then the usage of Agile Methods should be considered to be applied on these projects. Otherwise, traditional approaches should be used to reduce the risks.

References

Retrieved from "https://ceopedia.org/index.php?title=Agile_project_management_methodology&oldid=59395"