English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

Software is not developed in a vacuum. Development teams and organizations must react to various incidents, such as changes in personnel, development practices, project objectives, and business environment, and all kinds of delays occurring during large-scale software development projects. These incidents challenge contemporary communication, collaboration and development practices. They also require an ability to adapt to the new situation. We argue that the problems in reacting to those incidents and the inability in implementing corrective actions are the main reasons for software project failures. We identify four drivers of collaboration. They are named as contract, individual person, group of collaborators, and development process, each being appropriate in different points of time. Yet their emphasis and appropriateness vary over time. This emphasizes the developers’ ability to transit between the drivers of collaboration.

proceedings of the ... annual hawaii international conference on system sciences/proceedings of the annual hawaii international conference on system sciences

Collaboration Drivers andBreakdowns in Large Scale Software Customization