Agile Development Study Notes

First, the view

1. Plan is not to limit change, but to adapt to change.
   Plan itself is "management unit", the ability to adapt to change plans from the plan itself to narrow the "granularity" of.
2. Software development is a complex process
   do not try to deal with complex processes with complex methods, attempts to simplify the complex process into a simple process, then the simplest way to handle simple process.

   Here reminds me of the builder pattern, it is the core of the complex process of decomposition, and then by a simple process, the formation of a complete complex processes.

3. Property management and point of convergence of engineering properties, is the version management
   version management is to let anyone in R & D can be used in a simple language to describe what we are doing, what has been done, how many do.
4. Many industries who need the most agile and DevOps strongly dependent on IT non-IT industry?
   Financial sector business people never feel that they are doing the IT; financial corporate IT staff never feel that they are doing finance.
5. Brain agile provide innovative, DevOps provide innovative muscle
6. Research and development to enhance the effectiveness of the two major magic

• Management granularity
  optimize the management of the angle is always in particle size by controlling the "snap-in" to complete. The so-called "snap-in" may be a team, requirements, tasks, test, deliver a managed object of any research material and the like.
• Improve performance
  whether it is agile, lean or continuous delivery, its ultimate goal is to improve performance. The so-called "performance" is continuing to adapt its capacity and speed of the output value adjusted for changes in the market.
• Decoupling engineering
  optimization techniques angle is always achieved by releasing the coupling between the "engineering objects." The so-called "engineering object" may be systems, tools, code, modules, services, platforms, or any present or cloud delivered in the development process "technology object."

7. Forget Agile and DevOps, remember "performance"
   so-called "performance": that is continuing to adapt to market changes, to adjust the value of their output capacity and speed.
8. Signal cards, kanban
   signal card from the earliest sources of fine art manufacturing, first appeared in the Toyota production system (Toyota Production System, TPS). Goals: 1, the highest quality; 2, the lowest cost; 3, the minimum lead time.
   Lean manufacturing system to form a "pull system", bringing control of inventory, speed up circulation, and promote the improvement of flexible response and other benefits through billboards, end-user value so that the smooth flow of high quality.
   Workers manufacturing companies to do the job is to "create" software development worker to do the job is "to create."

Second, the tool

1, Docker

2, vessel scheduling system
supports deployment to different environments (public cloud, private cloud, independent data centers, virtual machines and physical machines)
four orchestration platform:

• Apache Mesos & Marathon (DC/OS)
• Google Kubernetes (k8s)
• Docker swarm(Docker datacenter)
• Azure Service Fabric in the Microsoft
  
  3, CI / CD line
  CI / CD line, which represents the continuous integration CI (Continuous Integration), CD represents the continuous delivery (Continuous Delivery) and continuous deployment (Continuous Deployment).
  

Reference document: "How to start from scratch to build a CI / CD line"

4, Git code management
feature branch management.

Disclaimer: This article is finishing study notes, the contents of the source Xu Lei teacher-site lectures.