What Is Agile and What Is It Used For?
Agile is a project management approach that divides a project into short cycles and has a working piece delivered to users for evaluation at the end of each cycle. The article covers the Agile Manifesto, Scrum and Kanban, its difference from the waterfall model, and the projects in which it works well.
Nurullah Okatan · Content Writer
· Updated: · 15 min read

Agile is a project management approach that divides a project into short cycles and delivers a working piece at the end of each cycle. The plan is updated after each delivery with customer feedback, so misunderstood requirements are noticed within a few weeks.
The origin of Agile and the Agile Manifesto
The Agile Manifesto was written in 2001. According to boenstitu.com, it was prepared by 17 software developers who came together. The aim was to find solutions to the delays and scope problems experienced in software projects. According to patika.dev, Agile became formalized with this manifesto.

The manifesto defines four core values and 12 principles. boenstitu.com states that these values are based on customer satisfaction, team collaboration, quick response and flexible work. The four values, by comparing two things, state which one should be given priority:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
The manifesto does not ignore the items on the right. It values the items on the left more. The 12 principles also turn these values into daily work: frequent delivery, business people and developers working together every day, and the team regularly reviewing its own way of working at fixed intervals.
Agile was born in software, but it was not limited to software. According to ilkimdilara.com, the approach is used today in many sectors. Marketing campaigns, product design and content production are examples. For applications on the software side, custom software development articles contain detailed examples.
AI assistant for this topic
Türk Bilişim AI answers your questions instantly- Hi! Ask whatever you're curious about.
How does Agile differ from the waterfall model?
The key difference is when the requirements are defined. In the waterfall model, requirements are written and approved once at the beginning of the project. In Agile, they are revisited in each cycle.
The arXiv study «Agile Islands in a Waterfall Environment» clearly describes this difference. In traditional methods, requirements engineering proceeds through preliminary stages of analysis, planning and documentation. In agile development, the same work is an iterative process that continues at every step of development. In waterfall, design, coding and testing begin one after another only after the requirements document is closed.
In Agile, requirements are revisited because customers often clarify what they want when they see a working piece. According to f4e.app, Agile divides the project into small parts and receives continuous feedback. Each piece can change the priority of the next step.
| Topic | Waterfall model | Agile |
|---|---|---|
| Requirement definition | At the start, all at once | Revisited in each cycle |
| Delivery | Whole product at the end of the project | A working piece at the end of each cycle |
| Change request | Off-plan work, requires additional approval | Added to the list of the next cycle |
| Customer involvement | At the start and in the acceptance phase | At the end of each cycle |
| Documentation | Detailed, in advance | As needed, as work progresses |
The two methods can be used together. The same arXiv study is based on 18 interviews and one focus group conducted in two departments of an automotive company. The study examines how Agile teams work within an organization operating in a waterfall structure. In the common arrangement, contracts, budget and the master schedule follow waterfall logic, while development proceeds in short cycles.
Looking for Android App Development?Applying Scrum and Kanban in Agile
Scrum and Kanban are two common frameworks that turn Agile into daily work. According to f4e.app, Scrum is the most widely used Agile methodology and is shaped around specific roles and meetings.
In Scrum, work progresses in fixed-length cycles called sprints. patika.dev The source states that sprints usually last 2–4 weeks. boenstitu.com However, it gives this range as 1–4 weeks. The duration is chosen once for the team and kept constant throughout the project. ilkimdilara.com According to the source, the goal is to present a completed product or product increment at the end of each sprint. This increment is not an unfinished draft. It is a tested function that users can try, such as a login screen, a payment step, or a report page.
Daily Scrum is a short status meeting that the team holds every day at the same time. f4e.app notes that this meeting lasts 15 minutes daily. Each member states three things: what they finished yesterday, what they will do today and what obstacle they face. Resolving obstacles is left to a conversation with the relevant people after the meeting.
Kanban does not use fixed-duration cycles. It shows the workflow on a board. According to ilkimdilara.com, this board makes the status and priority of work visible at a glance. A typical board has three columns:
- To do: work ordered by priority
- In progress: work currently being done
- Done: work that has been tested and accepted
Teams often set an upper limit on the «In progress» column. This way, unfinished work does not pile up. Examples of how these two frameworks are combined in mobile projects can be found in mobile app development articles.
What does Agile bring to a project?
Agile's real gain is that risk becomes visible early. According to patika.dev, each iteration produces a working piece of software that the customer or end user evaluates. techcareer.net also writes that at each step a function of the project goes live and improvements are made based on customer feedback. A wrongly designed screen is not noticed at the end of the project. It is noticed within two or three weeks, and only that part is revisited.

Agile is useful for projects where the full requirements are not known at the start. A new digital product, an application whose shape will be determined by user behavior, or a service whose market is tested are examples of this. There are also projects that struggle with it. In work whose scope is fixed by regulation, the cycles do not bring much flexibility. The same thing happens in projects where every change must pass formal approval. If no one on the client side gives feedback at the end of a sprint, the cycles are wasted.
In web applications, the first cycles are usually devoted to user login and the core data flow. Reporting, authorization management, and integrations are left for later sprints. In mobile applications, release sprints are planned separately because store review is a distinct step. Türk Bilişim, described as one of Turkey's leading AI Chatbot & Customer Assistant companies, has worked as a digital agency since 1998. The company has also been developing artificial intelligence solutions since 2022. In the company's Custom Web App & SaaS and Mobile Application services, design, software, and release are carried out by a single team. In this setup, feedback at the end of a sprint moves into the next cycle without waiting for handoffs between teams.
Steps to clarify before starting to work with Agile
The scope, schedule and feedback arrangement must be clear before the first sprint. Agile keeps the plan flexible, but without a starting point the cycles lose direction.
- A short discovery meeting records the need and the goal in writing.
- Work items are ordered by priority, and what must be included in the first release is set aside.
- The sprint length is chosen and the main schedule is roughly divided according to this length.
- On the client side, the person who will take part in the end-of-sprint review is determined.
The start described on the company's frequently asked questions page follows this same sequence. First, an discovery meeting is held, and then scope, timeline, and proposal are shared.
Feedback is collected at least at the end of every sprint. A quick communication channel is also opened for questions that arise during the day.
The cycles continue after release. At this stage the content of the sprints changes: improvements based on user data, bug fixes and security updates come to the fore. Türk Bilişim provides maintenance, updates and support after release. For this reason, writing the frequency of post-release cycles into the contract from the beginning makes it easier to plan the first year's budget.
Looking for AI Strategy & Consulting?Frequently asked questions
Are Agile and agile methodology the same thing?
Yes, «çevik» is the Turkish equivalent of the word Agile. Both terms describe the same approach and the same manifesto.
What is the difference between Scrum and Agile?
Agile is an approach made up of values and principles. Scrum is a specific framework that puts this approach into practice with roles, sprints and meetings. Kanban is another framework that implements Agile.
How is the budget determined in an Agile project?
The budget is usually calculated from the team size and the number of planned sprints. The scope is not fixed. Priorities are set, and the most valuable work is delivered until the budget runs out.
Can a small team use Agile?
It can. For a team of three or four people, a Kanban board and a weekly client review are usually sufficient. Separate role definitions are added as the team grows.
Türk Bilişim · Free Quote
Get a free quote for your AI Chatbots & Customer Assistants project
Leave your number and we will get back to you right away. The call is free.
Your request is saved on this device
We can't reach our server right now. Your request will be sent automatically once the connection is back. To talk right away:

Share this article
Comments
Comments
No comments yet.
















