Who is the "Alpha male" on your team?

One of the great things about using SCRUM for development is the great team spirit, you are "one" or zero, a team or a disaster, part of he binary world.
But to become this team you need to support different roles, and this is where you meet the "Aplha male". Actually he is just a developer, but what drives him is his interest in always wanting to try out new opportunities, to keep your project on the top of the new technology. A typically indication of the Alpha male could be this comment in the daily SCRUM: "..Okay, have you heard about this new database service? It is so great, really fantastic. If we just implement this it will save us for a bunch of work. It's so great it can do all we need to do and also a lot more :). We can't wait to grap and integrate it into production.." .
And this is where you as part of exactly the same team need to act as a team. You need to cool down for a moment from the excitement about this new component. When the Alpha male stops talking you start to ask. But do not hide the excitement in your voice as you speak as this will be disregarding your team member, after all everybody trust each other to be the best at what they are doing.

• Wow this sounds great, but what is the state of this new component?
• Is it something we are allowed to release yet?
• How does it actually perform, have you tried it?
• How much need to be refactored to integrate it?
• So what is the ROI?
• Current state, is it alpha, beta, CTP etc.

What you decide to do is up to the team.
The key point in this is that almost every team has this Alpha male, and you need to be aware of it, as is might be crucial to the success of your project, whether you make a success or a failure, back to the basics.

And please apologize for the use of male where it could as well be female, it just sounds greater :)