OSF
open access
Team design, best practice, and bad management: Lessons from software development
This article presents a comparative case study examining variation in team design and performance across 13 teams within agile software development. We develop a novel typology of team forms, distinguishing between process autonomy, task autonomy, and authority to contribute to planning and process
Conceptio Open Archive
Analyze & explore related research in Conceptio
Connect this record directly into your research workflow or AI agent. Explore citations across open repositories, query full text, and export structured proof bundles.
This document is indexed with metadata only: full text is not available in the archive for this record. Open the official source ↗
Related documents
- Team design, best practice, and bad management: Lessons from software development#1442000
- Metrics for the evaluation of documentation format in agile software projects#1089276
- Agile Worth-Oriented Systems Engineering. A Methodology for Incorporating Ethical Aspects in Development Processes#657571
- Design, When Everybody Designs#466138
- Chapter Design for transformation. Unlock competencies for coping complexity#486754
Record · ID 1441880
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Bring this data into your agent: Connect via MCP or API · 20 free credits to start · no card required
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive