DevOps

Best Practices

Bart de Best

paperback/ gebrocheerd: € 51.45: GRATIS verzending! (NL)
ISBN: 9789492618078, geïllustreerd, 168 blz., August 2017, Engels
Formaat: 29.0 (h) x 20.6 (b) x 1.4 (d) cm. Gewicht: 551 gram.

Uitgever: Leonon Media

serienaam/reeks: Dbmetrics

redactie: Louis van Hemmen

trefwoorden: devops, agile, scrum, story telling, best practice

beschrijving

In recent years, many organisations have experienced the benefits of using Agile approaches such as Scrum and Kanban. The software is delivered faster whilst quality increases and costs decrease.

The fact that many organisations that applied the Agile approach did not take into account the traditional service management techniques, in terms of information management, application management and infrastructure management, is a major disadvantage.

The solutions to this problem has been found in the Dev (Development) Ops (Operations) approach. Both worlds are merged into one team, thus sharing the knowledge and skills.

Inkijkexemplaar:

Meer teksten en voorbeelden:

over de schrijver(s)Drs. Ing. Bart de Best RI is vanaf 1985 werkzaam in de ICT, momenteel is hij als zzp'er werkzaam als consultant. Hij heeft voornamelijk bij de top 100 van het Nederlandse bedrijfsleven en de overheid gewerkt.

Ruim tien 12 jaar vervulde hij functies in alle fasen van de systeemontwikkeling, inclusief exploitatie en beheer. De laatste 14 jaar heeft hij zich toegelegd op het service management-vakgebied en vervult hij alle aspecten van de kennislevenscyclus van service management, zoals het schrijven en geven van trainingen, het adviseren van beheerorganisaties bij de inrichting, het verbeteren of uitbesteden van het beheer; het examineren van service managers en het reviewen en auditen van beheerorganisaties.

