بازاندیشی در بهره‌وری در مهندسی نرم‌افزار

Get the most out of this foundational reference and improve the productivity of your software teams. This open access book collects the wisdom of the 2017 "Dagstuhl" seminar on productivity in software engineering, a meeting of community leaders, who came together with the goal of rethinking traditional definitions and measures of productivity.The results of their work, __Rethinking Productivity in Software Engineering__, includes chapters covering definitions and core concepts related to productivity, guidelines for measuring productivity in specific contexts, best practices and pitfalls, and theories and open questions on productivity. You'll benefit from the many short chapters, each offering a focused discussion on one aspect of productivity in software engineering.Readers in many fields and industries will benefit from their collected work. Developers wanting to improve their personal productivity, will learn effective strategies for overcoming common issues that interfere with progress. Organizations thinking about building internal programs for measuring productivity of programmers and teams will learn best practices from industry and researchers in measuring productivity. And researchers can leverage the conceptual frameworks and rich body of literature in the book to effectively pursue new research directions.**What You'll Learn** * Review the definitions and dimensions of software productivity * See how time management is having the opposite of the intended effect * Develop valuable dashboards * Understand the impact of sensors on productivity * Avoid software development waste * Work with human-centered methods to measure productivity * Look at the intersection of neuroscience and productivity * Manage interruptions and context-switching **Who Book Is For**Industry developers and those responsible for seminar-style courses that include a segment on software developer productivity. Chapters are written for a generalist audience, without excessive use of technical terminology. Front Matter ....Pages i-xxviii Front Matter ....Pages 1-1 The Mythical 10x Programmer (Lutz Prechelt)....Pages 3-11 No Single Metric Captures Productivity (Ciera Jaspan, Caitlin Sadowski)....Pages 13-20 Why We Should Not Measure Productivity (Andrew J. Ko)....Pages 21-26 Front Matter ....Pages 27-27 Defining Productivity in Software Engineering (Stefan Wagner, Florian Deissenboeck)....Pages 29-38 A Software Development Productivity Framework (Caitlin Sadowski, Margaret-Anne Storey, Robert Feldt)....Pages 39-47 Individual, Team, Organization, and Market: Four Lenses of Productivity (Andrew J. Ko)....Pages 49-55 Software Productivity Through the Lens of Knowledge Work (Emerson Murphy-Hill, Stefan Wagner)....Pages 57-65 Front Matter ....Pages 67-67 Factors That Influence Productivity: A Checklist (Stefan Wagner, Emerson Murphy-Hill)....Pages 69-84 How Do Interruptions Affect Productivity? (Duncan P. Brumby, Christian P. Janssen, Gloria Mark)....Pages 85-107 Happiness and the Productivity of Software Engineers (Daniel Graziotin, Fabian Fagerholm)....Pages 109-124 Dark Agile: Perceiving People As Assets, Not Humans (Pernille Bjørn)....Pages 125-134 Front Matter ....Pages 135-135 Developers’ Diverging Perceptions of Productivity (André N. Meyer, Gail C. Murphy, Thomas Fritz, Thomas Zimmermann)....Pages 137-146 Human-Centered Methods to Boost Productivity (Brad A. Myers, Andrew J. Ko, Thomas D. LaToza, YoungSeok Yoon)....Pages 147-157 Using Biometric Sensors to Measure Productivity (Marieke van Vugt)....Pages 159-167 How Team Awareness Influences Perceptions of Developer Productivity (Christoph Treude, Fernando Figueira Filho)....Pages 169-178 Software Engineering Dashboards: Types, Risks, and Future (Margaret-Anne Storey, Christoph Treude)....Pages 179-190 The COSMIC Method for Measuring the Work-Output Component of Productivity (Charles Symons)....Pages 191-204 Benchmarking: Comparing Apples to Apples (Frank Vogelezang, Harold van Heeringen)....Pages 205-217 Front Matter ....Pages 219-219 Removing Software Development Waste to Improve Productivity (Todd Sedano, Paul Ralph, Cécile Péraire)....Pages 221-240 Organizational Maturity: The Elephant Affecting Productivity (Bill Curtis)....Pages 241-250 Does Pair Programming Pay Off? (Franz Zieris, Lutz Prechelt)....Pages 251-259 Fitbit for Developers: Self-Monitoring at Work (André N. Meyer, Thomas Fritz, Thomas Zimmermann)....Pages 261-270 Reducing Interruptions at Work with FlowLight (Manuela Züger, André N. Meyer, Thomas Fritz, David Shepherd)....Pages 271-279 Enabling Productive Software Development by Improving Information Flow (Gail C. Murphy, Mik Kersten, Robert Elves, Nicole Bryan)....Pages 281-292 Mindfulness as a Potential Tool for Productivity (Marieke van Vugt)....Pages 293-302 Back Matter ....Pages 303-310 Get the most out of this foundational reference and improve the productivity of your software teams. This open access book collects the wisdom of the 2017 "Dagstuhl" seminar on productivity in software engineering, a meeting of community leaders, who came together with the goal of rethinking traditional definitions and measures of productivity. The results of their work, Rethinking Productivity in Software Engineering, includes chapters covering definitions and core concepts related to productivity, guidelines for measuring productivity in specific contexts, best practices and pitfalls, and theories and open questions on productivity. You'll benefit from the many short chapters, each offering a focused discussion on one aspect of productivity in software engineering. Readers in many fields and industries will benefit from their collected work. Developers wanting to improve their personal productivity, will learn effective strategies for overcoming common issues that interfere with progress. Organizations thinking about building internal programs for measuring productivity of programmers and teams will learn best practices from industry and researchers in measuring productivity. And researchers can leverage the conceptual frameworks and rich body of literature in the book to effectively pursue new research directions. What You'll Learn Review the definitions and dimensions of software productivity See how time management is having the opposite of the intended effect Develop valuable dashboards Understand the impact of sensors on productivity Avoid software development waste Work with human-centered methods to measure productivity Look at the intersection of neuroscience and productivity Manage interruptions and context-switching Who Book Is For Industry developers and those responsible for seminar-style courses that include a segment on software developer productivity. Chapters are written for a generalist audience, without excessive use of technical terminology. ; Collects the wisdom of software engineering thought leaders in a form digestible for any developer Shares hard-won best practices and pitfalls to avoid An up to date look at current practices in software engineering productivity "Get the most out of this Open Access foundational reference and improve the productivity of your software teams. This open access book collects the wisdom of the 2017 "Dagstuhl" seminar on productivity in software engineering, a meeting of community leaders, who came together with the goal of rethinking traditional definitions and measures of productivity. The results of their work, Rethinking Productivity in Software Engineering, includes chapters covering definitions and core concepts related to productivity, guidelines for measuring productivity in specific contexts, best practices and pitfalls, and theories and open questions on productivity. You'll benefit from the many short chapters, each offering a focused discussion on one aspect of productivity in software engineering. Readers in many fields and industries will benefit from their collected work. Developers wanting to improve their personal productivity, will learn effective strategies for overcoming common issues that interfere with progress. Organizations thinking about building internal programs for measuring productivity of programmers and teams will learn best practices from industry and researchers in measuring productivity. And researchers can leverage the conceptual frameworks and rich body of literature in the book to effectively pursue new research directions"--Page 4 of cover