{"id":2771,"date":"2016-08-30T12:47:05","date_gmt":"2016-08-30T11:47:05","guid":{"rendered":"https:\/\/marvel7077.wpengine.com\/?p=2771"},"modified":"2020-12-14T08:27:44","modified_gmt":"2020-12-14T08:27:44","slug":"incremental-ux","status":"publish","type":"post","link":"https:\/\/marvelapp.com\/blog\/incremental-ux\/","title":{"rendered":"Incremental UX"},"content":{"rendered":"

The Agile approach<\/a> has in many organisations become the expected way of working. There have been many articles<\/a> and books<\/a> around the challenges of designing in an agile environment.<\/p>\n

When building a Minimum Viable Product<\/a> (MVP) there are many competing factors, and with the pressure to release something demoable every sprint, features can get compromised in a way that requires rework later down the line.<\/p>\n

A method that we\u2019ve been using at Caplin<\/a> for the last 18 months is \u2018Incremental UX\u2019<\/em>\u200a\u2014\u200abringing the concept of MVP down to the component or feature level.<\/em><\/strong><\/span><\/p>\n

<\/div>
<\/svg><\/div>

\u201cBringing the concept of MVP down to the component or feature level\u201d<\/p><\/span><\/blockquote>\n

The basic idea is to have a planned progression (leaving room for improvements through testing) of a feature that adds functionality at each stage.<\/p>\n

A common requirement of all our products (web applications for real time trading; foreign exchange, futures, bonds etc), is to be able to filter and sort very large tables of data. In one of our products we wanted to improve how we did this to make it more intuitive and powerful with the aim of bringing this across to all our products.<\/p>\n

\"Sorting<\/a>

How we used to do our sorting and filtering. This solution gave the user the same input for all data types; strings, numbers, dates etc. More advanced filtering like numerical and date ranges presumed the user knew the required input syntax. Property of Caplin Systems Ltd<\/p><\/div>\n

At the very start of the project, we wanted to have a thin slice (MVP) of the core functionality\u200a\u2014\u200abeing able to trade foreign exchange and have those trades appear in a table (or blotter as it is known in the industry). We knew the filtering was going to be a large piece of work (several sprints\u2019 worth), but wanted to get some basic filtering in quickly.<\/p>\n

Often in these cases, a shoddily designed solution would be added to cover the absolute bare minimum functionality. This design wouldn\u2019t take into account the additional requirements that would be added later, and would result in throw away code when the time came to build out the feature.<\/p>\n

The idea behind Incremental UX is to design iterations of a component, that can be developed one after the other. The key requirements are:<\/p>\n