book

Agile Application Lifecycle Management: Using DevOps to Drive Process Improvement

Name: Agile Application Lifecycle Management: Using DevOps to Drive Process Improvement
ISBN: 9780132761857

by Bob Aiello, Leslie Sachs

June 2016

Intermediate to advanced

400 pages

10h 55m

English

Addison-Wesley Professional

Read now

Unlock full access

About This E-Book
Title Page
Copyright Page
Dedication Page
Contents
Preface
DevOps and the ALMIT GovernanceApplication Lifecycle ManagementAgile CM in an ALM WorldThe Definition of Agile ALMUnderstanding Where We Have Come FromPrinciples of Process ImprovementTerminologyUse of “I” versus “We”Why I Write About Agile CM, DevOps, and Agile ALMBlindness and Process ImprovementClassroom MaterialsWebsite for this BookWho Should Read This BookHow This Book Is OrganizedPart I: Defining the ProcessPart II: Automating the ProcessPart III: Establishing ControlsPart IV: Scaling the Process
Acknowledgments
About the Authors
Part I: Defining the Process
Chapter 1. Introducing Application Lifecycle Management Methodology
1.1 Goals of Application Lifecycle Management1.2 Why Is ALM Important?1.3 Where Do I Start?1.4 What Is Application Lifecycle Management?1.4.1 Remember the SDLC?1.4.2 Business Focus1.4.3 Agile or Not?1.4.4 Mature Process or Fluid?1.4.5 Rapid Iterative Development1.4.6 Core Configuration Management Best Practices1.4.7 Automation1.4.8 Continuous Integration1.4.9 Continuous Deployment1.4.10 Change Management1.4.11 IT Operations1.4.12 DevOps1.4.13 Retrospectives1.4.14 IT Governance1.4.15 Audit and Regulatory Compliance1.4.16 ALM and the Cloud1.4.17 Mainframe1.4.18 Integration across the Enterprise1.4.19 Quality Assurance and Testing1.4.20 Role of Personality1.5 ConclusionReferences

