No, we use a derivative of Kanban;
Scrum is not flexible enough for a small team working on mostly startup-related projects with constantly changing scopes - usually by the time we were halfway through the sprint, half the sprint had already changed, some features became obsolete meaning some devs were doing nothing, new urgent fixes and features creeped in all the time and the overhead of doing sprint-planning was just too much - burndown charts never matched what was actually happening.
With Kanban work is assigned as soon as devs become available, if they need to stop something mid-way to work on something much more urgent, we can do that, we don't have to waste time assigning points to things - if it's a small task, do it now, if it'll take longer than a day, give it a priority, place it in the queue and whoever gets to it first, they get to do it.