I would personally start with figuring out who you want on your development team and then have them figure out which model makes the most sense.
At LiquidPlanner we've been working with (kind of) scrum for the better part of a year now and are pretty happy with it. But our team decided which model they wanted to spend time using. I'd say that it is not as important which model you use as it is that you use a single model and agree in advance how you will work. That way your team doesn't have to spend time thinking about how their work will fit into the life cycle. Instead they can spend their brain power on important things like designing and writing tight code.
Get the principles nailed down first and make sure that they're shared across your whole team. I talk a bit about shared principles in software development on my blog. I really think that you can get a long way just by sitting down with your team and spending some time to talk over how you want to work. Be sure to include things like source control, versioning, release schedules (i.e. do you want to release individual features as they're ready or batch them up into bigger releases), and of course who are your customers and what do they expect/require. If you can get agreement from the team on these things up front, then a whole lot of problems kind of solve themselves.
If you're interested in Scrum I recommend reading Agile Project Management with Scrum by Schwaber. It has a good overview. One word of caution, don't just read one or two chapters and then jump in and try to run an important project. You'll want to read it cover to cover and then get your team to read it too. That way you'll all be working from a shared understanding and vocabulary.
Good luck!