Yes, great idea. I floated the idea of sprints for web work a couple of weeks ago, and volunteered to be the sprint manager for web stuff. IMO useful bits from agile sprints are:
- Have a sprint manager
- Keep a list ('backlog') of all the stuff you ever want to do, somewhere people can add to it any time
- Nothing can go in a sprint until it's achievable (e.g. < 4 hours) and well defined (but everything goes in the backlog)
- Sprint manager responsible for
-- Keeping the backlog doc tidy and breaking down big tasks
-- Prioritising with all stakeholders for that project (may be different people from people who work on it!)
-- Grouping some tasks into one sprint (according to some sensible grouping)
-- Get commitment from people who will work on that sprint, for specific tasks.
-- Help a sprint through to completion
-- Keeping the people in the sprint on track, and keeping other pieces of work in that area out of their way so that they can focus only on the things in the sprint.
-- Tracking progress. There's no point doing any of this stuff if all work happens at the end of the sprint.
Once a sprint is running, don't work on anything else (in that project) so everyone can focus on just what is in the sprint.
Start small, over achieve, don't use any bollocks from agile (stand ups, burndown charts, 'points' systems) unless you can see a good reason to.