FlowingFlowing
← Back to all development cases
This case was judged by an anonymized AI reviewer and has not been independently reviewed by people; inspect the draft, cards, and both outputs to assess it.
AutocompleteWith cards better61 / 280 · beu-5d41b0828963c024

Understanding Work Practices of Autonomous Agile Teams: A Social-psychological Review

Psychology and cognitive neuroscience · 2011.03328v1

FLOWING EVIDENCE BENCHMARK

How do we compare writing with and without cards?

At the same writing position, the same model produces one first result with cards and one without. All 280 pairs enter the overall anonymized review, which assesses whether a decision not to continue fits the draft.

Overall: 138 with-card wins, 26 ties, 107 no-card wins, 5 pairs where neither was usable, and 4 inconclusive judgments. Both sides wrote text in 218 pairs; 48 had a deliberate stop and 14 included an invalid output.

SAME DRAFT · WITH OR WITHOUT CARDS

01 · FIXED WRITING POSITION

MANUSCRIPT

Same writing position ▌

Matched autocomplete at the same draft position

02 · TWO MATCHED VERSIONS

SHARED BY BOTH

Draft, writing task, and generation model

A · With cards

Relevant literature cards supplied

B · Without cards

No literature cards supplied

Generation model

Same model and version

A → first output

B → first output

Anonymized AI judge

First outputs are anonymized as X and Y

Continuation review: accuracy, fit to the writing task and usability
Returns: X preferred / tie / Y preferred / both unusable

Review again with the answer order swapped

HOW DOES BLIND JUDGING WORK?

① Anonymize both outputs
The AI judge sees the same draft and both first outputs without knowing which received cards.

② Compare and swap order
The judge applies task-specific criteria in X/Y and then Y/X order.

③ Review disagreements
A third pass resolves disagreements. Incomplete reviews remain in the denominator.

How are positions and cards selected?

We selected 40 writing positions in each of seven fields, for 280 comparisons. The position and relevant literature cards were set before each comparison, so both versions began from the same draft.

The main result retains every frozen position, including places where cards might not add a useful next move. This avoids selecting cases based on their outputs, but 49% describes the whole cohort, not a win rate where evidence clearly had an opportunity to help. This cohort did not record that opportunity label for each position before generation, so those two groups cannot yet be separated reliably.

CARD USE · 140/280

Reported card use in continuations with text

The model reports whether a card affected its continuation. In 140 of 280 tests it produced continuation text and reported card use. The previous count of 150 included 10 cases without continuation text and has been corrected.

COMPARISON · 70 / 7 / 30

Which written version was better?

Of the 107 reported-use cases where both versions produced text, the blinded AI judge preferred the with-card version 70 times, found 7 about the same, and preferred the without-card version 30 times.

How are the two table percentages calculated?

ADOPTION COVERAGE

140reported use with text
÷
280all positions
=
50%

WITH-CARD VERSION PREFERRED

70with cards better
÷
107comparable tests
=
65%

The percentages use different groups: 50% counts continuations with text reporting card use among all 280 tests; 65% covers the 107 such cases with text on both sides. The generating model reports card use, while an anonymized AI judge compares writing quality.

Card use is self-reported by the generator. The anonymized AI judge sees the draft and source snippets, so source-aware preference remains possible; there was no independent human review. The overall result describes these 280 frozen positions, not a win probability for any writing task.

Manuscript writing position

Text excerpt · not a PDF page

Research manuscript · excerpt

Understanding Work Practices of Autonomous Agile Teams: A Social-psychological Review

4 Discussion and Implications

…proposition is that harmonious relations between different subgroups of the organization is best kept by recognizing both the subgroups (e.g. Quality Assurance Engineer, Software Developers, Software Tester, etc.) and other organizational constellations, including the teams and the company as a whole. This means that the cross-functional agile teams must recognize both the value of the team as a whole but also the different roles and make distinctions between them. All these aspects should be part of agile team measurements in the future in order to fully make sense of the agile team context.

