New… for us, who are only starting to apply it now. Agile working is much older (we first came across it a decade ago).
\nAgile working means tackling a project by turning it into small mini-projects on which to focus efforts during short blocks of time. Those small blocks are quoted independently.
\nI'll tell you how we are applying it ourselves (it may not be the most orthodox way, but it is giving us very good results).
\nWe work in ten-hour blocks. Together with the client, we decide at each point what is next that interests them. And we dedicate that group of hours to those tasks.
\nWhat advantages does this bring us?
\n– we gain agility: the client can quickly change the goal of the project. It could be that a month ago they were interested in improving the stock system, but that now they are interested in customers receiving a weekly email with the shop's latest news.
\n– we adapt to the client's financial needs: if at a given moment the client decides to stop development, it is paused until further notice.
\n– it is a fairer system for both parties, since if any of the tasks is especially complicated, the client can choose not to go down that path, or to continue down that path, being aware of the number of hours needed.
\n– it makes the task of quoting much easier. Developers don't like preparing quotes very much; among other things because they usually don't match reality. And because unforeseen events always arise which, as the name suggests, are unknown in advance.
\nDespite all this, there was something that worried us, and that seemed to us an insurmountable obstacle: with this system, the client does not have a fixed quote, they really don't know how much the whole project is going to cost them. After having worked with this system, we can tell you that it is not a problem at all (except for our minds, used to past methods) because, indeed, the client does not have a fixed price… but the thing is that there is no real project that can ever be considered closed. On the other hand, as we have already said, with agile working the client can stop the project whenever they see fit; so no, there's no problem there either.
\nWhat do you think? Do you feel like getting started with this system?