• Author:
  • Moreira, Mario E.
• Subject:
  Computer Programming / Software Development
• Published by:
  John Wiley & Sons (UK)
• Published:
  16/10/2009
• Price:
  $82.99
• <  Buy this book  >

Effective Agile allows your team to move quickly and with confidence to evolve your business needs in short iterations. Configuration Management (CM) provides the smooth road and controls needed to move and maintain such a fast pace. The key is finding the right balance between Agile and CM, allowing you to stay on track whilst maintaining high velocity.

Many professionals find the alignment of CM and Agile a challenge, however adaptive CM for Agile should not mean throwing out the CM principles of identification, control, audit and report. Nor does it mean ignoring Agile values. Instead it means providing the best integration through rigorous yet lean CM practices that provide Agile projects with the sticky surface needed to keep it on track and with the integrity the customer expects. The question is how do we do this?

Adapting Configuration Management for Agile Teams provides very tangible approaches on how Configuration Management with its practices and infrastructure can be adapted and managed in order to directly benefit agile teams. Written by Mario E. Moreira, author of Software Configuration Management Implementation Roadmap, columnist for CM Crossroads online community and writer for the Agile Journal, this unique book provides concrete guidance on tailoring CM for Agile projects without sacrificing the principles of Configuration Management. When done properly, CM provides the lean and evolving structure needed for Agile projects to continue to run fast. CM for Agile can be a very powerful combination when done effectively.

Inside, learn how to:

• Adapt to Continuous Integration and Build introducing the notions of bit-size tasks, right-sizing branches, minimizing merging, emphasizing continuous build, and testing with teeth.
• Adapt CM Planning moving away from big-effort-up-front (BEUF) to a more evolutionary approach, applying an iteration 0 to get started, adapting CM roles and responsibilities, and considering wikis and other CM formats.
• Adapt CM to better support more effective Refactoring, Pair Programming, and Test Driven Development (TDD).
• Adapt CM to support Distributed Development for Agile teams when co-location is not an option by performing a distributed analysis and considering the best code access solution.
• Adapt CM to support Traceability, Baselines, Problem Management, CM Audit, and CM Reporting and lean metrics in an Agile context.
• Merge the mindsets of CM and Agile to form a very powerful partnership.
• Approach technical infrastructure for Agile thru Infrastructure Envisioning for brand new product lines or Infrastructure Refactoring for modifying existing infrastructure, focused on minimizing infrastructure debt while considering infrastructure on-premises or in-the-clouds.
• Approach CM infrastructure for Agile thru implementing CM Envisioning for a brand new product line that is following Agile methods or thru CM Refactoring when you need to adapt CM for an existing product line moving to Agile methods.
• Recognize those CM tools that can be a strategic Agile partner and how the more modern CM features help with implementing Agile in an effective manner.
• Effectively evaluate CM and Agile tools to ensure you are selecting those tools better suited for Agile and aligned with your Agile needs.
• Effectively support your Agile needs when your organization, product team, or project must align with CM standards and frameworks.

Sprinkled throughout the book are “Pit Stops” which provide insightful CM and Agile information in bit size chunks as take-aways for the reader and to encourage reading on.