Agile project management is more than just a fad. The first agile methods in the field of software development were already developed in the mid-1990s. They are based on empirical models which are used when the final result is not yet or only with difficulty predictable at the beginning of the project. Accordingly, with agile project management you can change or adapt the requirements during the course of the project. Among agile approaches Scrum is the best known and most widespread method.
In 2001, agile project management with Scrum is established in the book "Agile Software Development with Scrum", but only for software development. In 2003 the spectrum is extended to the entire project management with Scrum ("Agile Project Management with Scrum") and thus to the entire company.
In rugby, the word Scrum itself refers to the crowd of players throwing in the ball. The analogy is intended to underline the work in small, self-organized units, which are given only one direction (goal) from the outside, but which determine the tactics of how they want to achieve the common goal.
In the Scrum world you have three roles. There are:
The Product Owner is your customer or represents your customer. He makes sure that the customer's interests are implemented in the project.
The Development Team works independently and autonomously on the implementation of the customer's wishes.
The Scrum Master acts as a coach, who ensures that the team can work as smoothly as possible.
Scrum is currently the most popular method for agile project management.
But there are many more agile techniques like Kanban, Extreme Programming, MVP, Feature Driven Development, Test Driven Development or Crystal Clear, with which you can manage agile projects.
The term "agile project management" is becoming more and more a generic term for the approach, which differs significantly from the classic waterfall method.
Developed in the 1950s, Kanban (Japanese for "signal card") originally comes from the production control system of Toyota.
The aim is to efficiently control each manufacturing or production stage and to optimize the material flow. When transferred to IT, Kanban elements from Lean Production, Lean Development and the Theory of Constraints were added. The result is a separate agile project management system in which the number of parallel tasks is limited, thus achieving shorter throughput times.
This enables you to avoid bottlenecks for agile project management, as they become quickly visible.
The following principles help you to control your projects for agile project management with IT-Kanban:
Design Thinking is a user-oriented method for solving problems and developing new ideas. The team usually consists of members from different disciplines. They take the user's perspective and focus on the user's wishes and requirements.
You can divide the process of Design Thinking into six steps for agile project management:
The DevOps model is characterized by high IT and software relevance. DevOps is an artificial word made up of the terms development and (IT) operations.
The purpose of the model is to achieve more effective and efficient cooperation between the areas of development (Dev), IT operations (Ops) and quality assurance (QA). DevOps thus refers to the cross-departmental, company-wide cooperation of managers, developers, testers and administrators with the involvement of the customer. All those involved pull together and have the common goal in mind: the provision of high-quality software.
With DevOps you can develop software for agile project management faster and with better quality. It also improves the collaboration of your teams.
Regardless of which model you choose, agile project management brings you advantages:
You profit through:
These advantages give you a significant competitive edge.
In agile project management, however, you should pay attention to company-wide project and resource management, because the agile approach requires:
The introduction of agile project management is a challenge, but not witchcraft. It is important that you start small and as simple as possible:
If it is your first agile project, it would be important to record all successes and failures after completion in order to learn from them. Be sure to document what worked well, where you still have room for improvement or where you should use hybrid project management
Then optimize your agile project management and start your next project!