Agile methodologies are derived from one manifesto. The background mentality of this manifesto is simple and formed with a few sentences;
"We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. " (source:agilemanifesto.org)
And following 12 principles are known for agile processes;
The following future posts are proposed for candidacy;
1. Agile Methodologies as a Scrum and Kanban Comparison: a detailed definiton of Scrum and Kanban, Roles, Meetings, Performance Measurement, Solution approach of software development life cycle, and comparison of all for two approach.
2. How to Rationalize Agile Meetings: Detailed flow of meetings and behavioral attitude.
3. Added Value of Agile Methodologies: How projects gather value from agile methodologies.
Agile Related Posts:
1. JIRA vs Redmine Comparison With Respect to Features and Specs2. Setting Up an Open Source Development Environment
3. Spotify Agile Culture