…ooking at the descriptions of the agile practices overall, many of the internal practices seem to assume full group-membership seen from a group socialization perspective [ 9 ] . They also assume the entire work-group to be mature from a developmental perspective [ 10 ] . In order to fully understand the social-psychological components of the team-based workplace in general, and the agile context in particular, we also need to investigate the temporal perspective of the interplay between group development, group socialization, and the agile approach to projects by setting up autonomous teams.

↓ Next paragraph was generated here

The highlighted text is near the writing position. This is a layout of the evaluation input, not a PDF screenshot.

A matched comparison at the same writing positionOverall AI review: With cards better

Both arms use the same model, task and manuscript context. Only the retrieved passages differ. The first recorded output from each arm is shown below.

Read overall AI review rationale

A = without cards · B = with cards

The draft ends with a call to investigate 'the temporal perspective of the interplay between group development, group socialization, and the agile approach to projects by setting up autonomous teams.' This is an active research agenda statement that invites continuation—it does not read as a natural conclusion. Output A's 'complete' abstention is therefore premature; the paragraph has set up an empirical/theoretical program that needs at least a brief forward-looking or synthesizing move to land the argument. Output B provides exactly this: it transitions from the theoretical call to concrete empirical findings (group maturity correlating with iterative development and retrospectives, teams adopting agility differently at different stages), which directly supports the draft's argument and connects back to the sources. The claim about correlation with iterative development and retrospectives is supported by the 'Agile ways of working' source, and the claim about differential adoption by developmental stage is also source-supported. Output B fits the argument's scope, maintains academic register, and closes the logical loop opened by the draft's call for temporal investigation. Output A's abstention, while not 'invalid,' is less usable because leaving the paragraph at 'we also need to investigate...' feels incomplete and leaves the reader without the payoff the argument has been building toward.

Evidence

Same model and position · retrieved passages supplied · first output

Preferred by blind review

This temporal interplay is not merely a theoretical concern: empirical studies have found that group maturity correlates with agile practices such as iterative development and retrospectives, and that teams at different developmental stages adopt aspects of team agility differently. These findings suggest that the relationship between group development and agile work practices is contingent on where a team currently stands in its developmental trajectory, which has direct implications for how autonomous teams should be measured and supported.

Passages supplied to the Evidence version

Card 1 · Group development and group maturity when building agile teams

Overlap between what is meant by an and a mature group in psychology.Group developmental issues are dealt with in practice in groups.Quantitative survey data support the connections.Focusing on group development is a key success factor when building teams. The approach to projects focuses more on cl…

Read full passage excerpt

Overlap between what is meant by an and a mature group in psychology.Group developmental issues are dealt with in practice in groups.Quantitative survey data support the connections.Focusing on group development is a key success factor when building teams. The approach to projects focuses more on close-knit teams than traditional waterfall projects, which means that aspects of group maturity become even more important. This psychological aspect is not much researched in connection to the building of an agile team. The purpose of this study is to investigate how building teams is connected to a group development model taken from social psychology. We conducted ten semi-structured interviews with coaches, Scrum Masters, and managers responsible for the process from seven different companies, and collected survey data from 66 group-members from four companies (a total of eight different companies). The survey included an measurement tool and the one part of the Group Development Questionn …

Card 2 · Agile ways of working: A team maturity perspective

Abstract With the agile approach to managing software development projects comes an increased dependability on well‐functioning teams, since many of the practices are built on teamwork. The objective of this study was to investigate if, and how, team development from a group psychological perspectiv…

Read full passage excerpt

Abstract With the agile approach to managing software development projects comes an increased dependability on well‐functioning teams, since many of the practices are built on teamwork. The objective of this study was to investigate if, and how, team development from a group psychological perspective is related to some work practices of agile teams. Data were collected from 34 agile teams (200 individuals) from six software development organizations and one university in both Brazil and Sweden using the Group Development Questionnaire (Scale IV) and the Perceptive Agile Measurement (PAM). The result indicates a strong correlation between levels of group maturity and the two agile practices iterative development and retrospectives. We, therefore, conclude that agile teams at different group development stages adopt parts of team agility differently, thus confirming previous studies but with more data and by investigating concrete and applied agile practices. We thereby add evidence to t …

