A longitudinal case study on Nexus transformation: Impact on productivity, quality, and motivation
There have been success stories reported regarding the adoption of agile software development methods in the industry. There also exist observations on their limitations. One of these limitations is scalability since agile methods like Scrum were originally designed for small software teams. Scalabl...
Gespeichert in:
Veröffentlicht in: | Journal of software : evolution and process 2024-05, Vol.36 (5), p.n/a |
---|---|
Hauptverfasser: | , , , , |
Format: | Artikel |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
container_end_page | n/a |
---|---|
container_issue | 5 |
container_start_page | |
container_title | Journal of software : evolution and process |
container_volume | 36 |
creator | Ersoy, Ersin Çallı, Engin Erdoğan, Batuhan Bağrıyanık, Selami Sözer, Hasan |
description | There have been success stories reported regarding the adoption of agile software development methods in the industry. There also exist observations on their limitations. One of these limitations is scalability since agile methods like Scrum were originally designed for small software teams. Scalable agile frameworks were introduced to address this limitation. We conducted an industrial case study on the adoption of such a framework, called Nexus. Our study involves quantitative and qualitative evaluation based on observations within a product development organization over a period of 12 months. Scrum is used for the development of a product during the first 6 months of this period. Nexus is used in the remaining 6 months. Data are collected throughout the whole period for measuring productivity, quality, and team member motivation. Results suggest a significant increase in productivity and product quality after switching to Nexus. Team motivation was slightly improved as well.
An industrial case study is conducted for 12 months, where Scrum is used during the first 6 months and Nexus is used in the remaining 6 months. A significant increase in productivity and product quality is observed after Nexus transformation, while slight improvement is observed in team motivation as well. |
doi_str_mv | 10.1002/smr.2615 |
format | Article |
fullrecord | <record><control><sourceid>proquest_cross</sourceid><recordid>TN_cdi_proquest_journals_3045909531</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>3045909531</sourcerecordid><originalsourceid>FETCH-LOGICAL-c2885-f7d2123c63ec39afff4bbdb3f6c30f67d70319a8387f4df76076aaa513af84793</originalsourceid><addsrcrecordid>eNp1kMlOwzAQhi0EElWpxCNY4sKBFDtO4oRbVbFUKiCxnK2JEyNXSdzaDpC3x2kRN-Yy2zejmR-hc0rmlJD42rV2Hmc0PUKTmCQ84klOj_9izk7RzLkNCZbFJE3SCSoXuDHdh_Z9pTtosARXYxeyAZsOP9XfvcPeQueUsS14bbobvGq3IP3Y31pT9dLrT-2HK7zrodkH0FW4NaG8HzhDJwoaV89-_RS9392-LR-i9fP9arlYRzLO8zRSvIppzGTGaskKUEolZVmVTGWSEZXxihNGC8hZzlVSKZ4RngFAShmoPOEFm6KLw95w1a6vnRcb09vwlBOMJGlBipTRQF0eKGmNc7ZWYmt1C3YQlIhRRBFEFKOIAY0O6Jdu6uFfTrw-vuz5H7xVc_I</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>3045909531</pqid></control><display><type>article</type><title>A longitudinal case study on Nexus transformation: Impact on productivity, quality, and motivation</title><source>Wiley Journals</source><creator>Ersoy, Ersin ; Çallı, Engin ; Erdoğan, Batuhan ; Bağrıyanık, Selami ; Sözer, Hasan</creator><creatorcontrib>Ersoy, Ersin ; Çallı, Engin ; Erdoğan, Batuhan ; Bağrıyanık, Selami ; Sözer, Hasan</creatorcontrib><description>There have been success stories reported regarding the adoption of agile software development methods in the industry. There also exist observations on their limitations. One of these limitations is scalability since agile methods like Scrum were originally designed for small software teams. Scalable agile frameworks were introduced to address this limitation. We conducted an industrial case study on the adoption of such a framework, called Nexus. Our study involves quantitative and qualitative evaluation based on observations within a product development organization over a period of 12 months. Scrum is used for the development of a product during the first 6 months of this period. Nexus is used in the remaining 6 months. Data are collected throughout the whole period for measuring productivity, quality, and team member motivation. Results suggest a significant increase in productivity and product quality after switching to Nexus. Team motivation was slightly improved as well.
An industrial case study is conducted for 12 months, where Scrum is used during the first 6 months and Nexus is used in the remaining 6 months. A significant increase in productivity and product quality is observed after Nexus transformation, while slight improvement is observed in team motivation as well.</description><identifier>ISSN: 2047-7473</identifier><identifier>EISSN: 2047-7481</identifier><identifier>DOI: 10.1002/smr.2615</identifier><language>eng</language><publisher>Chichester: Wiley Subscription Services, Inc</publisher><subject>agile software development ; industrial case study ; Nexus ; Product development ; Productivity ; scaled agile transformation ; Software development ; software development process</subject><ispartof>Journal of software : evolution and process, 2024-05, Vol.36 (5), p.n/a</ispartof><rights>2023 John Wiley & Sons Ltd.</rights><rights>2024 John Wiley & Sons, Ltd.</rights><lds50>peer_reviewed</lds50><oa>free_for_read</oa><woscitedreferencessubscribed>false</woscitedreferencessubscribed><cites>FETCH-LOGICAL-c2885-f7d2123c63ec39afff4bbdb3f6c30f67d70319a8387f4df76076aaa513af84793</cites><orcidid>0000-0002-5561-4283 ; 0000-0002-6100-9514 ; 0000-0002-2968-4763</orcidid></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktopdf>$$Uhttps://onlinelibrary.wiley.com/doi/pdf/10.1002%2Fsmr.2615$$EPDF$$P50$$Gwiley$$H</linktopdf><linktohtml>$$Uhttps://onlinelibrary.wiley.com/doi/full/10.1002%2Fsmr.2615$$EHTML$$P50$$Gwiley$$H</linktohtml><link.rule.ids>314,780,784,1417,27924,27925,45574,45575</link.rule.ids></links><search><creatorcontrib>Ersoy, Ersin</creatorcontrib><creatorcontrib>Çallı, Engin</creatorcontrib><creatorcontrib>Erdoğan, Batuhan</creatorcontrib><creatorcontrib>Bağrıyanık, Selami</creatorcontrib><creatorcontrib>Sözer, Hasan</creatorcontrib><title>A longitudinal case study on Nexus transformation: Impact on productivity, quality, and motivation</title><title>Journal of software : evolution and process</title><description>There have been success stories reported regarding the adoption of agile software development methods in the industry. There also exist observations on their limitations. One of these limitations is scalability since agile methods like Scrum were originally designed for small software teams. Scalable agile frameworks were introduced to address this limitation. We conducted an industrial case study on the adoption of such a framework, called Nexus. Our study involves quantitative and qualitative evaluation based on observations within a product development organization over a period of 12 months. Scrum is used for the development of a product during the first 6 months of this period. Nexus is used in the remaining 6 months. Data are collected throughout the whole period for measuring productivity, quality, and team member motivation. Results suggest a significant increase in productivity and product quality after switching to Nexus. Team motivation was slightly improved as well.
An industrial case study is conducted for 12 months, where Scrum is used during the first 6 months and Nexus is used in the remaining 6 months. A significant increase in productivity and product quality is observed after Nexus transformation, while slight improvement is observed in team motivation as well.</description><subject>agile software development</subject><subject>industrial case study</subject><subject>Nexus</subject><subject>Product development</subject><subject>Productivity</subject><subject>scaled agile transformation</subject><subject>Software development</subject><subject>software development process</subject><issn>2047-7473</issn><issn>2047-7481</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2024</creationdate><recordtype>article</recordtype><recordid>eNp1kMlOwzAQhi0EElWpxCNY4sKBFDtO4oRbVbFUKiCxnK2JEyNXSdzaDpC3x2kRN-Yy2zejmR-hc0rmlJD42rV2Hmc0PUKTmCQ84klOj_9izk7RzLkNCZbFJE3SCSoXuDHdh_Z9pTtosARXYxeyAZsOP9XfvcPeQueUsS14bbobvGq3IP3Y31pT9dLrT-2HK7zrodkH0FW4NaG8HzhDJwoaV89-_RS9392-LR-i9fP9arlYRzLO8zRSvIppzGTGaskKUEolZVmVTGWSEZXxihNGC8hZzlVSKZ4RngFAShmoPOEFm6KLw95w1a6vnRcb09vwlBOMJGlBipTRQF0eKGmNc7ZWYmt1C3YQlIhRRBFEFKOIAY0O6Jdu6uFfTrw-vuz5H7xVc_I</recordid><startdate>202405</startdate><enddate>202405</enddate><creator>Ersoy, Ersin</creator><creator>Çallı, Engin</creator><creator>Erdoğan, Batuhan</creator><creator>Bağrıyanık, Selami</creator><creator>Sözer, Hasan</creator><general>Wiley Subscription Services, Inc</general><scope>AAYXX</scope><scope>CITATION</scope><scope>7SC</scope><scope>8FD</scope><scope>JQ2</scope><scope>L7M</scope><scope>L~C</scope><scope>L~D</scope><orcidid>https://orcid.org/0000-0002-5561-4283</orcidid><orcidid>https://orcid.org/0000-0002-6100-9514</orcidid><orcidid>https://orcid.org/0000-0002-2968-4763</orcidid></search><sort><creationdate>202405</creationdate><title>A longitudinal case study on Nexus transformation: Impact on productivity, quality, and motivation</title><author>Ersoy, Ersin ; Çallı, Engin ; Erdoğan, Batuhan ; Bağrıyanık, Selami ; Sözer, Hasan</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c2885-f7d2123c63ec39afff4bbdb3f6c30f67d70319a8387f4df76076aaa513af84793</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2024</creationdate><topic>agile software development</topic><topic>industrial case study</topic><topic>Nexus</topic><topic>Product development</topic><topic>Productivity</topic><topic>scaled agile transformation</topic><topic>Software development</topic><topic>software development process</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>Ersoy, Ersin</creatorcontrib><creatorcontrib>Çallı, Engin</creatorcontrib><creatorcontrib>Erdoğan, Batuhan</creatorcontrib><creatorcontrib>Bağrıyanık, Selami</creatorcontrib><creatorcontrib>Sözer, Hasan</creatorcontrib><collection>CrossRef</collection><collection>Computer and Information Systems Abstracts</collection><collection>Technology Research Database</collection><collection>ProQuest Computer Science Collection</collection><collection>Advanced Technologies Database with Aerospace</collection><collection>Computer and Information Systems Abstracts Academic</collection><collection>Computer and Information Systems Abstracts Professional</collection><jtitle>Journal of software : evolution and process</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Ersoy, Ersin</au><au>Çallı, Engin</au><au>Erdoğan, Batuhan</au><au>Bağrıyanık, Selami</au><au>Sözer, Hasan</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>A longitudinal case study on Nexus transformation: Impact on productivity, quality, and motivation</atitle><jtitle>Journal of software : evolution and process</jtitle><date>2024-05</date><risdate>2024</risdate><volume>36</volume><issue>5</issue><epage>n/a</epage><issn>2047-7473</issn><eissn>2047-7481</eissn><abstract>There have been success stories reported regarding the adoption of agile software development methods in the industry. There also exist observations on their limitations. One of these limitations is scalability since agile methods like Scrum were originally designed for small software teams. Scalable agile frameworks were introduced to address this limitation. We conducted an industrial case study on the adoption of such a framework, called Nexus. Our study involves quantitative and qualitative evaluation based on observations within a product development organization over a period of 12 months. Scrum is used for the development of a product during the first 6 months of this period. Nexus is used in the remaining 6 months. Data are collected throughout the whole period for measuring productivity, quality, and team member motivation. Results suggest a significant increase in productivity and product quality after switching to Nexus. Team motivation was slightly improved as well.
An industrial case study is conducted for 12 months, where Scrum is used during the first 6 months and Nexus is used in the remaining 6 months. A significant increase in productivity and product quality is observed after Nexus transformation, while slight improvement is observed in team motivation as well.</abstract><cop>Chichester</cop><pub>Wiley Subscription Services, Inc</pub><doi>10.1002/smr.2615</doi><tpages>18</tpages><orcidid>https://orcid.org/0000-0002-5561-4283</orcidid><orcidid>https://orcid.org/0000-0002-6100-9514</orcidid><orcidid>https://orcid.org/0000-0002-2968-4763</orcidid><oa>free_for_read</oa></addata></record> |
fulltext | fulltext |
identifier | ISSN: 2047-7473 |
ispartof | Journal of software : evolution and process, 2024-05, Vol.36 (5), p.n/a |
issn | 2047-7473 2047-7481 |
language | eng |
recordid | cdi_proquest_journals_3045909531 |
source | Wiley Journals |
subjects | agile software development industrial case study Nexus Product development Productivity scaled agile transformation Software development software development process |
title | A longitudinal case study on Nexus transformation: Impact on productivity, quality, and motivation |
url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2024-12-24T06%3A29%3A57IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest_cross&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=A%20longitudinal%20case%20study%20on%20Nexus%20transformation:%20Impact%20on%20productivity,%20quality,%20and%20motivation&rft.jtitle=Journal%20of%20software%20:%20evolution%20and%20process&rft.au=Ersoy,%20Ersin&rft.date=2024-05&rft.volume=36&rft.issue=5&rft.epage=n/a&rft.issn=2047-7473&rft.eissn=2047-7481&rft_id=info:doi/10.1002/smr.2615&rft_dat=%3Cproquest_cross%3E3045909531%3C/proquest_cross%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=3045909531&rft_id=info:pmid/&rfr_iscdi=true |