MITRE Defense Agile Acquisition Guide - Mar 2014practices within current policy by tailoring program processes and structure to deliver releases every 6–12 months. The DoD can apply Agile practices to the full range of IT product and service acquisitions ............................. 6 3 Deciding to Adopt an Agile Approach .............................................................................................. 6 4 Embracing the Agile Culture ............................................................................................. 10 6 Tailoring Program Structure and Processes for Agile Development ..................................0 码力 | 74 页 | 3.57 MB | 6 月前3
The DevOps HandbookThe DevOps Handbook – Parts 5 & 6 – Part 5: The Third Way – The Technical Practices of Continual Learning and Experimentation; 1. Introduction a. Goal – practices to enable learning as quickly, frequently responded to the problem 4. People who diagnosed the problem 5. People who were affected by the problem 6. Anyone else who is interested in attending the meeting iv. Guidance 1. Pull all factual evidence standards and tools, including security 4. Deployment pipeline tools 5. Monitoring and analysis tools 6. Tutorials and standards ii. Google – Single repository with over 1B files and over 2B SLOC, over 25K0 码力 | 9 页 | 25.13 KB | 6 月前3
Agile Summit One-PagerNDIA's Agile in Government Summit 6/6/2018-6/7/2018. Keynotes: Major General Sarah Zabel http://www.ndia.org/events/2018/6/6/agile-in-government/proceedings Agile and EVMS They Can Co-exist! ( per0 码力 | 2 页 | 347.35 KB | 6 月前3
My Take on Agile CoachingAgile for Defense Agile Coaching by Darin Plum Aug 6, 2014 1 My Take on Agile Coaching The core to all Agile is maximizing each individuals potential through autonomy and mastery Agile Coaching by Darin Plum Aug 6, 2014 2 Books 1. “Good Business” by Mihaly Csikszentmihalyi 2. “Drive” by Dan Pink (~11 minute video at https://www.youtube.com/watch?v=u6XAPnuFjJc) 3. “How to Win Conversations” by Patterson, Grenny, McMillan, and Switzler 5. “Coaching Agile Teams” by Lyssa Adkins 6. “Positive Intelligence” by Shirzad Chamine “Coaching Agile Teams” by Lyssa Adkins0 码力 | 2 页 | 417.28 KB | 6 月前3
The DevOps Handbookworking on now? f. What is your next step? g. What is your expected outcome? h. When can we check? 6. PART II—WHERE TO START 47 7. Ch. 5 Selecting Which Value Stream to Start With 51 a. GREENFIELD vs Any Leader needs to be brave enough to allocate teams to do some calcuated risk- taking.” 8. Ch. 6 Understanding the Work in Our Value Stream, Making it Visible, and Expanding it Across the Organization AGREE ON A SHARED GOAL i. Define a measurable goal with a clearly defined deadline approximately 6 months to 2 years out.e. KEEP OUR IMPROVEMENT PLANNING HORIZONS SHORT i. Act like a startup, strive0 码力 | 8 页 | 22.57 KB | 6 月前3
The DevOps HandbookEnvironment scripts & creation tools 3. DB scripts and reference data 4. Containers 5. Automated tests 6. Project artifacts – documentation, procedures, etc. 7. Application configuration files 8. This also middleware 4. Copying packages to production servers 5. Restarting VMs, containers, applications, etc. 6. Generating configuration files 7. Run automated smoke tests 8. Running test procedures 9. Scripting progressive rollouts 4. Eliminates big bang, have already evaluated for considerable time before releasing 6. Ch. 13 Architect for Low-Risk Releases a. Principle of Evolutionary Architecture – Jez Humble – “any0 码力 | 8 页 | 23.08 KB | 6 月前3
DoD CIO Enterprise DevSecOps Reference Design - Summarybehavior. 4. Vulnerability Management 5. A service mesh proxy to connect to the service mesh 6. Zero Trust down to the container level. Zero trust requires strict controls, never trust anything Runtime Behavior Analysis Artificial Intelligence (AI) service 5. DCAR for the hardened containers 6. Common Vulnerabilities and Exposures (CVE)Service / host-based security to provide CVEs for the security0 码力 | 8 页 | 3.38 MB | 6 月前3
The Goal - A Process of Ongoing Improvementyou think we can move through the line each time we go through the cycle? 3.5 is the average of the 6 numbers on the dice. Make it interesting. Let’s say that everyone has a quota of 3.5 matches per each of them deviates from the average. They all start at zero. If the roll of the die is a 4, 5, or 6 then record - respectively - a gain of .5, 1.5, or 2.5. And if the roll is a 1, 2, or 3, then record0 码力 | 6 页 | 100.81 KB | 6 月前3
The DevOps Handbookprivileged changes 4. Data changes (CRUD) 5. Invalid input, possible malicious injections or threats 6. Resources (RAM, disk, CPU, bandwidth, and others with hard or soft limits) 7. Health & availability metric improvement>. We WillHave Confidence To Proceed When6. Ch. 18 – Create Review and Coordination Process to Increase Quality of Our Current Work a. Goal – 0 码力 | 8 页 | 24.02 KB | 6 月前3
Velocity Conference 2015/public/schedule/proceedings [2] YouTube Playlist: https://www.youtube.com/playlist?list=PL055Epbe6d5Y86GSg3nhUH3o_v62FGpCI0 码力 | 4 页 | 176.79 KB | 6 月前3
共 11 条
- 1
- 2













