What is Agile?
We can find multiple definitions for this term. But if you ask me then I will simplify it as a software development and management methodology and consistent iterations with interactivity.
Other definitions are
– Agile is a time-boxed, iterative approach to software delivery that builds software incrementally from the start of the project, instead of trying to deliver it all at once near the end.
– Agile is a process that helps teams provide quick and unpredictable responses to the feedback they receive on their project. It creates opportunities to assess a project’s direction during the development cycle. Teams assess the project in regular meetings called sprints or iterations.
– An agile is a very empowering process that helps companies design and build the right product. The management process is very beneficial for software companies because it helps them analyze and improve their product throughout its development. This enables companies to produce a highly valuable product so they stay competitive in the market.
Under the Agile umbrella, we have multiple branches like
- Sprint (A set of specific time for a specific work to be done)
- Scrum (An agile way to manage project)
- Kanban (Best for continued delivery and not overburdening the coders)
- XP (Extreme Programming for faster development)
- Lean (Value Stream mechanism that delivers the value to the project)
- Crystal (most lightweight and adaptable approaches in developing software)
- FDD (Feature-Driven Development)
- DSDM (Dynamic Systems Development Method)
I personally practiced Sprint, Scrums, Kanban but others I couldn’t get a chance yet to practice. I don’t even know what are those. But definily I will get those to be in my knowledge book.
Agile Sprint Retrospective
It doesn’t matter how much a scrum team is good but we all know that there is always an opportunity to improve and make things in a better and more better way. Usually, sprint retrospective is done right after sprint review. You can say that it’s the last thing to do in a sprint. It is recommended to have an agile sprint retrospective meeting for 1 hour. The purpose of the retrospective is to get the answers from each team member for the following questions
- Start doing
- Stop doing
- continue doing
if we describe the above questions then those are related to the efficiency and improving developments by keeping the hurdles intact. I can summarize it by naming it brainstorming.
Agile Sprint Retrospective meetings are conducted by the scrum master and all the team members including product owner should join this meeting.
A good to know the question and I will answer with my personal experience as I am using it for years now.
- Best communication structure and bridges
- Clients love it and off course all the stakeholders love it. The big reason for this is clear visibility of what we are doing? whatwill wel do? When will we do?
- Quality increased rapidly
- % of blockers solve quiet faster
- It’s fun as it makes team actively involved.
Why No AGILE?
Don’t think to use it in case of a Very Dynamic Client with Constant Price 🙂 Agile is directly proportional to $$