Mostrar el registro sencillo del ítem

dc.contributor.authorCrawford B.
dc.contributor.authorSoto R.
dc.contributor.authorde la Barra C.L.
dc.contributor.authorCrawford K.
dc.contributor.authorOlguín E.
dc.date.accessioned2020-09-02T22:16:03Z
dc.date.available2020-09-02T22:16:03Z
dc.date.issued2014
dc.identifier10.1007/978-3-319-07857-1_5
dc.identifier.citation434 PART I, , 24-29
dc.identifier.issn18650929
dc.identifier.urihttps://hdl.handle.net/20.500.12728/4173
dc.descriptionAgile Software processes emphasize collaboration more than traditional methods. Collaborations and interactions are cited directly in two of the four values listed in the agile manifesto. Because of everything that involves communication contains the potential for conflict, we are interested in knowing how to manage conflicts to enhance agile projects. © Springer International Publishing Switzerland 2014.
dc.language.isoen
dc.publisherSpringer Verlag
dc.subjectAgile Development
dc.subjectConflict Management
dc.subjectSoftware Engineering
dc.subjectComputer science
dc.subjectComputers
dc.subjectAgile development
dc.subjectAgile software process
dc.subjectAgile softwares
dc.subjectConflict management
dc.subjectUse conflicts
dc.subjectSoftware engineering
dc.titleAgile Software Teams Can Use Conflict to Create a Better Products
dc.typeConference Paper


Ficheros en el ítem

Thumbnail

Este ítem aparece en la(s) siguiente(s) colección(ones)

Mostrar el registro sencillo del ítem