How Agile Practices Lead to Project Success Through Teamwork Mechanisms
Can we control mechanisms of teamwork?
The author has analyzed these questions in a study involving 227 participants of 55 software development teams. First, he empirically confirmed his teamwork model based on innovation research, goal setting and control theory. Second, he measured the impact of a wide selection of agile practices on these teamwork mechanisms. Third, he explained these impacts based on a thorough review of current psychological research.
This book is intended for people working in agile contexts as they will gain insight into the complexity of how «good teamwork» emerges. This insight on team dynamics may also prove valuable for upper management for calibrating agile practices and «soft factors», thus increasing the effectiveness of software teams.
D Project Management Scales 171
Appendix D Project Management Scales Item Name Unit Item Description Mean SD Company Demographics Company Size persons How many employees does your company employ? 21686 42523 IT Dept. Size persons How many employees does your IT department employ? 3998 16540 Markets served nominal Consumer Market, Industrial Mar- ket, Government, Other n/a n/a Socio-Demographic Questions Total Team Size persons Please state the total number of team members. 10.08 7.02 Technical Team Size persons Please state the total number of tech- nical team members. 7.19 4.73 Team Affili- ation months How many months has the same team of developers worked together primarily in the same constellation (i.e. less than 20% fluctuation) before this project? 6.77 9.54 Scale: Project Demographics Project Effort person days Please state the total effort worked on this project in number of person days. 1264 1946 Project Du- ration calender weeks Please state the total length of this project in number of elapsed weeks. 79.19 194.13 171 Item Name Unit Item Description Mean SD Nature of Project nominal Product Enhancement, New Product, Maintenance, Migration, Other n/a n/a Type of Product nominal Network Product, Standalone Prod- uct, Hybrid, Embedded Software n/a n/a Product Age months State the age of the product in months. 30.64 48.07 Customer Type nominal internal-same vs. other dept., external-new vs. existing customer n/a n/a Sw. Dev. Method nominal Extreme Programming (XP), SCRUM, Crystal, Feature Driven Development (FDD), Dynamic Sys- tem Development Method (DSDM), Adaptive Software Development (ASD), Custom iterative approach, Waterfall with XP practices n/a n/a...
You are not authenticated to view the full text of this chapter or article.
This site requires a subscription or purchase to access the full text of books or journals.
Do you have any questions? Contact us.Or login to access all content.