Real Agile brings real benefits to everyone involved in software development, from business to development teams.
Currently, there are less and less teams working in methodologies other than Agile, while the level of their maturity is very diverse. So are they really Agile, or are they only Agile in name? In this article, you will not find the definitions used in Agile methodologies, but you will find out what we think is really important for a team to be really Agile.
- 3 Magic roles
- Power of Definition of Done
- Power of iterations and empiricism
- Well tuned development team
In our daily work, we use agile methodologies such as Scrum or AgilePM. We derive the best from these methodologies, which makes us work better and better with each sprint. We know what is really important and what is not, what problems the business world has in the IT area and how we can solve them. There are many publications thoroughly describing each of the methodologies we use, but look how we see them at glance…
The scrum methodology is characterized by the pursuit of the scrum team towards a common goal in an iterative approach. The team gains knowledge and experience with each successive sprint, which is the basis for further improvement of both the effectiveness of the scrum team and the resulting product. Scrum gives the opportunity to focus and constantly focus on the business need, or to ensure the right speed of adaptation to the changing environment and market, which is crucial for the project’s success. “Gives the opportunity” was used consciously, because scrum alone does not solve anything by itself. It only gives the framework in which the teams operate, while the effectiveness depends only on the level of maturity. It is important to understand that the true value of Scrum is not measured by running scrum events or by producing artifacts, although they are very important. The real value of scrum is when the team takes full responsibility for the implementation of a given business initiative from start to finish, supporting it with all their experience and knowledge. The success of the project is the success of the team. This is the essence of Agile.
After the first fascination with the Scrum methodology, part of the business world saw that, from a formal point of view, Scrum alone is not sufficient to manage projects. Therefore, as a result of evolution, a methodology was created that combines the Agile world with the features of classic methodologies such as Prince2 or PMBOK. In such project management, the intensive participation of business in the process of creating a solution is important, often it is a person delegated to such work. It actively participates in the production process. On the one hand, it facilitates faster decision making, and on the other hand, it is the allocation of additional resource. AgilePM is, however, quite well scalable depending on the situation and the complexity of the project. The main goal is to meet the business need, reduce the excess of formalities and deliver on time. Below are the main differences between the Classic and Agile approaches.
Whole article available on our workshop site.