國立高雄大學圖資館 |

登入

回首頁

Leading modern technology teams in complex timesapplying the principles of the agile manifesto /

紀錄類型:	書目-電子資源 : Monograph/item
正題名/作者:	Leading modern technology teams in complex timesby Kevin R. Lowell.
其他題名:	applying the principles of the agile manifesto /
作者:	Lowell, Kevin R.
出版者:	Cham :Springer International Publishing :2023.
面頁冊數:	xxiii, 183 p. :ill., digital ;24 cm.
Contained By:	Springer Nature eBook
標題:	Software engineeringManagement.
電子資源:	https://doi.org/10.1007/978-3-031-36429-7
ISBN:	9783031364297$q(electronic bk.)

Leading modern technology teams in complex timesapplying the principles of the agile manifesto /
Lowell, Kevin R.

Leading modern technology teams in complex timesapplying the principles of the agile manifesto /[electronic resource] :by Kevin R. Lowell. - Cham :Springer International Publishing :2023. - xxiii, 183 p. :ill., digital ;24 cm. - Future of business and finance,2662-2475. - Future of business and finance..

Part I: The Role of the Leader -- 1. The Role of the Leader -- 2. A few words about complexity -- 3. To the Manifesto!- 4. Using the Agile Manifesto as a framework -- Part II: Leadership in Today's Technology Organizations -- 5. What is leadership?- Part III. Why Change the Way We Lead?- 6. Employee expectations are changing -- 7. The way work gets done is changing -- Part IV: The Twelve Principles of the Agile Manifesto -- 8. Agile Principle 1: "Our highest priority is to satisfy the customer through early and continuous delivery of valuable software." -- 9. Agile Principle 2: "Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage." -- 10. Agile Principle 3: "Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale." -- 11. Agile Principle 4: "Businesspeople and developers must work together daily throughout the project." -- 12. Agile Principle 5: "Build projects around motivated individuals. Give them the environment and support they need and trust them to get the job done." -- 13. Agile Principle 6: "The most efficient and effective method of conveying information to and within a development team is face-to-face conversation." -- 14. Agile Principle 7: "Working software is the primary measure of progress." -- 15. Agile Principle 8: "Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely." -- 16. Agile Principle 9: "Continuous attention to technical excellence and good design enhances agility." -- 17. Agile Principle 10: "Simplicity--the art of maximizing the amount of work not done--is essential." -- 18. Agile Principle 11: "The best architectures, requirements, and designs emerge from self-organizing teams." -- 19. Agile Principle 12: "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.".

The practices of agile software development and DevSecOps (Development integrated with Security integrated with Operations) differ from traditional linear systems of working. The people doing this work - who they are and what they expect - and the way the work gets done in today's tech industry demand a leadership practice specific to this way of working. This book explores leadership practice in today's technology industry using the twelve principles of the Agile Manifesto as a framework. Each of the twelve principles includes a section of key takeaways to help the reader apply the principle in practice. It extends traditional notions of leadership, specifically Complexity Leadership Theory (CLT), to one that is post-heroic, acknowledging the processual, conjunctive and generative nature of leadership relationships. Leader-follower dynamics are complex-they include power dynamics, conflict, ambiguity, and paradox-and technology organizations are complex. This book challenges the suitability of some aspects of complexity theory and offers practices that are more suitable for leading today's technology organizations.

ISBN: 9783031364297$q(electronic bk.)

Standard No.: 10.1007/978-3-031-36429-7doiSubjects--Topical Terms:

225916
Software engineering
--Management.

LC Class. No.: QA76.9.M3

Dewey Class. No.: 004.068

Leading modern technology teams in complex timesapplying the principles of the agile manifesto /
LDR:04233nmm a2200337 a 4500 001 651078
003 DE-He213
005 20230929183719.0
006 m d
007 cr nn 008maaau
008 240327s2023 sz s 0 eng d
020 $a 9783031364297$q(electronic bk.)
020 $a 9783031364280$q(paper)
024 7 $a 10.1007/978-3-031-36429-7 $2 doi
035 $a 978-3-031-36429-7
040 $a GP $c GP
041 0 $a eng
050 4 $a QA76.9.M3
072 7 $a KJC $2 bicssc
072 7 $a BUS041000 $2 bisacsh
072 7 $a KJC $2 thema
082 0 4 $a 004.068 $2 23
090 $a QA76.9.M3 $b L915 2023
100 1 $a Lowell, Kevin R. $3 961244
245 1 0 $a Leading modern technology teams in complex times $h [electronic resource] : $b applying the principles of the agile manifesto / $c by Kevin R. Lowell.
260 $a Cham : $b Springer International Publishing : $b Imprint: Springer, $c 2023.
300 $a xxiii, 183 p. : $b ill., digital ; $c 24 cm.
490 1 $a Future of business and finance, $x 2662-2475
505 0 $a Part I: The Role of the Leader -- 1. The Role of the Leader -- 2. A few words about complexity -- 3. To the Manifesto!- 4. Using the Agile Manifesto as a framework -- Part II: Leadership in Today's Technology Organizations -- 5. What is leadership?- Part III. Why Change the Way We Lead?- 6. Employee expectations are changing -- 7. The way work gets done is changing -- Part IV: The Twelve Principles of the Agile Manifesto -- 8. Agile Principle 1: "Our highest priority is to satisfy the customer through early and continuous delivery of valuable software." -- 9. Agile Principle 2: "Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage." -- 10. Agile Principle 3: "Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale." -- 11. Agile Principle 4: "Businesspeople and developers must work together daily throughout the project." -- 12. Agile Principle 5: "Build projects around motivated individuals. Give them the environment and support they need and trust them to get the job done." -- 13. Agile Principle 6: "The most efficient and effective method of conveying information to and within a development team is face-to-face conversation." -- 14. Agile Principle 7: "Working software is the primary measure of progress." -- 15. Agile Principle 8: "Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely." -- 16. Agile Principle 9: "Continuous attention to technical excellence and good design enhances agility." -- 17. Agile Principle 10: "Simplicity--the art of maximizing the amount of work not done--is essential." -- 18. Agile Principle 11: "The best architectures, requirements, and designs emerge from self-organizing teams." -- 19. Agile Principle 12: "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.".
520 $a The practices of agile software development and DevSecOps (Development integrated with Security integrated with Operations) differ from traditional linear systems of working. The people doing this work - who they are and what they expect - and the way the work gets done in today's tech industry demand a leadership practice specific to this way of working. This book explores leadership practice in today's technology industry using the twelve principles of the Agile Manifesto as a framework. Each of the twelve principles includes a section of key takeaways to help the reader apply the principle in practice. It extends traditional notions of leadership, specifically Complexity Leadership Theory (CLT), to one that is post-heroic, acknowledging the processual, conjunctive and generative nature of leadership relationships. Leader-follower dynamics are complex-they include power dynamics, conflict, ambiguity, and paradox-and technology organizations are complex. This book challenges the suitability of some aspects of complexity theory and offers practices that are more suitable for leading today's technology organizations.
650 0 $a Software engineering $x Management. $3 225916
650 0 $a Computer programming $x Management. $3 225724
650 0 $a Agile software development. $3 306567
650 1 4 $a Business Strategy and Leadership. $3 914887
650 2 4 $a IT in Business. $3 703717
710 2 $a SpringerLink (Online service) $3 273601
773 0 $t Springer Nature eBook
830 0 $a Future of business and finance. $3 849243
856 4 0 $u https://doi.org/10.1007/978-3-031-36429-7
950 $a Business and Management (SpringerNature-41169)