Agile!
Salve Agilis Project Administratores!!
The word agile comes from the Latin ‘agere’ meaning ‘to keep in movement or set in motion’ and from the related adjective ‘agilis’ meaning ‘quick and nimble’. Agile first appeared in late Middle English sometime in the 1580s and was directly derived from the French.
You may have heard the word Agile at school, at work, or perhaps just as a lifestyle. Agile basically works with the principle of doing a job quickly and with high error compensation. When you think about your daily life, don’t you want to reach a point with fewer and safer steps? When we ask this question to the software world, agile methodologies answer our question.
The word software is not far from our lives anymore. It has even become a part of our lives. Let’s take a closer look at how software processes work to understand agile.
Like every production process, the software process also has a development cycle. This cycle is called the “Software Development Life Cycle”. The activities of the software development process begin with Planning. Requirements are determined by Analysis. A prototype is created during the Design phase, it is carried out during the Implementation phase. Errors are debugged in the Test and Integration section. Errors in the operating system are intervened during the Maintenance phase.
What if I asked you how you would make these processes faster and higher quality? What would you do differently at what stage? What sub-processes would you add? So how would you manage your project more agile? I’m sure you all have different solution scenarios. Turks have a proverb like this; “Every man’s way of eating yogurt is different.” So everyone’s optimal way to accomplish a task is different. That’s why there are many methodologies in agile and there is always room for new methodologies. Blindly sticking to a methodology is never agile. Many methods such as Kanban, Scrum, XP, Crystal etc. have been developed to improve software processes.
Before I come to the end, I would like to talk about the most popular agile methodology, SCRUM;
It is an innovative product development approach, called the holistic or “Rugby” approach. Scrum provides transparency in communication, creates an environment of collective accountability and continuous improvement.
At the core of Scrum there is a Scrum Team.
The Scrum Team consists of Developers, Product Owner, and Scrum Master.
Developers are individuals on the Scrum Team committed to creating any portion of a usable Increment in each Sprint.
The Product Owner is responsible for maximizing the value of the product created as a result of the work of the Scrum Team.
The Scrum Master is responsible for the adoption of Scrum.
It does this by helping the Scrum Team and everyone within the organization understand Scrum theory and practices.
Get Project Manager's Diary’s stories in your inbox
Join Medium for free to get updates from this writer.
Scrum consists of Sprints. In these sprints, work divisions are made and valuable work pieces are completed in a certain plan.Sprints are of fixed duration, which can be a month or less. As soon as the previous Sprint ends, the new Sprint begins.
The most important activities within Scrum are the various meetings that are held frequently and regularly. These;
Sprint Planning: It is the activity that starts the Sprint, where the work to be done in that Sprint is planned. This plan is prepared with the cooperation of the entire Scrum Team.
Daily Scrum: These are 15-minute meetings held at the same place at the same time every day. In this meeting everyone talks about the progress of the process and the problems, if any. In this way, if there is any problem, the scrum master eliminates this problem.
Sprint Review: It is done at the end of each sprint. The sprint is reviewed and the resulting product is evaluated. If there is an error, it is noticed and corrected.
Sprint Retrospective: It is the meeting where the quality of the work done during the sprint, the right and wrong are evaluated. This meeting is an opportunity for the scrum team to improve itself. “What can we do better?”, “How can we do better?” answers to questions are sought.
I tried to create as small and efficient information set as possible. They are such long and detailed topics so a book can be written on Agile or Scrum. But they are also very entertaining topics.
If you’ve come there, it means you have basic knowledge on this subject. If you are curious about the details or want to talk about it, you can always write to me :)
If you are interested, I would like to share with you my thesis about Design Sprint, which is an Agile software design process.
https://drive.google.com/file/d/1-mLO8SmF0SRUw5M9cvJtZA0wWZf8qy6x/view?usp=sharing
Stay Agile!








