Home / Process / Methodology

Project Management Methodology

In order to achieve goals and planned results within a defined schedule and a budget, a manager uses a project. Regardless of which field or which trade, there are assortments of methodologies to help managers at every stage of a project from the initiation to implementation to the closure. A methodology is a model, which project managers employ for the design, planning, implementation and achievement of their project objectives. There are different project management methodologies to benefit different projects.

Agile Project Management

Agile project management is a most flexible approach to software development. Agile projects go through a number of smaller cycles called sprints. Each sprint has a backlog and includes design, implementation, testing, and deployment stages, completed within the pre-defined scope of work. At the end of each sprint, the team delivers a potentially shippable product increment. Ultimate features of Agile are interactivity, flexibility and fast turnaround, ease in prioritizing tasks, increase of team efficiency due to daily task allocation & clear project visibility through the simple planning system. Agile project management focuses on adaptability to changing situations and constant, regular feedback – whether it’s from the client or from other members of the team.

Waterfall Project Management

Waterfall has been a dominant software development methodology among traditional methodologies since the early 1970s. It takes a linear approach to the project execution, its internal phases are sequential and executed in a chronological order. A waterfall is characterized by:

  • Strong emphasis on planning and specifications development, which takes up to 40% of the project time and budget.
  • Tight control over the development process.
  • The strict order of the project phases; a new project stage does not begin until the previous one is finished.

The methodology works best for clearly defined projects with a single deliverable and fixed deadline. In this case, it enables On-time, on-budget delivery, low project risks, and predictable final results.

Adaptive Project Framework

Adaptive Project Framework was born in two client engagements – one a product-development project and the other was process-design project management. According to the adaptive approach, projects are not just a collection of activities that need to be completed on time. Instead, projects are business related processes that must deliver business results. Our model considers the strategic as well as the tactical aspects of project performance in the short and the long term, and it considers the points of view of different project stakeholders, including customers and businesses.

Dynamic Systems Development

DSDM(Dynamic Systems Development Method) is a development methodology not really and algorithm. Dynamic programming is the use of sub problems and memoization(storing in memory results) to solve larger problems which is a separate thing. Basically DSDM is a methodology that like scrum or other agile one is iterative and its based on the fact that there is an exploration time has part of the process. The other thing is that it was based on focusing on deploying on time. So you would time-box and item from it. I got to use for one project on MS a long time ago it was interesting. It had a problem of admitting when a deadline could not be reached and people just scramming to it. First released in 1994, DSDM originally sought to provide some discipline to the rapid application development (RAD) method. This is the successor of Rapid Application Development (RAD) methodology.

Information Technology Infrastructure

ITIL is an acronym; it stands for Information Technology Infrastructure Library. It’s a set of books created by the British government after embarking on a huge research project in an attempt to improve their own internal IT departments. Their research turned into the largest collection of “best practice” in IT, collected from organizations around the world. So, when you hear “ITIL” – remember it’s the set of books. You don’t “implement ITIL”, you implement something called ITSM. The most important thing about the ITIL books is their subject matter: the concept of IT Service Management (ITSM). ITSM is about providing great services to customers – services that add value. Practicing ITSM helps IT organizations better understand their customers’ needs.

Rapid Application Development

Rapid application development (RAD) is a software development methodology that uses minimal planning in favor of rapid prototyping. A prototype is a working model that is functionally equivalent to a component of the product. In RAD model the functional modules are developed in parallel as prototypes and are integrated to make the complete product for faster product delivery. Historically, RAD systems have tended to emphasize reducing development time, sometimes at the expense of generating efficient executable code. Nowadays, though, many RAD systems produce extremely fast code. Since there is no detailed preplanning, it makes it easier to incorporate the changes within the development process. RAD projects follow iterative and incremental model and have small teams comprising of developers, domain experts, customer representatives and other IT resources working progressively on their component or prototype. The most important aspect for this model to be successful is to make sure that the prototypes developed are reusable.