
On Agile: SCRUM
This piece is yet another installment in my series on Agile methods and mindsets. Each article in the series progressively elaborates on the subject and shouldn’t be consumed on their own, but along with the other entries. The form in which the articles are split isn’t along any lines except for those of my convenience. At a later stage, I may re-organise the content so one article flows into the other, however, my primary concern for now is to share the knowledge in my head as quickly as possible. Please please feel free to share your thoughts and excitement in the comment section below. Thank you. Agile is a project management approach that was first adopted by cool people building software. Today, is adopted to drive the delivery of different types of projects irrespective of the domain. The Agile Manifesto, puts forward 12 principles to guide software teams (and really any team) that uses or plans to adopt the Agile mindset. Some key advantages of Agile is that the teams detect potential failure(s) in delivering the project early and can then take steps to remedy the situation. The team(s) understand change and are quite adaptable to it. And the customer knows what is being built, sees the work being done take shape and can thus re-evaluate their priorities, bring new information that can impact the product being built to the attention of the project team, commence the process for making changes etc. At a very high level, Agile, lets teams build and deliver



















