Leading Modern Technology Teams in Complex Times

Kevin R. Lowell ()

in Future of Business and Finance from Springer

Date: 2023
ISBN: 978-3-031-36429-7
References: Add references at CitEc
Citations:

There are no downloads for this item, see the EconPapers FAQ for hints about obtaining it.

Chapters in this book:

Ch 1 The Role of the Leader

Kevin R. Lowell

Ch 2 A Few Words About Complexity

Kevin R. Lowell

Ch 3 To the Manifesto!

Kevin R. Lowell

Ch 4 Using the Agile Manifesto as a Framework

Kevin R. Lowell

Ch 5 What Is Leadership?

Kevin R. Lowell

Ch 6 Employee Expectations Are Changing

Kevin R. Lowell

Ch 7 The Way Work Gets Done Is Changing

Kevin R. Lowell

Ch 8 Agile Principle 1: “Our Highest Priority Is to Satisfy the Customer Through Early and Continuous Delivery of Valuable Software”

Kevin R. Lowell

Ch 9 Agile Principle 2: “Welcome Changing Requirements, Even Late in Development. Agile Processes Harness Change for the Customer’s Competitive Advantage”

Kevin R. Lowell

Ch 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”

Kevin R. Lowell

Ch 11 Agile Principle 4: “Businesspeople and Developers Must Work Together Daily Throughout the Project”

Kevin R. Lowell

Ch 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”

Kevin R. Lowell

Ch 13 Agile Principle 6: “The Most Efficient and Effective Method of Conveying Information to and Within a Development Team Is Face-to-Face Conversation”

Kevin R. Lowell

Ch 14 Agile Principle 7: “Working Software Is the Primary Measure of Progress”

Kevin R. Lowell

Ch 15 Agile Principle 8: “Agile Processes Promote Sustainable Development. The Sponsors, Developers, and Users Should Be Able to Maintain a Constant Pace Indefinitely”

Kevin R. Lowell

Ch 16 Agile Principle 9: “Continuous Attention to Technical Excellence and Good Design Enhances Agility”

Kevin R. Lowell

Ch 17 Agile Principle 10: “Simplicity—The Art of Maximizing the Amount of Work Not Done—Is Essential”

Kevin R. Lowell

Ch 18 Agile Principle 11: “The Best Architectures, Requirements, and Designs Emerge from Self-Organizing Teams”

Kevin R. Lowell

Ch 19 Agile Principle 12: “At Regular Intervals, the Team Reflects on How to Become More Effective, Then Tunes and Adjusts Its Behavior Accordingly”

Kevin R. Lowell

Ch 20 Conclusion

Kevin R. Lowell

Related works:
This item may be available elsewhere in EconPapers: Search for items with the same title.

Export reference: BibTeX RIS (EndNote, ProCite, RefMan) HTML/Text

Persistent link: https://EconPapers.repec.org/RePEc:spr:fuobaf:978-3-031-36429-7

Ordering information: This item can be ordered from
http://www.springer.com/9783031364297

DOI: 10.1007/978-3-031-36429-7

Access Statistics for this book

More books in Future of Business and Finance from Springer
Bibliographic data for series maintained by Sonal Shukla () and Springer Nature Abstracting and Indexing ().