WiredWorx || Web design || SEO || Bournemouth
Web design, website development and search engine optimisation (SEO) in Bournemouth, Dorset, UK.
Home ·
Website and SEO · Kanban vs Scrum pt 1
Kanban vs Scrum pt 1
17.06.2010. 12:29
There are a million and one architectures on which to base a development project, but since we are an agile lot here at WW we lean towards agile methodologies. We have previous experience of using both Kanban as well as SCRUM but are finally putting together an in depth evaluation of both frameworks to see which suits us best.
For those new to both approaches, the idea of both is simple - develop and deploy working, functionally perfect code as quickly as possible. This sounds daunting at first - people generally associate speed with lower quality but both approaches couldn't be further from the truth - the 'normal' waterfall standard development life cycle where requirements are mapped out at the beginning and then delivered at the end (which could be a year or more down the line) has obvious downfalls. The most obvious being that during that time requirements will have no doubt changed. Even if the customer doesn't think they have changed, once they can see the product and visualise how it will work, there are almost always changes then. This is when RAD and agile really come into their own.. At the end of each task (kanban) or sprint (SCRUM) there should be working functionality which the customer can see and then interrogate to make sure it is performing as they desire.
In further articles we will go on further to look at the differences between these methodologies and see which is proven to work better for us...
Comments
No commenting allowed at this time.
No commenting allowed at this time.
