WYDIWYN – What you define, is what you need: Defining agile/traditional mixed methodologies
dc.contributor.author | Bustamante A.F. | |
dc.contributor.author | Rincón R.D. | |
dc.contributor.department | Universidad EAFIT. Departamento de Ingeniería de Sistemas | spa |
dc.contributor.researchgroup | I+D+I en Tecnologías de la Información y las Comunicaciones | spa |
dc.date.accessioned | 2021-04-12T21:07:07Z | |
dc.date.available | 2021-04-12T21:07:07Z | |
dc.date.issued | 2018-01-01 | |
dc.description.abstract | Defining software development methodologies may jointly include traditional and agile frameworks practices. Agile frameworks give teamwork structure and dynamics which are focused on delivering value in an incremental way. Traditional frameworks establish clarity in work products and project phases along all its lifecycle. The combination of frameworks can help to apply best practices of different models, but increasing the complexity in the methodology definition when having to start from contexts of a different nature. You will see in this article a carried out study that confirms the use of agile/traditional mixed methodologies in the industry, the difficulties that emerged and that are still seen in this approach, and the creation, setting and analysis of a guide that helps to uncomplex the definition of mixed methodologies. © Springer International Publishing AG 2018. | eng |
dc.identifier | https://eafit.fundanetsuite.com/Publicaciones/ProdCientif/PublicacionFrw.aspx?id=7850 | |
dc.identifier.doi | 10.1007/978-3-319-69341-5_4 | |
dc.identifier.issn | 21945357 | |
dc.identifier.issn | 21945365 | |
dc.identifier.other | SCOPUS;2-s2.0-85032673558 | |
dc.identifier.uri | http://hdl.handle.net/10784/28764 | |
dc.language.iso | eng | |
dc.publisher | Springer Verlag | |
dc.relation.uri | https://www.scopus.com/inward/record.uri?eid=2-s2.0-85032673558&doi=10.1007%2f978-3-319-69341-5_4&partnerID=40&md5=77bc67465b8ac5a2de506c0dade32ce4 | |
dc.rights | https://v2.sherpa.ac.uk/id/publication/issn/2194-5357 | |
dc.source | Advances In Intelligent Systems And Computing | |
dc.subject.keyword | Application | eng |
dc.subject.keyword | programs | eng |
dc.subject.keyword | Life | eng |
dc.subject.keyword | cycle | eng |
dc.subject.keyword | Process | eng |
dc.subject.keyword | engineering | eng |
dc.subject.keyword | Software | eng |
dc.subject.keyword | engineering | eng |
dc.subject.keyword | Agile | eng |
dc.subject.keyword | frameworks | eng |
dc.subject.keyword | Software | eng |
dc.subject.keyword | development | eng |
dc.subject.keyword | methodologies | eng |
dc.subject.keyword | Software | eng |
dc.subject.keyword | Process | eng |
dc.subject.keyword | Improvement | eng |
dc.subject.keyword | Traditional | eng |
dc.subject.keyword | frameworks | eng |
dc.subject.keyword | VSEs | eng |
dc.subject.keyword | Software | eng |
dc.subject.keyword | design | eng |
dc.title | WYDIWYN – What you define, is what you need: Defining agile/traditional mixed methodologies | eng |
dc.type | info:eu-repo/semantics/conferencePaper | eng |
dc.type | conferencePaper | eng |
dc.type | info:eu-repo/semantics/publishedVersion | eng |
dc.type | publishedVersion | eng |
dc.type.local | Documento de conferencia | spa |