In 2001, 17 software developers met at Utah to put together ideas they had on lightweight development methods. They agreed on 12 Principles that turned into “The Agile Manifesto”.
Agile software development is about doing things based in short term plans instead of spending a lot of time planning a big strategy. According to the Agile Manifesto individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation and responding to change over following a plan.
Scrum is the most common approach to agile development. It’s an alternative to the traditional waterfall method, as each process isn’t dependant on its previous process. All processes happen at the same time, quickly and in an interconnected, multifunctional matter. Then, after all processes are done, analysis and conclusions are reached and a whole set of new interactions can start.
If you want to know more about scrum you can watch the following video:
Agile development provides a way to know the direction of a project THROUGHOUT the development cycle, not before.
Scrum is a lightweight agile project management framework with broad applicability for managing and controlling iterative and incremental projects of all types.
With “Scrum” methodology, the “Product owner” works closely with the team to identify and prioritize system functionality in form of a “Product Backlog”.
Scrum is a sub-group of agile:
Agile is a set of values and principles that describe a group’s day-to-day interactions and activities. Agile itself is not prescriptive or specific.
The Scrum methodology follows the values and principles of agile, but includes further definitions and specifications, especially regarding certain software development practices.
Organizations that have adopted agile Scrum have experienced:
Reduced time to market
Improved stakeholder satisfaction
Better team dynamics
To get started with agile Scrum, it is not uncommon for an individual Scrum team to use simple Scrum tools like a whiteboard, sticky notes, or a spreadsheet to manage the product backlog and the progress of the sprint backlog items in each sprint.