Hij is op zowel HTS-niveau als universitair niveau afgestudeerd op het beheervakgebied.
inhoudsopgaveTable of Contents
1 INTRODUCTION
1.1 BACKGROUND
1.2 OBJECTIVE
1.3 TARGET AUDIENCE
1.4 STRUCTURE
1.5 READING GUIDELINES
2 DEVOPS DEFINED (#01)
2.1 DEVOPS – THE ORIGIN
2.2 DEVOPS – WHAT IS IT?
2.3 DEVOPS - COMMON FEATURES
2.4 DEVOPS - A FRAMEWORK
2.5 DEVOPS - CONCLUSION
3 DEVOPS PROCESS (#02)
3.1 INTRODUCTION
3.2 DEVOPS PROCESS
3.2.1 Planning process
3.2.2 Code process
3.2.3 Build process
3.2.4 Test process
3.2.5 Release process
3.2.6 Deployment process
3.2.7 Operate process
3.2.8 Monitor process
3.2.9 Relationship to the DevOps framework
4 ORGANISATION PATTERNS (#3)
4.1 INTRODUCTION
4.2 TERMS
4.3 CONCEPTS
4.4 PATTERNS
4.4.1 Business line pattern
4.4.2 Portfolio pattern
4.4.3 Information value chain pattern
4.5 FAQ
5 PROCESS BLUE PRINT (#4)
5.1 INTRODUCTION
5.2 TERMS
5.3 CONCEPTS
5.4 PATTERNS
5.4.1 Pattern classic service organisation
5.4.2 Pattern Agile Development team
5.4.3 Pattern DevOps team
5.5 FAQ
6 TOOL PORTFOLIO (#05).
6.1 INTRODUCTION VIII DevOps Best Practices
6.2 TERMS
6.3 CONCEPTS
6.4 BEST PRACTICES
6.4.1 Ownership
6.4.2 Portfolio framework
6.4.3 Portfolio analysis.
6.4.4 Pitfalls
7 MONITORING (#06)
7.1 INTRODUCTION
7.2 TERMS
7.3 CONCEPTS
7.4 BEST PRACTICES
7.4.1 Monitor principles
7.4.2 Monitor tools and SLA’s
7.4.3 DevOps process
8 THE DELIVERABLES (#7)
8.1 TERMS
8.2 CONCEPTS
8.3 BEST PRACTICES
8.3.1 Up front definition is done
8.3.2 Funnel management
8.3.3 Roadmap
8.3.4 Release planning
9 WATERFALL IS NOT YET OVER (#8)
9.1 INTRODUCTION
9.2 TERMS
9.3 CONCEPTS
9.4 BEST PRACTICES
9.4.1 Waterfall is to stay for ever
9.4.2 Agile project management is useful as:
9.4.3 Agile project management is not useful as:
9.4.4 The essence
10 FROM FUNNEL TO SCRUM BOARD (#9)
10.1 INTRODUCTION
10.2 TERMS
10.3 CONCEPTS
10.4 BEST PRACTICES
10.4.1 Lifecycle management
10.4.2 Functional and technical design
10.4.3 Test cases
10.4.4 Traceability
10.4.5 Information debt
11 SLA’S AND NFR’S (#10)
11.1 INTRODUCTION
11.2 TERMS
11.3 CONCEPTS
11.4 BEST PRACTICES – DEVOPS PLAN
Table of Contents IX
11.4.1 Is a SLA still needed?
11.4.2 SLA in the funnel
11.4.3 SLA in the roadmap
11.4.4 SLA in the release planning
11.4.5 SLA in the code phase
11.4.6 SLA in the build phase
11.4.7 SLA in the test phase
11.4.8 SLA in the release phase
11.4.9 SLA in the operate phase
11.4.10 SLA in the monitor phase
12 FUNCTIONAL & TECHNICAL DESIGN (#11)
12.1 INTRODUCTION
12.2 TERMS
12.3 BEST PRACTICES FOR DEVOPS CODE
12.3.1 The DevOps process
12.3.2 The functional design
12.3.3 The technical design
12.3.4 Conclusion
13 SPLITTING FEATURES (#12)
13.1 INTRODUCTION
13.2 TERMS
13.3 CONCEPTS
13.4 BEST PRACTICES
Vertical split
13.4.1 Horizontal split 13.4.2 The preference
14 DEFINING FEATURES AND STORIES (#13)
14.1 INTRODUCTION
14.2 DEFINITIONS
14.3 CONCEPTS
14.4 BEST PRACTICES FOR DEVOPS CODE
14.4.1 Why a data model
14.4.2 Attributes for a Feature
14.4.3 Attrtibutes of a story
15 AGILE CHANGE MANAGEMENT PROCESS (#14)
15.1 INTRODUCTION
15.2 TERMS
15.3 CONCEPTS
15.4 BEST PRACTICES
15.4.1 Level of control
15.4.2 Waste
15.4.3 Feature admin
16 STATIC OR DYNAMIC REQUIREMENTS (#15)
16.1 INTRODUCTION
16.2 TERMS
16.3 CONCEPTS
16.4 BEST PRACTICES
X DevOps Best Practices
16.4.1 Dynamisch or not?
16.4.2 The consideration
17 SOFTWARE CONFIGURATION ITEMS (#16)
17.1 INTRODUCTION
17.2 TERMS
17.3 CONCEPTS
17.4 BEST PRACTICES FOR DEVOPS CODE
17.4.1 Relationship CMDB en S-CMDB.
17.4.2 Usage S-CMDB
17.4.3 Usage of S-CI
18 VERSIONING (#17)
18.1 INTRODUCTION
18.2 TERMS
18.3 CONCEPTS
18.4 BEST PRACTICES
18.4.1 Why versioning management?
18.4.2 Where in the DevOps process are objects versioned?
18.4.3 Why version these objects?
19 STANDARD, RULES AND GUIDELINES (#18)
19.1 INTRODUCTION
19.2 TERMS
19.3 CONCEPTS
19.3.1 Quality Control & Assurance (QCA)
19.4 BEST PRACTICES
19.4.1 Modularity
19.4.2 Branching
19.4.3 Versioning
19.4.4 Code Quality
19.4.5 Event management
19.4.6 Conclusion
20 BRANCHING (#19)
20.1 INTRODUCTION
20.2 TERMS
20.3 CONCEPTS
20.4 BEST PRACTICES
20.4.1 Does branching fit with DevOps?
20.4.2 Incidents
20.4.3 Forward releases
20.4.4 Branche strategy
20.4.5 Conclusion
21 EXCEPTION MANAGEMENT (#20)
21.1 INTRODUCTION
21.2 TERMS
21.3 CONCEPTS
21.4 BEST PRACTICES
21.4.1 Where does an exception occur?
21.4.2 Which information needs operations?
Table of Contents XI
21.4.3 How to determine that the exceptions are complete?
21.4.4 Exception management in the DevOps process:
21.4.5 Conclusion
22 CONTINUOUS INTEGRATION (#21)
22.1 INTRODUCTION
22.2 TERMS
22.3 CONCEPTS
22.4 BEST PRACTICES
22.4.1 CI Lifecycle
22.4.2 CI Best practices
22.4.3 CI Maturity
22.4.4 CI growth path
22.4.5 CI tools
23 TOOLING (#22)
23.1 INTRODUCTION
23.2 TERMS
23.3 CONCEPTS
23.4 BEST PRACTICES
Scope
23.4.1 Datamodel
23.4.2 Tool requirements
24 TEST TYPES (#23)
24.1 INTRODUCTION
24.2 TERMS
24.3 CONCEPTS
24.4 BEST PRACTICES
24.4.1 The Onion Test Type layer
24.4.2 Deployment Pipeline
24.4.3 Commit phase
24.4.4 Acceptance phase
24.4.5 Capacity phase
24.4.6 Manual testing
24.4.7 Production testing
25 TEST PATTERNS (#24)
25.1 INTRODUCTION
25.2 TERMS
25.3 CONCEPTS
25.4 BEST PRACTICES
25.4.1 Pattern maturity
25.4.2 Pattern language
26 DEPLOYMENT PIPELINE (#25)
26.1 INTRODUCTION
26.2 TERMS
26.3 CONCEPTS
26.4 BEST PRACTICES
26.4.1 Steps
XII DevOps Best Practices
27 FORWARD RELEASING (#26)
27.1 INTRODUCTION
27.2 TERMS
27.3 CONCEPTS
27.4 BEST PRACTICES
27.4.1 The train metaphor
27.4.2 How do the trains run?
27.4.3 What’s on the train?
28 SERVICE MODEL (#27)
28.1 INTRODUCTION
28.2 TERMS
28.3 CONCEPTS
28.4 BEST PRACTICES
28.4.1 Two types of services
28.4.2 Two type of products
29 TASK DEMARCATION (#28)
29.1 INTRODUCTION
29.2 DEFINITIONS
29.3 CONCEPTS
29.4 BEST PRACTICES
29.4.1 The OPS process
29.4.2 The OPS demarcation
30 CONTINUOUS MONITORING (#29)
30.1 INTRODUCTION
30.2 TERMS
30.3 CONCEPTS
30.4 BEST PRACTICES FOR DEVOPS RELEASE
30.4.1 Monitoring Best practices
30.4.2 Monitoring KPI’s per phase
30.4.3 Montoring Means
30.4.4 Monitor tools
31 THE BUSINESS CASE (#30)
31.1 INTRODUCTION
31.2 TERMS
toelichtingIn recent years, many organisations have experienced the benefits of using Agile approaches such as Scrum and Kanban. The software is delivered faster whilst quality increases and costs decrease.

The fact that many organisations that applied the Agile approach did not take into account the traditional service management techniques, in terms of information management, application management and infrastructure management, is a major disadvantage.

The solutions to this problem has been found in the Dev (Development) Ops (Operations) approach. Both worlds are merged into one team, thus sharing the knowledge and skills.

This book is about sharing knowledge on how DevOps teams work together. For each aspect of the DevOps process best practices are given in 30 separate articles. The covered aspects are: Plan, Code, Build, Test, Release, Deploy, Operate and Monitor.

Each article starts with the definition of the specifically used terms and one or more concepts. The body of each article is kept simple, short en easy to read.

Meer boekennieuws op Facebook.

ingezonden mededeling: