The DevOps Handbooklearning throughout the organization 2. Ch. 19 – Enable and Inject Learning into Daily Work a. Complex systems are impossible to predict for all outcomes i. Dr. Steven Spear - resilient organizations design of the tools that we gave them.” 2. Accidents are due to the inevitable design problems in complex systems that we build; they are system problems – not individual problems iii. Effective practices injection across critical systems ii. Simulate and rehearse accidents for practice 1. Schedule the event 2. Give teams time to prepare, make changes, and establish procedures 3. Execute iii. Expose latent0 码力 | 9 页 | 25.13 KB | 6 月前3
The DevOps HandbookThe Second Way: The Principles of Feedback 27 i. KEEP PUSHING QUALITY CLOSER TO THE SOURCE 1. In complex systems, adding more inspection steps and approval processes actually increases the likelihood of are written d. Pushing large batches of work to teams and special committees for approval and processing and then waiting for responses 3. Instead a. Use peer reviews of our proposed changes to gain organization iii. ENABLING ORGANIZATIONAL LEARNING AND A SAFETY CULTURE 1. When we work within a complex system, by definition it is impossible for us to perfectly predict all the outcomes for any action0 码力 | 8 页 | 22.57 KB | 6 月前3
The DevOps Handbookenvironments layer a. Events, logs, & metrics b. Common service to centralize, rotate, and delete 2. Event router responsible for storing our events and metrics a. Enables visualization, trending, alerting use other Blue- Green, Canary release patterns b. DEV SHARES PAGER ROTATION DUTIES WITH OPS i. Complex systems will inevitably have unexpected problems ii. Prevent upstream work from locally optimizing0 码力 | 8 页 | 24.02 KB | 6 月前3
Cynefin - Agile for DefenseComplicated Sense Analyze Respond Good Practice Rigid Constraints Governing Constraints Complex Probe Sense Respond Emergent Practice Enabling ConstraintsChaotic • No cause & effect relationship Complicated Sense Analyze Respond Good Practice Rigid Constraints Governing Constraints Complex Probe Sense Respond Emergent Practice Enabling Constraints Chaotic Act Sense Respond Complicated Sense Analyze Respond Good Practice Rigid Constraints Governing Constraints Complex Probe Sense Respond Emergent Practice Enabling Constraints Chaotic Act Sense Respond0 码力 | 17 页 | 3.75 MB | 6 月前3
MITRE Defense Agile Acquisition Guide - Mar 2014practices within each element of their programs, thus helping them to succeed in an increasingly complex environment. Agile has emerged as the leading industry software development methodology, and has challenges, but offers a set of principles that can help reduce cycle times and risks to deliver IT in a complex environment. “The US joint force will be smaller and leaner. But its great strength will be that recognize the potential of Agile methods, but don’t know how to apply Agile within the unique and complex DoD acquisition environment. This guide seeks to adapt proven principles of Agile development specifically0 码力 | 74 页 | 3.57 MB | 6 月前3
No Silver Bullet – Essence and Accident in Software Engineeringsimplicity.”Abstract “All software construction involves essential tasks, the fashioning of the complex conceptual structures that compose the abstract software entity, and accidental tasks, the representation complexity, conformity, changeability, and invisibility.”Complexity • Software entities are more complex for their size than perhaps any other human construct, because no two parts are alike • The complexity disasterConformity • Software people are not alone in facing complexity • Physics deals with terribly complex objects even at the fundamental level, but • Einstein argued there must simplified explanations,0 码力 | 35 页 | 1.43 MB | 6 月前3
A Seat at the Table - IT Leadership in the Age of Agilityrisk really the essence of what we do. Complex Adaptive Systems: Fourth and last, that the business should be thought of as a community, or perhaps as a Complex Adaptive System, which needs to be led0 码力 | 4 页 | 379.23 KB | 6 月前3
The DevOps Handbookearly as possible, in the fastest category as possible ii. Later stages require more scarce and complex environment to detect and reproduce issues iii. When an error is found, create a test in an earlier part of the deployment pipeline iii. Creating performance testing environments can easily be more complex than the application itself iv. Log performance results and evaluate compared to previous results0 码力 | 8 页 | 23.08 KB | 6 月前3
Agile Summit One-PagerExecute each PI • Measure progress biweekly via system demo • PI System Demo is the major contract event • Measure, evaluate, Inspect and Adapt • Increase, steady, ramp down? Dr. Mayner is also working0 码力 | 2 页 | 347.35 KB | 6 月前3
The Goal - A Process of Ongoing Improvementwith the hike and it causes him to realize something about his plant. ● Dependent events - an event, or series of events, must take place before another can begin ● Statistical fluctuations - most0 码力 | 6 页 | 100.81 KB | 6 月前3
共 10 条
- 1













