Agile Processes in Software Engineering and Extreme Programming : (Record no. 307700)
[ view plain ]
000 -LEADER | |
---|---|
fixed length control field | 09395nam a22004813i 4500 |
001 - CONTROL NUMBER | |
control field | EBC6640049 |
005 - DATE AND TIME OF LATEST TRANSACTION | |
control field | 20240122001401.0 |
006 - FIXED-LENGTH DATA ELEMENTS--ADDITIONAL MATERIAL CHARACTERISTICS | |
fixed length control field | m o d | |
007 - PHYSICAL DESCRIPTION FIXED FIELD--GENERAL INFORMATION | |
fixed length control field | cr cnu|||||||| |
008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION | |
fixed length control field | 231124s2021 xx o ||||0 eng d |
020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
International Standard Book Number | 9783030780982 |
Qualifying information | (electronic bk.) |
020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
Canceled/invalid ISBN | 9783030780975 |
035 ## - SYSTEM CONTROL NUMBER | |
System control number | (MiAaPQ)EBC6640049 |
035 ## - SYSTEM CONTROL NUMBER | |
System control number | (Au-PeEL)EBL6640049 |
035 ## - SYSTEM CONTROL NUMBER | |
System control number | (OCoLC)1257030839 |
040 ## - CATALOGING SOURCE | |
Original cataloging agency | MiAaPQ |
Language of cataloging | eng |
Description conventions | rda |
-- | pn |
Transcribing agency | MiAaPQ |
Modifying agency | MiAaPQ |
050 #4 - LIBRARY OF CONGRESS CALL NUMBER | |
Classification number | QA76.758 |
100 1# - MAIN ENTRY--PERSONAL NAME | |
Personal name | Gregory, Peggy. |
245 10 - TITLE STATEMENT | |
Title | Agile Processes in Software Engineering and Extreme Programming : |
Remainder of title | 22nd International Conference on Agile Software Development, XP 2021, Virtual Event, June 14-18, 2021, Proceedings. |
250 ## - EDITION STATEMENT | |
Edition statement | 1st ed. |
264 #1 - PRODUCTION, PUBLICATION, DISTRIBUTION, MANUFACTURE, AND COPYRIGHT NOTICE | |
Place of production, publication, distribution, manufacture | Cham : |
Name of producer, publisher, distributor, manufacturer | Springer International Publishing AG, |
Date of production, publication, distribution, manufacture, or copyright notice | 2021. |
264 #4 - PRODUCTION, PUBLICATION, DISTRIBUTION, MANUFACTURE, AND COPYRIGHT NOTICE | |
Date of production, publication, distribution, manufacture, or copyright notice | �2021. |
300 ## - PHYSICAL DESCRIPTION | |
Extent | 1 online resource (215 pages) |
336 ## - CONTENT TYPE | |
Content type term | text |
Content type code | txt |
Source | rdacontent |
337 ## - MEDIA TYPE | |
Media type term | computer |
Media type code | c |
Source | rdamedia |
338 ## - CARRIER TYPE | |
Carrier type term | online resource |
Carrier type code | cr |
Source | rdacarrier |
490 1# - SERIES STATEMENT | |
Series statement | Lecture Notes in Business Information Processing Series ; |
Volume/sequential designation | v.419 |
505 0# - FORMATTED CONTENTS NOTE | |
Formatted contents note | Intro -- Preface -- Organization -- Contents -- Agile Practices -- From Collaboration to Solitude and Back: Remote Pair Programming During COVID-19 -- 1 Introduction -- 2 Background and Related Work -- 2.1 Pair Programming -- 2.2 Remote Pair Programming -- 3 Empirical Cases and Research Method -- 3.1 The Case Study Design -- 3.2 InterSoft and SavingsBank and Their Transition to WFH -- 3.3 Data Collection -- 3.4 Data Analysis -- 3.5 Limitations and Threats to Validity -- 4 Findings -- 4.1 Do Engineers Pair Program When Working from Home? -- 4.2 How is Remote Pair Programming Done? -- 4.3 What Are the Main Challenges in Remote Pair Programming in WFH? -- 4.4 What Are the Benefits of Remote Pair Programming in WFH? -- 5 Discussion and Concluding Remarks -- References -- UX Work in Software Start-Ups: Challenges from the Current State of Practice -- 1 Introduction -- 2 Related Work -- 3 Research Method -- 4 Results -- 4.1 UX in the Software Development Activities -- 4.2 UX Work from the Perspective of Start-Ups Professionals -- 4.3 Threats to Validity -- 5 Challenges for UX in Software Start-Ups -- 6 Conclusions -- References -- How to Write Ethical User Stories? Impacts of the ECCOLA Method -- 1 Introduction -- 2 Background -- 2.1 Implementing Ethics into Software Development -- 2.2 ECCOLA Method and It's Application -- 2.3 User Stories in Ethically Aligned Software Design -- 3 Research Framework -- 4 Study Design -- 4.1 Data Collection Methodology and Study Context -- 4.2 Data Analysis -- 5 Findings -- 5.1 Validity Threats -- 6 Discussion and Conclusion -- References -- Process Assessment -- Setting the Scope for a New Agile Assessment Model: Results of an Empirical Study -- 1 Introduction -- 2 Related Work -- 2.1 Model Development Approaches -- 2.2 Assessment Models -- 3 An Assessment Model Proposal -- 3.1 Methodology -- 3.2 Model Structure. |
505 8# - FORMATTED CONTENTS NOTE | |
Formatted contents note | 3.3 Validation -- 4 Results -- 4.1 Embrace Change to Deliver Customer Value Principle -- 4.2 Plan and Deliver Software Frequently Principle -- 4.3 Human Centricity Principle -- 4.4 Technical Excellence Principle -- 4.5 Customer Collaboration Principle -- 4.6 Overall Structure -- 5 Discussion -- 5.1 General Findings -- 5.2 Cluster Specific Findings -- 5.3 Threats to Validity -- 6 Conclusion and Future Work -- References -- Towards a Standardized Questionnaire for Measuring Agility at Team Level -- 1 Introduction -- 2 Related Work -- 3 Research Method -- 3.1 Initial Construction of the Questionnaire -- 3.2 Pretest -- 3.3 Evaluation in the Public Administration Sector -- 3.4 Expert Survey -- 4 Results -- 4.1 Defining Six Dimensions of Agility -- 4.2 Demographic questions -- 4.3 Assessment Questions -- 4.4 Weighting Questions -- 5 Discussion and Limitations -- 6 Conclusion and Future Work -- References -- The Impact of Agile Transformations on Organizational Performance: A Survey of Teams, Programs and Portfolios -- 1 Introduction -- 2 Related Work -- 2.1 Agile Transformations and Their History -- 2.2 Understanding Individual Transformation Journeys -- 2.3 The Impact of Agile Transformations -- 3 Research Question -- 4 Methodology -- 4.1 Survey Design -- 4.2 Data Collection -- 5 Results -- 5.1 Descriptive Statistics -- 5.2 Transformation Details -- 5.3 Correlation Analysis -- 6 Discussion -- 6.1 The Impact of Agile Transformations: General Observations -- 6.2 Impacted Metric Dimensions -- 6.3 The Relevance of Organizational Layers -- 6.4 Limitations -- 7 Conclusions -- References -- Measuring Software Delivery Performance Using the Four Key Metrics of DevOps -- 1 Introduction -- 2 The Four Key Metrics (FKM) -- 3 Multi-vocal Literature Review -- 3.1 Systematic Literature Review -- 3.2 Gray Literature Review -- 3.3 Results -- 4 Measure the Four Key Metrics. |
505 8# - FORMATTED CONTENTS NOTE | |
Formatted contents note | 5 Case Study -- 5.1 Case Description -- 5.2 Methodology -- 5.3 Results -- 6 Discussion -- 6.1 RQ1: How to Automatically Measure the FKM? -- 6.2 RQ2: How Valuable Is the Approach to Automatically Measure the FKM for Software Development Teams? -- 6.3 Limitations -- 6.4 Summary -- 6.5 Outlook -- 7 Conclusions -- References -- Large-scale Agile -- Evolution of the Agile Scaling Frameworks -- 1 Introduction -- 2 Background and Related Work -- 3 Research Methodology -- 4 Results -- 4.1 RQ1: Evolution of the Agile Scaling Frameworks -- 4.2 RQ2: Key Reasons Behind Creating Agile Scaling Frameworks -- 4.3 RQ3: Benefits of Adopting Agile Scaling Frameworks -- 4.4 RQ4: Challenges of Adopting Agile Scaling Frameworks -- 5 Discussion and Conclusions -- 5.1 Key Findings -- 5.2 Limitations -- 5.3 Conclusions -- References -- Coordination Strategies: Managing Inter-team Coordination Challenges in Large-Scale Agile -- 1 Introduction -- 2 Background and Related Work -- 2.1 Managing Dependencies in Large-Scale Agile Development -- 2.2 Coordination Strategies -- 3 Method and Analysis -- 3.1 Case Description -- 3.2 Data Collection and Analytical Procedures -- 3.3 Limitations and Threats to Validity -- 4 Findings -- 4.1 Strategy 1: Aligning Autonomous Teams -- 4.2 Strategy 2: Gaining and Maintaining Overview Across Teams -- 4.3 Managing Prioritization Issues -- 4.4 Managing Architecture and Technical Dependencies -- 5 Discussion -- 5.1 Implications for Practice -- 6 Conclusion and Future Research -- References -- Challenges of Adopting SAFe in the Banking Industry - A Study Two Years After Its Introduction -- 1 Introduction -- 2 Large Scale Agile Software Development -- 3 Related Work -- 3.1 Individual Case Studies -- 3.2 Systematic Literature Reviews -- 4 Method -- 5 Results -- 6 Discussion -- 7 Threats to Validity -- 8 Conclusions -- References. |
505 8# - FORMATTED CONTENTS NOTE | |
Formatted contents note | Benefits and Challenges of Adopting SAFe - An Empirical Survey -- 1 Introduction -- 2 Background and Related Work -- 2.1 SAFe -- 2.2 Previous Studies -- 3 Research Methodology -- 3.1 Research Questions -- 3.2 Survey Design -- 3.3 Data Analysis -- 4 Results and Discussion -- 4.1 Overview of the Contextual Information -- 4.2 Benefits of Adopting SAFe -- 4.3 Challenges of Adopting SAFe -- 4.4 Threats to Validity -- 5 Conclusions and Future Work -- References -- Short Contributions -- Using a Low Code Development Environment to Teach the Agile Methodology -- 1 Introduction -- 2 Related Work -- 2.1 Microsoft PowerApps -- 2.2 Course Background -- 2.3 Hypothesis -- 3 Research Methods -- 3.1 Participants -- 3.2 Materials -- 3.3 Procedure -- 4 Results -- 5 Discussion -- 5.1 Limitations and Further Research -- 6 Conclusion -- References -- Comparing Participants' Brainwaves During Solo, Pair, and Mob Programming -- 1 Introduction -- 2 Background -- 3 Collection and Analysis of Brainwaves -- 4 Experimental Method -- 5 Evaluation of Results -- 5.1 RQ1: Do Pair and Mob Programming Induce Lower Levels of Concentration (Attention) Compared to Solo Programming? -- 5.2 RQ2: Do Group Sessions Induce Higher Levels of Calmness (Meditation) Compared to Solo Programming? -- 5.3 RQ3: Does Difficulty Decrease When Working in a Group? -- 5.4 RQ4: Are there the Significant Differences Between Pair and Mob Programming Sessions? -- 6 Discussion -- 7 Conclusion and Future Work -- References -- Author Index. |
588 ## - SOURCE OF DESCRIPTION NOTE | |
Source of description note | Description based on publisher supplied metadata and other sources. |
590 ## - LOCAL NOTE (RLIN) | |
Local note | Electronic reproduction. Ann Arbor, Michigan : ProQuest Ebook Central, 2023. Available via World Wide Web. Access may be limited to ProQuest Ebook Central affiliated libraries. |
655 #4 - INDEX TERM--GENRE/FORM | |
Genre/form data or focus term | Electronic books. |
700 1# - ADDED ENTRY--PERSONAL NAME | |
Personal name | Lassenius, Casper. |
700 1# - ADDED ENTRY--PERSONAL NAME | |
Personal name | Wang, Xiaofeng. |
700 1# - ADDED ENTRY--PERSONAL NAME | |
Personal name | Kruchten, Philippe. |
776 08 - ADDITIONAL PHYSICAL FORM ENTRY | |
Relationship information | Print version: |
Main entry heading | Gregory, Peggy |
Title | Agile Processes in Software Engineering and Extreme Programming |
Place, publisher, and date of publication | Cham : Springer International Publishing AG,c2021 |
International Standard Book Number | 9783030780975 |
797 2# - LOCAL ADDED ENTRY--CORPORATE NAME (RLIN) | |
Corporate name or jurisdiction name as entry element | ProQuest (Firm) |
830 #0 - SERIES ADDED ENTRY--UNIFORM TITLE | |
Uniform title | Lecture Notes in Business Information Processing Series |
856 40 - ELECTRONIC LOCATION AND ACCESS | |
Uniform Resource Identifier | <a href="https://ebookcentral.proquest.com/lib/bacm-ebooks/detail.action?docID=6640049">https://ebookcentral.proquest.com/lib/bacm-ebooks/detail.action?docID=6640049</a> |
Public note | Click to View |
No items available.