MSF Agile is one of the software development processes that ships with Visual Studio Team System. It incorporates an agile software development process into some of Microsoft's proven practices for building software.
Randy Miller has a good post about using the MSF Agile Process: Agile Software Development for Projects Large and Small. He talks about how even large projects are usually broken up into teams of teams, and how this process can be used for very small projects are extremely large ones.
I've been a little hesitant about diving into this process, because there are several different roles, and I wasn't sure how to divide some things up, especially with some projects that I work on, the only person being the team is me. Then I read this, and something kinda clicked:
MSF for Agile Software Development contains six roles, the business analyst, project manager, architect, developer, tester, and release manager. To play any of these roles, you must simply possess the necessary skills. Your job title may be different. You may also play multiple roles. In other words, the MSF Team Model allows a lot of flexibility in the way that you organize your team.
Basically, you can cover multiple roles if you want/need to. Or, on a more fundamental level, make the process work for you, not you for the process. I realize this is probably REALLY evident to a majority of people out there, but for myself, who sometimes has tunnel vision, it was, for lack of a better term, a light bulb going off.
The MSF Agile process may still be a bit overkill for a really small team (aka 1 person), but I'm interested enough now to delve into it some, to see how I can modify it to make it work for me, instead of me working for it.