Characteristics:
- Requirements can be loose and the developer will inquire to produce the correct functionality
- Likes to do "cool" development but is practical about its use
- Has a good grasp on Business need for development
- Usually good code formatting
- Usually under estimates time to complete a development task
- Good team member
- Usually has better communication skills then previous categories.
Draw backs:
- Still not fully engaged in the reason the product is being produced
- Thinks the code style and beauty is more important then the functionality it provides
How to Utilize:
- Very good on teams where the drawbacks can be compensated by others
- Usually you want a majority of these guys