Card 3 · Group Maturity and Agility, Are They Connected? - A Survey Study

The fact is that a mature group performs much better; e.g., they finish projects faster [ 20 ] . Students perform better on standardized test if the faculty team is at a mature development stage [ 21 , 22 ] , and intensive care staff functioning in a mature team save more lives [ 23 ] . Paying atten…

Read full passage excerpt

The fact is that a mature group performs much better; e.g., they finish projects faster [ 20 ] . Students perform better on standardized test if the faculty team is at a mature development stage [ 21 , 22 ] , and intensive care staff functioning in a mature team save more lives [ 23 ] . Paying attention to group development could help the group to succeed. The agile methods assume that groups are mature since they describe agile collaboration in the same way as a characteristic mature group. The agile methods cannot skip the aspect of group development, since all groups will have to deal with its effect, i.e., much more of what happens in agile teams would be understood better if group development was taken into account. However, in order to justify such a merge, it must be shown that agility and group development have connections.

Card 4 · Group-Development Psychology Training: The Perceived Effects on Agile Software-Development Teams

Research has shown that the maturity of small workgroups from a psychological perspective is intimately connected to team agility. We, therefore, tested if agile team members appreciated group development psychology training. Our results show that the participating teams seem to have a very positive…

Read full passage excerpt

Research has shown that the maturity of small workgroups from a psychological perspective is intimately connected to team agility. We, therefore, tested if agile team members appreciated group development psychology training. Our results show that the participating teams seem to have a very positive view of group development training and state that they now have a new way of thinking about teamwork and new tools to deal with team-related problems. We, therefore, see huge potential in training agile teams in group development psychology since the positive effects might span over the entire software development organization.

Card 5 · Trying to Increase the Mature Use of Agile Practices by Group Development Psychology Training - An Experiment

There has been some evidence that agility is connected to the group maturity of software development teams. This study aims at conducting group development psychology training with student teams, participating in a project course at university, and compare their group effectiveness score to their ag…

Read full passage excerpt

There has been some evidence that agility is connected to the group maturity of software development teams. This study aims at conducting group development psychology training with student teams, participating in a project course at university, and compare their group effectiveness score to their agility usage over time in a longitudinal design. Seven XP student teams were measured twice (43+40), which means 83 data points divided into two groups (an experimental group and one control group). The results showed that the agility measurement was not possible to increase by giving a 1.5-hour of group psychology lecture and discussion over a two-month period. The non-significant result was probably due to the fact that 1.5 hours of training were not enough to change the work methods of these student teams, or, a causal relationship does not exist between the two concepts. A third option could be that the experiential setting of real teams, even at a university, has many more variables not …

Model-reported card use

Card 2 · fact

Affected output: empirical studies have found that group maturity correlates with agile practices such as iterative development and retrospectives, and that teams at different developmental stages adopt aspects of team agility differently

Model explanation: This row supplied the concrete empirical finding that group maturity correlates with iterative development and retrospectives, which the Draft alone did not contain.

Card 1 · direction

Affected output: which has direct implications for how autonomous teams should be measured and supported

Model explanation: This row's call for maturity-differentiated guidelines shaped the direction of the closing implication toward measurement and support rather than a generic future-work statement.

Card 3 · scope

Affected output: This temporal interplay is not merely a theoretical concern

Model explanation: This row's framing that the agility–group development connection requires empirical justification guided the decision to ground the temporal argument in reported correlations rather than leaving it as a theoretical claim.

No Evidence

Same model and position · no retrieved passages · first output

Not preferred in this comparison

No continuation text was produced.

Model action：complete

Earlier card-use comparison

The earlier diagnostic compared only cases with reported card use and text on both sides; its scope differs from the overall AI review above.

The with-card arm produced text and reported card use, but the no-card arm produced no text. This counts as reported use, without entering the two-text preference comparison.

The passages are input material; their presence does not mean an output used them or that they support every claim. Draft and source passages are excerpted; no simulated scores or PDF appear here.