A Seat at the Table: IT Leadership in the Age of Agility - Part 2appears to offer predictability, control, and efficiency, the key values of the contractor-control model. But it doesn’t. Requirements: Requirements are a way of controlling the development team by constraining Characteristics of an Agile governance and oversight model: Before we dive into an Agile governance and oversight model, let’s think about what characteristics such a model should have in order to both take advantage appropriate (what we are typically looking for is opportunity cost). We use a simple, one-page document we call the Financial Summary for this purpose. How to gauge plans: To gauge the plans for the0 码力 | 7 页 | 387.61 KB | 5 月前3
A Seat at the Table - IT Leadership in the Age of Agilitydecisions under uncertainty, and then have the courage to face the consequences. In the plan-driven model, quality was easier to understand. We specified what the system should do, and then measured quality that, either. We are constantly making quality decisions, especially in a Continuous Delivery model, as we decide whether the quality of each individual feature is adequate for the feature to be deployed that we have not yet learned to take advantage of, caught up as we are in the contractor-control model of IT. Shadow IT is what happens when the IT organization is unable to meet the needs of a part of0 码力 | 7 页 | 387.48 KB | 5 月前3
DoD CIO Enterprise DevSecOps Reference Design - Summaryemulation of common infrastructure components to achieve consistent and predictable resultConceptual Model DevSecOps LifecycleDevSecOps Pillars DevSecOps EcosystemDevSecOps Software Factory DevSecOps MVP correlated and centralized logs, container security, east/west traffic management, a zero-trust model, a whitelist, Role-Based Access Control (RBAC), continuous monitoring, signature-based continuous0 码力 | 8 页 | 3.38 MB | 5 月前3
The DevOps Handbooktypically structured as:1. Standardized Model – where routine and systems govern everything; including strict compliance with budget and schedule 2. Experimental Model – every day every exercise and new piece0 码力 | 9 页 | 25.13 KB | 5 月前3
The DevOps Handbookinto Our Daily Work a. INTRODUCTION i. Jez Humble, “The most inefficient way to test a business model or product idea is to build the complete product to see whether the predicted demand actually exists0 码力 | 8 页 | 24.02 KB | 5 月前3
The DevOps Handbookright” 2. Type 2 – System of Engagement – “Doing it fast” ii. DevOps helps reject the bi-modal IT model and lets you do both c. START WITH THE MOST SYMPATHETIC AND INNOVATION GROUPS i. Chrossing the Chasm0 码力 | 8 页 | 22.57 KB | 5 月前3
The DevOps Handbookthe first time we see how an application behaves in a production-like environment ii. Don’t just document the environment specifications 1. Create a common build mechanism to create it on demand 2. Codified0 码力 | 8 页 | 23.08 KB | 5 月前3
python3学习手册print(len(strb)) #结果是8 ★python3在将str="xxx"转换成3s时,会报错: struct.error: argument for 's' must be a bytes object 需要在传入的字符参数前加b import struct a=b'hello' b=b'world!' bytes=struct.pack('5s6s',a,b) 或者把str转为对应编码的bytes0 码力 | 213 页 | 3.53 MB | 1 年前3
共 8 条
- 1













