DevOps Meetupover there fix “their” problems. Discovered, multiple teams involved in snowflake environment support. The practice team wasn’t the same as the game time team. Segregated technical and business are cross-trained on each other’s concerns – empathy Combined the development support team with the production support team. Operations becomes familiar with new features in QA, rather than in front issues. Maintenance window changed from once a week to everyday Expanded Sphere of Influence Machine Imaging DEG and 3rd Party Application Installations Route Adds – requires heightened security0 码力 | 2 页 | 246.04 KB | 5 月前3
The DevOps Handbookindependent of developers 2. Segregated processes so we know the dependencies – eliminates “worked on my machine” 3. Package the application to enable repeatable installation and configuration into an environment Captures the history of events for a build, test results, environments deployed to, etc. a. Use to support audits and compliance iv. Create out continuous integration practices 1. Comprehensive and reliable 2. Wrap UI or application logic in conditional statements or strategy patterns 3. Support easy roll back 4. Support graceful performance degradation 5. Increase resilience through SOA ii. Perform Dark0 码力 | 8 页 | 23.08 KB | 5 月前3
No Silver Bullet – Essence and Accident in Software Engineeringrepresentation of the abstract entities in programming languages and the mapping of these onto machine languages within space and speed constraints.”Abstract “Most of the big gains in software productivity inordinately hard, such as severe hardware constraints, awkward programming languages, lack of machine time. How much of what software engineers now do is still devoted to the accidental, as opposed survives beyond the normal life of the machine for which it is first written • Software is embedded in a cultural matrix of applications, users, laws, and machine vehiclesInvisibility • Software is invisible0 码力 | 35 页 | 1.43 MB | 5 月前3
The Goal - A Process of Ongoing Improvementcapacity of the plant is to increase the capacity of only the bottleneck. Story - NCX-10 n/c machine idle on lunch break, pile of inventory in front of heat treat Jonah: “Whatever is available, the world’. What is the process? STEP 1 IDENTIFY the systems’ constraint (bottleneck at the NCX10 machine) STEP 2 Decide how to EXPLOIT the constraint (Machines should not take lunch breaks) STEP0 码力 | 6 页 | 100.81 KB | 5 月前3
MITRE Defense Agile Acquisition Guide - Mar 2014growing number of programs continue to chart new paths in this field. This guide is intended to support that growth, as well as to capture the best practices and lessons learned by these early Agile adopters execution will take time, trial and error, and shaping of processes, policies, and culture, but with support from oversight and process owners can reach the full potential of Agile development. Agile Acquisition prescribed processes, but is designed to allow dynamic, tailored, and rapidly evolving approaches to support each organization’s IT environment. “You never know less than on the day you begin your new project0 码力 | 74 页 | 3.57 MB | 5 月前3
Agile Summit One-PagerRelease/Program Increment Planning. Scenario describes one method of how Agile can underpin EVM progress in support of tracking program cost and schedule status and metrics • The scenario is a generic SW program structures (standard C, IDIQ, BPA, GWAC, set-aside, etc.) can support Lean-Agile contracts All types (FFP, T&M, CPFF, CPAF, etc.) can support Lean-Agile contracts ...In exercising initiative, Government0 码力 | 2 页 | 347.35 KB | 5 月前3
A Seat at the Table - IT Leadership in the Age of Agilitythat has functional capabilities (how it is used today) but also latent capabilities (how it will support future agility and how it will offer options in the future). Build Versus Buy: In a world where simply an efficient process we use to select among alternatives. Shadow IT Agile ways of working support a community approach to IT, where IT leaders achieve their objectives by mobilizing the skills and they have to be? If everyone is really becoming more tech savvy, might it not be a better idea to support and encourage rogue development? Impediment Remover: The leadership model that seems to work best0 码力 | 7 页 | 387.48 KB | 5 月前3
Spreadsheet Analysis using Atlassian Toolscontrol tasks. As a distributed revision control system it is aimed at speed, data integrity, and support for distributed, non-linear workflows https://try.github.io/levels/1/challenges/1 https://www0 码力 | 1 页 | 120.37 KB | 5 月前3
Velocity Conference 2015man in the middle for your page, hence HTTPS only Most benefit for single page apps for offline support Putting Performance Best Practices Together to Create the Perfect SPA by Chris Love (Love2Dev) @ChrisLove0 码力 | 4 页 | 176.79 KB | 5 月前3
DoD CIO Enterprise DevSecOps Reference Design - Summaryidentities per Pod using certificates, and whitelisting rather than blacklisting. Services that support the security sidecar include: 1. Program-specific Log Storage and Retrieval Service 2. Service0 码力 | 8 页 | 3.38 MB | 5 月前3
共 14 条
- 1
- 2
相关搜索词
DevOpsMeetupTheHandbookNoSilverBulletEssenceandAccidentinSoftwareEngineeringGoalProcessofOngoingImprovementMITREDefenseAgileAcquisitionGuideMar2014SummitOnePagerSeatattheTableITLeadershipAgeAgilitySpreadsheetAnalysisusingAtlassianToolsVelocityConference2015DoDCIOEnterpriseDevSecOpsReferenceDesignSummary