Chapter 2. Defining the Software Development Process
2.1 Goals of Defining the Software Development Process2.2 Why Is Defining the Software Development Process Important?2.3 Where Do I Start?2.4 Explaining the Software Development Lifecycle2.5 Systems versus Software Development Lifecycle2.6 Defining Requirements2.6.1 Managing Complexity and Change2.6.2 Validity of Requirements2.6.3 Testing Requirements2.6.4 Functional Requirements2.6.5 Nonfunctional Requirements2.6.6 Epics and Stories2.6.7 Planning for Changing Requirements2.6.8 Workflow for Defining Requirements2.7 Test-Driven Development2.8 Designing Systems2.9 Software Development2.10 Testing2.10.1 Testing the Application2.10.2 Testing the Process Itself2.11 Continuous Integration2.12 Continuous Delivery and Deployment2.13 Defining Phases of the Lifecycle2.14 Documentation Required2.15 DevOps2.16 Communicating with All Stakeholders2.17 Production Support2.18 Maintenance and Bugfixes2.19 Lifecycle in the Beginning2.20 Maintenance of the Lifecycle2.21 Creating the Knowledge Base2.22 Continuous Improvement2.23 Conclusion
Chapter 3. Agile Application Lifecycle Management
3.1 Goals of Agile Application Lifecycle Management3.2 Why Is Agile ALM Important?3.3 Where Do I Start?3.4 Understanding the Paradigm Shift3.5 Rapid Iterative Development3.6 Remember RAD?3.7 Focus on 12 Agile Principles3.8 Agile Manifesto3.9 Fixed Timebox Sprints3.10 Customer Collaboration3.11 Requirements3.12 Documentation3.13 Conclusion
Chapter 4. Agile Process Maturity
4.1 Goals of Agile Process Maturity4.2 Why Is Agile Process Improvement Important?4.3 Where Do I Start?4.4 Understanding Agile Process Maturity4.4.1 Adherence to the Principles4.4.2 Repeatable Process4.4.3 Scalability (Scrum of Scrums)4.4.4 Comprehensive (Items on the Right)4.4.5 Transparency and Traceability4.4.6 IT Governance4.4.7 Coexistence with Non-agile Projects4.4.8 Harmonization with Standards and Frameworks4.4.9 Following a Plan4.4.10 Continuous Process Improvement4.5 Applying the Principles4.6 Recognition by the Agile Community4.7 Consensus within the Agile Community4.8 What Agile Process Maturity Is Not4.9 What Does an Immature Agile Process Look Like?4.10 Problems with Agile4.11 Waterfall Pitfalls4.11.1 Mired in Process4.11.2 Pretending to Follow the Process4.12 The Items on the Right4.12.1 Adjusting Ceremony4.13 Agile Coexisting with Non-Agile4.14 IT Governance4.14.1 Providing Transparency4.15 ALM and the Agile Principles4.16 Agile as a Repeatable Process4.16.1 Scalability4.16.2 Delivering on Time and within Budget4.16.3 Quality4.17 Deming and Quality Management4.17.1 Testing versus Building Quality In4.17.2 Productivity4.18 Agile Maturity in the Enterprise4.18.1 Consistency across the Enterprise4.18.2 Marketing the New Approach4.19 Continuous Process Improvement4.19.1 Self-Correcting4.20 Measuring the ALM4.20.1 Project Management Office (PMO) Metrics4.21 Vendor Management4.22 Hardware Development4.22.1 Firmware4.23 Conclusion
Chapter 5. Rapid Iterative Development
5.1 Goals of Rapid Iterative Development5.2 Why Is Rapid Iterative Development Important?5.3 Where Do I Start?5.4 The Development View5.5 Controlled Isolation5.6 Managing Complexity5.7 Continuous Integration5.8 It’s All About (Technology) Risk5.9 Taming Technology5.10 Designing Architecture5.11 ConclusionFurther Reading
Part II: Automating the Process
Chapter 6. Build Engineering in the ALM
6.1 Goals of Build Engineering6.2 Why Is Build Engineering Important?6.3 Where Do I Start?6.4 Understanding the Build6.5 Automating the Application Build6.6 Creating the Secure Trusted Base6.7 Baselining6.8 Version Identification6.9 Compile Dependencies6.10 Build in the ALM6.11 The Independent Build6.12 Creating a Build Robot6.13 Building Quality In6.14 Implementing Unit Tests6.15 Code Scans6.16 Instrumenting the Code6.17 Build Tools6.18 Conclusion
Chapter 7. Automating the Agile ALM
7.1 Goals of Automating the Agile ALM7.2 Why Automating the ALM Is Important7.3 Where Do I Start?7.4 Tools7.4.1 Do Tools Matter?7.4.2 Process over Tools7.4.3 Understanding Tools in the Scope of ALM7.4.4 Staying Tools Agnostic7.4.5 Commercial versus Open Source7.5 What Do I Do Today?7.6 Automating the Workflow7.7 Process Modeling Automation7.8 Managing the Lifecycle with ALM7.9 Broad Scope of ALM Tools7.10 Achieving Seamless Integration7.11 Managing Requirements of the ALM7.12 Creating Epics and Stories7.13 Systems and Application Design7.14 Code Quality Instrumentation7.15 Testing the Lifecycle7.16 Test Case Management7.17 Test-Driven Development7.18 Environment Management7.18.1 Gold Copies7.19 Supporting the CMDB7.20 Driving DevOps7.21 Supporting Operations7.22 Help Desk7.23 Service Desk7.24 Incident Management7.25 Problem Escalation7.26 Project Management7.27 Planning the PMO7.28 Planning for Implementation7.29 Evaluating and Selecting the Right Tools7.30 Defining the Use Case7.31 Training Is Essential7.32 Vendor Relationships7.33 Keeping Tools Current7.34 Conclusion
Chapter 8. Continuous Integration
8.1 Goals of Continuous Integration8.2 Why Is Continuous Integration Important?8.3 Where Do I Start?8.4 Principles in Continuous Integration8.5 Challenges of Integration8.6 Commit Frequently8.7 Rebase and Build Before Commit8.8 Merge Nightmares8.9 Smaller Units of Integration8.10 Frequent Integration Is Better8.10.1 Easier to Find Issues8.10.2 Easier to Fix Problems8.10.3 Fix Broken Builds8.11 Code Reviews8.12 Establishing a Build Farm8.12.1 Virtualization and Cloud Computing8.13 Preflight Builds8.14 Establishing the Build and Deploy Framework8.15 Establishing Traceability8.16 Better Communication8.17 Finger and Blame8.18 Is the Nightly Build Enough?8.19 Selecting the Right Tools8.19.1 Selecting the Right CI Server8.19.2 Selecting the Shared Repository8.20 Enterprise Continuous Integration8.21 Training and Support8.22 Deploy and Test8.23 Tuning the Process8.23.1 Getting Lean8.23.2 Interesting Builds8.24 CI Leads to Continuous Deployment8.25 Conclusion
Chapter 9. Continuous Delivery and Deployment
9.1 Goals of Continuous Deployment9.2 Why Is Continuous Deployment Important?9.3 Where Do I Start?9.4 Establishing the Deployment Pipeline9.5 Rapid Incremental Deployment9.6 Minimize Risk9.7 Many Small Deployments Better than a Big Bang9.8 Practice the Deploy9.9 Repeatable and Traceable9.10 Workflow Automation9.10.1 Kanban—Push versus Pull9.11 Ergonomics of Deployments9.12 Verification and Validation of the Deployment9.13 Deployment and the Trusted Base9.14 Deploy to Environments that Mirror Production9.15 Assess and Manage Risk9.16 Dress Rehearsal and Walkthroughs9.17 Imperfect Deployments9.18 Always Have a Plan B9.19 Smoke Test9.20 Conclusion
Part III: Establishing Controls
Chapter 10. Change Management
10.1 Goals of Change Management10.2 Why Is Change Management Important?10.3 Where Do I Start?10.4 Traceability for Compliance10.5 Assess and Manage Risk10.6 Communication10.7 Change in Application Lifecycle Management10.8 The Change Ecosystem10.9 QA and Testing10.10 Monitoring Events10.11 Establishing the Command Center10.12 When Incidents Occur10.13 Problems and Escalation10.14 The Change Management Process10.14.1 Entry/Exit Criteria10.14.2 Post-Implementation10.15 Preapproved Changes10.16 Establishing the Change Management Function10.16.1 Change Control Board10.16.2 Change Advisory Board10.17 Change Control Topology10.17.1 A Priori10.17.2 Gatekeeping10.17.3 Configuration Control10.17.4 Emergency Change Control10.17.5 Process Change Control10.17.6 E-change Control10.17.7 Preapproved10.18 Coordinating across the Platform10.19 Coordinating across the Enterprise10.20 Beware of Fiefdoms10.21 Specialized Change Control10.22 Vendor Change Control10.23 SaaS Change Control10.24 Continuous Process Improvement10.25 Conclusion
Chapter 11. IT Operations
11.1 Goals of IT Operations11.2 Why Is IT Operations Important?11.3 Where Do I Start?11.4 Monitoring the Environment11.4.1 Events11.4.2 Incidents11.4.3 Problems11.5 Production Support11.6 Help Desk11.6.1 Virtual Help Desks11.6.2 Remote Work11.6.3 Virtual World Help Desk11.6.4 Developers on the Help Desk11.7 IT Process Automation11.7.1 Knowledge Management11.8 Workflow Automation11.9 Communication Planning11.9.1 Silos within the Organization11.10 Escalation11.10.1 Level 111.10.2 Level 211.10.3 Level 311.11 DevOps11.12 Continuous Process Improvement11.13 Utilizing Standards and Frameworks11.13.1 ITIL v311.13.2 Knowledge Management11.13.3 ISACA Cobit11.14 Business and Product Management11.15 Technical Management11.16 IT Operations Management11.17 IT Operations Controls11.17.1 Facilities Management11.18 Application Management11.18.1 Middleware Support11.18.2 Shared Services11.19 Security Operations11.19.1 Center for Internet Security11.19.2 Outsourcing11.20 Cloud-Based Operations11.20.1 Interfacing with Vendor Operations11.21 Service Desk11.21.1 Centralized11.21.2 Virtual11.21.3 Specialized11.21.4 Vendor Escalation11.22 Staffing the Service Desk11.23 Incidents and Problems11.24 Knowledge Management11.25 Conclusion
Chapter 12. DevOps
12.1 Goals of DevOps12.2 Why Is DevOps Important?12.3 Where Do I Start?12.4 How Do I Implement DevOps?12.5 Developers and Operations Conflict12.6 Developers and Operations Collaboration12.7 Need for Rapid Change12.8 Knowledge Management12.9 The Cross-Functional Team12.10 Is DevOps Agile?12.11 The DevOps Ecosystem12.12 Moving the Process Upstream12.12.1 Left-Shift12.12.2 Right-Shift12.13 DevOps in Dev12.14 DevOps as Development12.14.1 Deployment Pipeline12.15 Dependency Control12.16 Configuration Control12.17 Configuration Audits12.18 QA and DevOps12.19 Information Security12.20 Infrastructure as Code12.21 Taming Complexity12.22 Automate Everything12.23 Disaster Recovery and Business Continuity12.24 Continuous Process Improvement12.25 Conclusion
Chapter 13. Retrospectives in the ALM
13.1 Goals of Retrospectives13.2 Why Are Retrospectives Important?13.3 Where Do I Start?13.4 Retrospectives as Process Improvement13.4.1 Start with Assessing Success13.4.2 Incidents and Problems13.4.3 Mistakes Are Good13.4.4 Personality and Disposition13.4.5 Don’t Just Tell Me What I Want to Hear13.5 Which Mode Should You Use?13.5.1 In Person Is Best13.5.2 Online and Video Conferencing13.5.3 Teleconference13.5.4 Virtual Worlds13.6 Perspective Is Essential13.6.1 Developers13.6.2 Customers13.6.3 Tester13.6.4 Operations13.7 DevOps: The Cross-Functional View13.8 Understanding the Use Case13.8.1 Epics and Stories13.9 Retrospectives as Leadership13.9.1 Removing Barriers13.10 Running the Meeting13.10.1 Probing and Questioning13.11 Retrospectives Supporting ITIL13.11.1 Incidents13.11.2 Problems13.12 Retrospectives and Defect Triage13.13 Retrospectives as Crisis Management13.14 Supporting IT Governance13.15 Audit and Regulatory Compliance13.16 Retrospectives as Risk Management13.17 Vendor Management13.18 Too Much Process13.19 Corporate Politics13.20 Metrics and Measurement13.21 Conclusion
Part IV: Scaling the Process
Chapter 14. Agile in a Non-Agile World
14.1 Goals of Hybrid Agile14.2 Why Is Hybrid Agile Important?14.3 Where Do I Start?14.4 Pragmatic Choices14.5 The Best of Both Worlds14.6 Keeping It Agile14.7 Establishing the Agile Pilot14.8 Transitioning to Agile14.9 Having a Baby14.10 The Elephant in the Room14.11 Are We There Yet?14.12 Agile Disasters14.13 Developer View14.14 No Information Radiators Allowed14.15 Waterfall Is Iterative, Too14.16 Document Requirements as Much as Possible14.17 Last Responsible Moment14.18 Technology Risk14.19 Understanding the Ecosystem14.20 Mature Agile14.21 Meeting IT Governance Requirements14.22 Conclusion
Chapter 15. IT Governance
15.1 Goals of IT Governance15.2 Why Is IT Governance Important?15.3 Where Do I Start?15.4 Senior Management Makes Decisions15.5 Communicating Up15.6 How Much Work Is Going On?15.7 Identify and Manage Risk15.8 Time and Resources15.9 Scalability with More Resources15.10 Delays Happen15.11 The Helicopter Mom15.12 I Told You That Already15.13 Learning from Mistakes15.14 Governance Ecosystem15.15 Continuous Process Improvement15.16 Governance and Compliance15.17 Conclusion
Chapter 16. Audit and Regulatory Compliance
16.1 Goals of Audit and Regulatory Compliance16.2 Why Are Audit and Regulatory Compliance Important?16.3 Where Do I Start?16.4 Compliance with What?16.5 Establishing IT Controls16.6 Internal Audit16.7 External Audit16.8 Federally Mandated Guidelines16.8.1 Section 404 of the Sarbanes-Oxley Act of 200216.8.2 Financial Industry Regulatory Authority16.8.3 Health Insurance Portability and Accountability Act of 199616.8.4 ISACA Cobit16.8.5 Government Accountability Office16.8.6 Office of the Comptroller of the Currency (OCC)16.9 Essential Compliance Requirements16.10 Improving Quality and Productivity through Compliance16.11 Conducting an Assessment16.12 Conclusion
Chapter 17. Agile ALM in the Cloud
17.1 Goals of ALM in the Cloud17.2 Why Is ALM in the Cloud Important?17.3 Where Do I Start?17.4 Understanding the Cloud17.5 Developing in the Cloud17.5.1 Source Code Management in the Cloud17.5.2 Build Automation in the Cloud17.5.3 Release Engineering in the Cloud17.5.4 Deployment in the Cloud17.6 Change Management in the Cloud17.6.1 Service Provider Notification17.7 Managing the Lifecycle with ALM17.8 Cloud-based ALM Tools17.9 Achieving Seamless Integrations17.10 Iterative Development in the Cloud17.10.1 Development Models in SaaS17.11 Interfacing with Your Customers17.11.1 Fronting Service Providers17.12 Managing with SLAs17.12.1 Reliance upon Service Providers17.13 Managing Cloud Risk17.14 Development and Test Environments for All17.14.1 Starting Small17.15 Environment Management17.15.1 Gold Copies17.15.2 CMDB in the Cloud17.16 DevOps in the Cloud17.17 Controlling Costs and Planning17.18 Conclusion
Chapter 18. Agile ALM on the Mainframe
18.1 Goals of Agile ALM on the Mainframe18.2 Why Is Agile ALM on the Mainframe Important?18.3 Where Do I Start?18.4 DevOps on the Mainframe18.5 Conclusion
Chapter 19. Integration across the Enterprise
19.1 Goals of Integration across the Enterprise19.2 Why Is Integration across the Enterprise Important?19.3 Where Do I Start?19.4 Multiplatform19.5 Coordinating across Systems19.6 Understanding the Interfaces19.7 The Enterprise Ecosystem19.8 Release Coordination19.9 Conclusion
Chapter 20. QA and Testing in the ALM
20.1 Goals of QA and Testing20.2 Why Are QA and Testing Important?20.3 Where Do I Start?20.4 Planning the Testing Process20.5 Creating the Test Cases20.6 Ensuring Quality20.7 Ensuring Quality from the Beginning20.8 Conclusion
Chapter 21. Personality and Agile ALM
21.1 Goals of Personality and the Agile ALM21.2 Why Are Personality and Agile ALM Important?21.3 Where Do I Start?21.3.1 Understanding the Culture21.3.2 Probing Deeper into the Organization’s Psyche21.4 Group Dynamics21.4.1 Using DevOps to Drive Out Silos21.4.2 Managing Power and Influence in DevOps21.5 Intergroup Conflict21.5.1 Overly Agreeable People and Other Challenges21.5.2 Learned Helplessness21.5.3 Introspection and the Postmortem21.6 Managing Stress and Dysfunctional Behavior21.6.1 The Danger of Learned Complacency21.6.2 Dealing with Aggressive Team Members21.6.3 Extremism in the Workplace21.7 Taking a Positive Approach21.7.1 How Positive Psychology Can Help Your Organization21.7.2 Three Pillars of Positive Psychology21.7.3 Using Positive Psychology to Motivate Your Team21.7.4 Learning from Mistakes21.7.5 Positive Psychology in DevOps21.8 ConclusionReferencesFurther Reading
Chapter 22. The Future of ALM
22.1 Real-World ALM22.2 ALM in Focus22.3 Conclusion
Index

Content preview from Agile Application Lifecycle Management: Using DevOps to Drive Process Improvement

Chapter 7. Automating the Agile ALM

Application lifecycle management (ALM) touches every aspect of the software and systems lifecycle. This includes requirements gathering, design, development, testing, application deployment, and operations support. Automation plays a major role in the agile ALM, which sets it apart in many ways from other software development methodologies. Since you simply cannot implement all of these practices at once, you will need to assess the scope and priorities for your team. That said, it is essential to appreciate the big picture at all times so that the functions you implement are in alignment with the overall goals and structure of your ALM.

7.1 Goals of Automating the Agile ALM

The goal in automating the application ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Agile Project Management with Azure DevOps: Concepts, Templates, and Metrics

Publisher Resources

ISBN: 9780132761857Purchase book

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Agile Application Lifecycle Management: Using DevOps to Drive Process Improvement

by Bob Aiello, Leslie Sachs