What is agile project management?

agile project management

The agile approach — a few words of introduction

Everything has its pros and cons

  1. First of all, a client has a strong feeling of being involved in the whole process because of the direct cooperation with a project team. This way, the customer not only gains a strong feeling of project’s ownership but can also make changes at an early stage of each phase and adapt the product to their expectations. Addressing problems quickly enough saves a lot of time and gives the customer a sense of empowerment.
  2. Another important convenience offered by Agile is the fact that the team can develop a basic version of working software and modify it later. It enables the customer to use the product faster and thus promote their services earlier and make money even before the product is released with all functionalities. New features can be added in future iterations.
  3. We can’t forget that Agile also provides a greater level of transparency which results in higher trust, openness, and communication for all parties involved. Last but not least, thanks to constant feedback, the development is often more user-focused which allows creating a unique product.
  4. On the other hand, the high level of client involvement may also be a drawback for customers themselves — they may not have time for meetings or may not be interested in participating at all. What’s more, customer involvement often leads to new ideas connected with new functionalities which can increase the overall cost of the project.
  5. It is also important to have close working relationships in the team which is possible thanks to meeting in person in the same location. As we know, it’s not always possible. However, nowadays we have a lot of solutions enabling such contact even from a distance, e.g. Google Meet or Zoom.
  6. Apart from that, the iterative nature of this methodology may lead to refactorings if the first arrangements drafts don’t include the full scope of the system. Those refactorings are necessary because they help prevent a reduction in a project’s quality.

The Agile methodology — crucial steps

  1. Discovery — before starting any new project, the team has to find out more about the client’s needs, visions, and goals. It happens during a meeting with the team when there’s a chance to exchange ideas and brainstorm together.
  2. The Product Backlog — during the first phase the team creates a list of all functionalities that are desired by a client or their customers. The client has a chance to determine which elements are the most important and should be focused on first. It helps the team plan their work.
  3. Iterations — once the wishlist is completed, the team begins to work on the project. Each sprint which is a determined period for one iteration lasts usually 1–4 weeks, but it depends on the project.
  4. Additional Sprints — they are conducted if there’s a need to work on additional functionalities of the project. Each Sprint improves what has already been done and adds some new features.

The Team of Agile

How to choose a methodology of development ideal for the project?

  • client’s preferences,
  • client’s availability,
  • client’s openness to possible cost variations,
  • client’s tolerance for scope changes,
  • project complexity,
  • project size,
  • implementation to the market date.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store