Here are the topics that we’ll cover in this complete guide to Agile & Scrum:
What is Agile?
A Brief History on Agile
What are the 12 principles of agile?
What are the Benefits of Agile?
What Is Scrum?
A Brief History on Scrum
Scrum Methodology & Process
Different Roles in Scrum
Benefits of Scrum Methodology
How are Scrum and agile different from traditional methodologies?
Waterfall Approach
What's so bad about Waterfall development?
Case Study
What is the difference between agile and scrum?
Should I be using Scrum, Kanban, or another framework of agile?
How will Agile and Scrum help me?
How do I get started with Agile and Scrum?
Wrapping Up
WHAT IS AGILE?
Agile is a time-bound agile project management methodology that follows an iterative approach that builds software in increments from the start till the completion of the project.
It breaks down the larger project into phases and then builds the requirements in timeboxed iterations which typically last 2-4 weeks.
A Brief History on Agile
The history of Agile software development dates back to 2001 when 17 software developers came together at a resort in Utah to discuss lightweight development methods.
This discussion led to the inception of the Agile Manifesto. It prioritized four values-
1. Individuals and Interactions over tools
Historically, tools and processes have been prioritized over people. The Agile Manifesto suggests that though those are important, the team members take precedence.
The team members are instrumental to the success of the project. Even the best tools are ineffective in the hands of unskilled people. The success of the project is largely reliant on the mutual interaction and communication between the team members.
Interpersonal communication between team members helps the team members solve any problem.
2. Working software over comprehensive documentation
Throughout the ages, developers have been working on creating documentation. It may serve a purpose but without a piece of working software, it is worthless.
The customers should be given the working, functional software. Feedback can be taken in loops to make changes for future releases.
3. Customer collaboration over contract negotiation
Since time immemorial, contracts would be drafted first where customers would detail the entire product requirement. This led to a disparity of contract mentioned, what the product did, and what the customer desired.
The focal point should be continuous development. When customers are asked for feedback regularly, you can build a product that delivers the optimum value.
4. Responding to change over following a plan
Do you like rigidity where things don’t change according to circumstances?
How realistic would an affirmative answer be?
It isn’t possible but development plans were never flexible to accommodate things as per requirement. A dynamic development plan is the need of the hour where requirements can be added according to the need.
To view the full blog and this blog "What is agile and scrum?" is originally published on Agilemania website.
