Show Less

Making Software Teams Effective

How Agile Practices Lead to Project Success Through Teamwork Mechanisms

Chaehan So

How does good teamwork emerge?
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.

Prices

Show Summary Details
Restricted access

A Agile Practices Scales 161

Extract

Appendix A Agile Practices Scales Item Name Item Wording Corrected Item- Total Correla- tion Cronbach α if Item Deleted Scale: Iteration Planning Iteration planning meetings share the practice of having all technical team members participate in the effort estimation of the iteration scope. This is common to e.g. the Sprint planning meeting in Scrum or the Planning Game/Planning Poker in XP. How was iteration planning practiced on your project? plan1 All members of the technical team actively participated during iteration planning meetings. 0.58 0.75 plan2 All technical team members took part in defining the ef- fort estimates for requirements of the current iteration. 0.62 0.75 plan3 When effort estimates differed, the technical team members discussed their underlying assumption. 0.59 0.75 plan4 All concerns from team members about reaching the it- eration goals were considered. 0.57 0.76 plan5 The effort estimates for the iteration scope items were modified only by the technical team members. 0.41 0.78 plan6 Each developer signed up for tasks on a completely vol- untary basis. 0.55 0.76 plan7 The customer picked the priority of the requirements in the iteration plan. 0.40 0.79 161 Item Name Item Wording Corrected Item- Total Correla- tion Cronbach α if Item Deleted Scale: Iterative Development The underlying process of all agile methods consists in an iterative approach of developing software: The project/release is structured into short iterations which are time-boxed and produce working software. To what extent do the following statements describe how iterative development was practiced on your project/release? iterat1 We implemented our...

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.