Q2. What are the future works in "Development of a team measure for tacit knowledge in software development teams" ?
Finally, the technique to develop the TTKM may be used to measure team-level tacit knowledge in any domain not just software development expanding the possibilities for uncovering and comparing similarities and differences in team-level tacit knowledge.
Q3. What is the definition of tacit knowledge?
The development of a team-level definition for tacit knowledge should reflect the social cognitive process which gives rise to shared mental models using groups or teams of people as the unit of analysis, where individual scores on cognitive measures are aggregated.
Q4. What is the significance of tacit knowledge in team performance?
it appears that tacit knowledge only contributes partly to competitiveness since effectiveness refers to the achievement of project goals and not budget and schedule.
Q5. What are the implications for software development teams?
The implications for software development teams are that processes and methods that may encourage interaction, may also lead directly and indirectly to an increase in the tacit knowledge base.
Q6. How was the generalisation to others established?
Generalisation to others in the domain was established using test-retest reliabilities for repeated administration of the test across individuals.
Q7. What is the reason why the TTKM is considered acceptable at the team level?
Given that the obtained team-level reliability falls within the range for other situational judgement tests and for those reliabilities obtained on previous measures of tacit knowledge then the authors consider the internal consistency of the team-level score to be acceptable.
Q8. What are the main factors that affect the performance of a software development team?
Team performance on software development projects is dependent on many different and interacting factors like effective plans, good communication, clear goals etc.
Q9. How many experienced project managers were selected?
Thirteen experienced project managers in the software development field from seven different organisations in Ireland (N=6) and the UK (N=1) were chosen as experts.
Q10. What is the purpose of tacit knowledge?
Tacit knowledge may be shared in a number of ways, including mentoring and apprenticeships, but usually involves social interaction.
Q11. What is the significance of tacit knowledge in software development?
Knowledge sharing is therefore a key process in developing software, and since expert knowledge is tacit, the acquisition and transmission of tacit knowledge is significant in the development process.
Q12. What was the unified validity framework used to test the TTKM?
Using Messick’s (1995) unified validity framework, it was found that the TTKM was a reasonably internally valid and reliable measure of tacit knowledge at the team-level, but not at the individual level, though more studies would be needed to further test the reliability and expand the validity to other populations.
Q13. What are the implications of this research for software development teams?
team tacit knowledge and the coordination of specialised knowledge within teams are significant factors in effective performance for software development teams.
Q14. What is the process of developing a tacit knowledge inventory?
The process of developing a tacit knowledge inventory in this way begins by eliciting experienced-based tacit knowledge from successful practitioners in a particular domain and finishing with a validated and revised instrument.
Q15. How many themes were used in the supplied grid?
In order to develop a team measure for tacit knowledge regarding the factors that influence team performance on successful software projects, a ‘supplied’ or ‘standardized’ grid (Fransella et al., 2004) was developed based on the 27 themes.