Adapting Configuration Management for Agile Teams: Balancing Sustainability and Speed

Adapting Configuration Management for Agile Teams\r......Page 1
Contents......Page 3
1 Introduction: Racing with Confidence......Page 11
1.2 Who should Use this Book......Page 14
1.3 Navigation through this Book......Page 15
1.4 Value of this Book......Page 17
2 CM Primer......Page 19
2.1 Brief History of CM......Page 20
2.2 CM Values......Page 21
2.2.2 Control......Page 22
2.2.3 Audit......Page 24
2.3 CM Practices......Page 25
2.3.1 CM Planning Practice......Page 26
2.3.2 Version Control Practice......Page 28
2.3.3 Change Control Practice......Page 29
2.3.4 Build Management Practice......Page 30
2.3.6 Problem Management Practice......Page 31
2.3.7 Audit Practice......Page 32
2.3.8 Report Practice......Page 33
2.4.2 Benefits of CM to Development Staff......Page 34
2.5 CM Roles......Page 35
2.6.2 Thinking Integrity......Page 39
2.7 Relationship of CM to Culture, Methods, & Governance......Page 40
2.7.1 Relationship of Culture to CM......Page 41
2.7.3 Relationship of Methods to CM......Page 43
2.7.4 Avoiding Mistakes in CM Adoption......Page 44
2.8.2 CM websites......Page 45
3 Agile Primer......Page 46
3.1 Brief History of Agile......Page 49
3.2 Agile Values (a.k.a., Manifesto)......Page 50
3.3.1 Scrum......Page 51
3.3.1.2 Scrum Practices and Artifacts......Page 52
3.3.2.2 XP Practices and Rules......Page 54
3.3.3.1 DSDM......Page 56
3.3.3.3 Agile Unified Process......Page 57
3.4 Benefits of Agile......Page 58
3.5 Agile Personality Types......Page 59
3.5.2 Champion......Page 60
3.5.3 Workhorse......Page 61
3.5.5 Cowboy......Page 62
3.5.6 Deceiver......Page 63
3.6 Agile Roles......Page 64
3.6.2 Agile Project Manager/ScrumMaster......Page 65
3.6.4 Product Owner/Manager......Page 66
3.7 Agile Mindset......Page 67
3.7.4 Thinking Self-Empowered Team......Page 68
3.7.5 Thinking Collaboration......Page 69
3.8.1 Targeting the Sweet Spot......Page 70
3.8.2 Targeting the Product Level......Page 71
3.8.3.2 Ensure Continuous Customer Participation......Page 72
3.8.3.5 Introducing Agile Terminology......Page 73
3.8.3.9 Praising Cancelled Projects......Page 74
3.8.4 Determining Agile Readiness......Page 75
3.8.5 Measuring your Move Toward Agile......Page 76
3.8.6 Avoiding Mistakes in Agile Adoption......Page 77
3.9.1 Agile Books......Page 78
3.9.2 Agile Websites......Page 79
4 How CM and Agile Values Work Together......Page 80
4.1 Aligning Agile and CM Mindsets......Page 81
4.1.1 Challenges of Aligning the Minds......Page 82
4.2 Supporting Agile and CM Values without Sacrifice......Page 83
4.3 Value of Retrospective to CM......Page 84
4.4.1 Value Ranking of CM Practices by CM Professionals......Page 85
4.4.2 Value Rating of CM Practices by Agile Professionals......Page 86
4.4.2.1 Agile Perspective of CM Tools in General......Page 87
4.4.2.2 Agile Perspective of CM Planning......Page 88
4.4.2.4 Agile Perspective for Build Management......Page 90
4.4.2.7 Agile Perspective of CM Audit......Page 91
4.4.2.9 Agile Perspective of Release Engineering......Page 92
5 Approaching Infrastructure for Agile......Page 93
5.1 Guiding Principles for Approaching Infrastructure......Page 94
5.2.2 Agile Team as Customer of Infrastructure......Page 95
5.2.3 Architecture Envisioning......Page 96
5.3 Infrastructure Envisioning......Page 98
5.3.2 Thinking Iterations......Page 99
5.3.3 Tasks in Product Backlog or Infrastructure Backlog......Page 101
5.4 Infrastructure Refactoring......Page 102
5.4.2 Thinking in Iterations......Page 104
5.4.3 Tasks in Product Backlog or Infrastructure Backlog......Page 105
5.4.4 Reflections on Infrastructure Refactoring......Page 106
5.5 Owning on Premises or Renting in the Clouds......Page 107
5.5.1 Renting in the Clouds......Page 108
5.5.2 Owning Server and Renting Space (a.k.a., Co-location as a Service)......Page 110
5.5.3 Owning on Premises......Page 111
5.5.4 Reflections on Premises or in the Clouds......Page 112
6.1 CM Envisioning......Page 113
6.1.1 Strategizing for the Whole with Iteration 0......Page 114
6.1.1.2 Renting CM Infrastructure in the Clouds......Page 115
6.1.1.3 Sharing through CM Co-op Environments......Page 116
6.1.2 Implementing Incrementally......Page 117
6.2 CM Refactoring......Page 118
6.2.1 Iteration Planning or Iteration 0......Page 119
6.3 Automate, Automate, Automate for Agile......Page 120
6.3.1 Benefits of CM Automation to Agile......Page 122
6.3.2.1 Advantages of Smaller Chunks and Increments......Page 124
6.3.2.2 Disadvantages of Smaller Chunks and Increments......Page 125
6.3.3.1 Co-location of Team......Page 126
6.3.3.2 Co-location of Infrastructure......Page 128
6.3.3.3 Co-location of Functionality......Page 129
6.3.3.4 CM Considerations for Co-location and Agile......Page 130
7 Adapting CM Practices for Agile......Page 132
7.1 Adapting to Continuous Integration and Build......Page 133
7.1.1 The ‘‘Continuous’’ Cultural Shift......Page 135
7.1.1.1 How ‘‘Continuous’’ Adds Stress and Load to CM......Page 137
7.1.2.1 ABCs of Branching......Page 138
7.1.2.2 Private Workspace......Page 142
7.1.2.3 Factors for an Agile Branching Strategy......Page 145
7.1.2.4 Understanding Codelines......Page 148
7.1.2.5 Branching Scenarios......Page 149
7.1.2.6 Branching Challenges......Page 152
7.1.2.7 Branching Summary......Page 153
7.1.4 Effective Merge for Agile......Page 154
7.1.4.1 Merge Challenges......Page 156
7.1.5.1 Build Levels......Page 157
7.1.5.2 Build Automation for Continuous Integration......Page 159
7.1.6.2 Smoke Testing......Page 160
7.1.7 Reflections on Continuous Integration and Build......Page 161
7.2.1 Balancing Agile Values with Organization Needs......Page 162
7.2.2 Getting Started with Iteration 0......Page 163
7.2.3 Evolutionary CM Plan......Page 164
7.2.4 Reusable CM Plan......Page 165
7.2.5 Inherited CM Plan......Page 166
7.2.6 Types of CM Planning Formats......Page 167
7.2.7 Adapting CM Roles and Responsibilities for Agile......Page 171
7.2.7.1 CM as Holistic Part of the Agile Team......Page 172
7.2.7.2 Adjusting CM Responsibilities......Page 173
7.3 Adapting to Support Refactoring......Page 175
7.4 Adapting to Support Pair Programming......Page 177
7.5 Adapting to Support Test Driven Development (TDD)......Page 180
7.6.1 Distributed Analysis for Distributed Teams......Page 182
7.6.2 Code Access Approaches......Page 183
7.7 Adapting Change Control, Traceability, and Baselines......Page 187
7.7.1 Tracking Requirements or Stories and their Changes......Page 188
7.7.2 Adjusting the Notion of Baseline......Page 189
7.7.2.2 Baselines for Agile......Page 190
7.7.3.1 Traceability for the Right Reasons......Page 192
7.7.3.2 Traceability Considerations for Agile......Page 193
7.8 Adapting CM Audit......Page 194
7.8.1.2 What Baselines to Audit Against......Page 195
7.8.2.1 Automating Code to Build Baselines......Page 196
7.8.2.4 Giving Cadence to Industry Standards......Page 197
7.8.3 Reflections on CM Audit for Agile......Page 198
7.9.2 From Phase to Iteration......Page 199
7.9.5 Reflections on Problem Management for Agile......Page 200
7.10.1 Moving CM Report and Review into the Retrospective......Page 201
7.10.3 Constructing a Value-Added Metric......Page 202
7.10.3.2 Considering the Benefit of the Metric......Page 203
7.10.3.3 Determining Effort to Collect the Metric......Page 204
7.10.3.4 Assessing the Value of the Metric......Page 205
7.10.3.6 Monitoring of the Metric......Page 206
7.10.4 Waste and Examples of Value-Added CM Metrics......Page 207
7.10.5 Reflections on Adapting CM Report and Review for Agile......Page 209
8 CM Tool as a Strategic Agile Partner......Page 210
8.1 CM Tool Support for Software Development......Page 211
8.2.1 Whole Team......Page 215
8.2.4 Short Iterations......Page 216
8.2.8 Refactoring......Page 217
8.2.11 Traceability vs. Variance......Page 218
8.3.2 Outdated Tools......Page 219
8.4.3 Native Internet Support......Page 220
8.4.6 Codelines (a.k.a. Streams, Lines of Development)......Page 221
8.4.7 Change Tracking......Page 222
8.4.7.2 Transactions (a.k.a. Change Lists or Change Sets)......Page 223
8.4.7.3 Change Packages......Page 224
8.5 Integration with Your Agile Ecosystem......Page 225
8.5.3 Integration with the Test Automation Tool......Page 226
8.6 Conclusion......Page 227
9.1 Looking for Tools out there and in here......Page 228
9.1.1 Using a Vendor Tool Specific for Agile......Page 229
9.1.2 Using a Freeware Tool Specific for Agile......Page 231
9.1.3 Using a Homegrown Tool for Agile......Page 232
9.2 Levels of Technology Evaluation......Page 233
9.2.2 Demonstration Evaluation......Page 234
9.2.4 Considerations on Levels......Page 235
9.3 Perform a Technology Evaluation......Page 236
9.3.1.1 Version Control......Page 237
9.3.1.3 Change Control/Problem Management......Page 238
9.3.2 Investigating Agile Tools......Page 239
9.3.3 Evaluation Process......Page 240
9.3.3.1 Establishing Evaluation Team......Page 241
9.3.3.3 Conducting a Research Evaluation......Page 242
9.3.3.4 Conducting a Demo Evaluation......Page 243
9.3.3.5 Conducting a Pilot/Full Evaluation......Page 244
9.3.3.6 Considering a Request for Proposal (RfP)......Page 245
9.3.3.7 Acquisition Process – Owning or Renting......Page 247
10 Using CM Standards and Frameworks to Support Agile......Page 248
10.2 Compliance and IT Governance Requirements......Page 249
10.3 Communicating Your Approach to Senior Management......Page 250
10.4 Which Standards Should Be Considered?......Page 252
10.5.1 Continuous Integration without the Required Version ID......Page 254
10.6 How do Frameworks such as Cobit, ITIL, CMMI, and RUP support Agile?......Page 256
10.6.2 itSMF ITIL Framework......Page 257
10.6.4 Rational Unified Process (RUP) and Agile Unified Process (AUP)......Page 258
10.7.1 Change Control on Your Standards Tailoring......Page 259
10.8 Conclusion......Page 260
Bibliography......Page 261
Index......Page 265