|
 Allan Kelly's book Changing Software Development: Learning to Become Agile is not what you might expect at first. It's not about the practices and techniques to use in order to adopt and adapt Agile development, nor about how to execute and master various Agile practices. This book is about how Agile development and its adoption is really the application of knowledge management, learning organizations, and organizational change management. Those seeking a deeper understanding of this connection and what it means when trying to adopt agility won't be disappointed.This ~230 page book is divided into 12 chapters. Chapter 1 is simply a brief introduction to the purpose and premise of the book, which includes defining software development as knowledge work. I liked this because I'm a big fan of Philip Armour's work in this area in The Laws of Software Process, where Armour argues early in the book that software is not a product but rather a medium for storing executable knowledge (and therefore software development is a knowledge creation activity). I also like the early reference to Peter Drucker's work in this area.  The second chapter is about "Understanding Agile", particularly the values and principles of Agile and Lean and their underlying roots. Chapters 3-5 are about "Knowledge creation & management", "Learning", and "Learning organizations" and introduce us to the basic vocabulary, theory and models of those domains. Chapter 6 takes a step away from the previous three to discuss IT and the present nature of IT work and IT itself as an agent of change. Then Kelly discusses organizational change management in depth in the next three chapters (7-9). My favorite chapter is the one on change models (chapter 8) where we get to learn about each of the following theories: Lewin, Satir, Kotter, Theory E, Theory 0, and Appreciative Inquiry. The last three chapters (10-12) focus on leading and empowering individuals (through change), planning change, and final advice and recap of the books three key interlocking ideas:
About the Reviewer Brad Appleton is an enterprise SCM/ALM solution architect for a Fortune 100 technology company. Currently he helps projects and teams adopt and apply agile development & SCM practices. Brad also author's the Agile CM Environments blog, and is co-author of Software Configuration Management Patterns: Effective Teamwork, Practical Integration, the "Agile SCM" column in CMCrossroads.com's CM Journal, and is a former section editor for The C++ Report. Since 1987, Brad has extensive experience using, developing, and supporting SCM environments for teams of all shapes and sizes. He holds an M.S. in Software Engineering and a B.S. in Computer Science and Mathematics.
Set as favorite
Bookmark
Email this
Hits: 5373 Comments (0)
|
Show/hide comment form
| < Prev | Next > |
|---|
Agile Marketplace - Announcements and Special Offers
White Paper: Code Review IS an Agile Process!
Peer code review is one of the most effective ways to improve Software Quality – but is it Agile? Done correctly, it absolutely is. This white paper tells you how.
Download Today!
Virtual Conference: Collabnet Agile ALM
Stay current by attending CollabNet’s virtual conference, Agile ALM for Distributed Development, Thursday, April 15, from 7:30 am to 3:30 pm PDT. Free registration.
Register Today!
Webcast: Moving Build and Code Quality Upstream
This interactive panel discussion moderated by Bob Aiello, Editor-in-Chief fo the CM Journal brings industry experts Anders Wallgren, CTO of Electric Cloud and Gwyn Fisher, CTO of Klocwork together for a candid discussion of the cost savings, productivity and quality benefits that can be achieved by stabilizing builds and code quality as early in the development cycle as possible.
Register Now!
Collabnet -TeamForge 5.3
CollabNet TeamForge 5.3 includes Dynamic Planning—providing flexibility to model release scope and timeline in a single view. Now, you can easily manipulate/adjust release data.
Download Your Free Trial
Requirements-based testing (RBT) can help to ensure comprehensive test coverage, reducing the risk of failure and improving software quality. This white paper details how application lifecycle management can be used to more effectively implement RBT processes, offering greater collaboration, traceability and control.can help you increase efficiency, reduce project risk, and improve overall software quality. Learn how MKS Integrity for application lifecycle management enables RBT, delivering full lifecycle traceability to help ensure that project requirements have complete test planning and execution coverage.
Download the Requirements-Based Testing whitepaper
PureCM –SCM for Agile Teams
PureCM helps you to manage development in short iterations: keeping track of changes, supporting automated builds and preserving frequent snapshots of your projects.
Get the free trial now