Answer the question
In order to leave comments, you need to log in
What is agile development?
As far as I understand, is this an approach to creating a product when tasks and technical specifications can change in real time?
Is it so?
Thanks in advance for the detailed answer!
Answer the question
In order to leave comments, you need to log in
Development methodology.
Waterfall: we carefully plan everything, set deadlines, develop, deliver.
Agile: Roughly plan, analyze, set a deadline, plan for the current iteration, develop, plan for the current iteration, develop... , hand over
Problems Waterfall:
If someone is doing well, everyone is waiting. If you need to add something, it's very difficult, because the planning phase was very long and thorough, and to change something means you have to change everything.
If the plan states that we do this first and then that, it may happen that some people who will do "that" will kick "cucumbers" for a while while waiting for the first people to do "that".
Pros of Waterfall:
Everything is planned, everyone knows exactly what they will do when.
Problems of Agile:
People need to be mature enough to keep themselves busy with work - Agile in a bureaucratic environment will simply fail.
Advantages of Agile:
Virtually no downtime for anyone - everyone can always keep themselves busy with tasks.
If new requirements appear, they can be introduced into the project at almost any stage without much harm. The main thing is that this is technically possible (in the case of waterfall, the problem is precisely at the level of statements and plans, that is, bureaucracy)
Adequate use of labor force - if someone does not have current tasks, they can officially be occupied for other projects.
Agile is not a super feature, it is a tool, or rather an approach to work planning, but you need to be able to use it.
I am very interested in this Agile topic. My 2nd penny in Agile application. Many people think that Agile is a way to develop new products. In fact, Agile is the practice of quickly implementing an already developed solution. That is, the product has already been set by someone - a client or a boss. The task of Agile is not to create something new, but to implement it quickly. Hence, a lot of problems in understanding the tasks of Agile and the roles of development participants, especially the Product Owner. Summarized my experience in the form of a simple presentation. You might be interested in taking a look: www.slideshare.net/ishmelev/agilerus
Agile is not a development method, but a way of thinking!
The basic principles for decision making are specified in the manifest link above.
You cannot compare Methodologies and Values on which a person makes a decision.
You can compare Scrum, Kanban, Waterfall, etc. And then, Scrum and Kanban are not a methodology, but a framework.
Everything about Scrum, Kanban is described in a very accessible language here:
https://vimeo.com/90713041
And on which projects it is better to use and what Agile is, you can understand here
https://vimeo.com/90713060
Agile is a way of thinking by and large, not a methodology. Agile - defines the core values and principles on the basis of which various frameworks (methodologies) such as Scrum are created. Learn more about Agile here - mahamba.com/ru/gibkaya-metodologiya-razrabotki-agile
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question