A Seat at the Table: IT Leadership in the Age of Agility - Part 2IT capabilities together, we arrive at an asset that enables the enterprise to earn future revenues and reduce future costs—that is, an asset in the classic economic sense. This asset I will refer to as direction you choose. That is its latent value; the inverse of the cost of implementing changes in the future. What does such an EA, brimming with latent value, look like? It has little technical debt. risk of buying a vendor’s product, where the investment is one large lump sum—and a commitment to future maintenance payments. Then, of course, there is the risk of the vendor going out of business or0 码力 | 7 页 | 387.61 KB | 6 月前3
A Seat at the Table - IT Leadership in the Age of Agility(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 IT capabilities were delivered as dealing with uncertainty. Plan driven approaches, even Waterfall, have always acknowledged that the future is uncertain. But this uncertainty was treated as a potential aberrance—a risk or eventuality whose failure modes is high. In weighing the things known for certain against the uncertainties of the future, we are sure to find that the uncertainties dwarf the certainties, and that the uncertainties are0 码力 | 7 页 | 387.48 KB | 6 月前3
python3学习手册若要在py2中也使用py3中的这些特性,可以导入名为 __future__ 的 包,导入后,py2会启导入的功能使得也支持py3的这些特性。同时py2 的这些原有特性会被py3覆盖 让源代码兼容python2和python3,只需要在代码开头添加以下几行, 然后都用py3的语法去写代码: from __future__ import absolute_import from __future__ import division division from __future__ import print_function from __future__ import unicode_literals import sys if sys.version_info[0] < 3: reload(sys) sys.setdefaultencoding('utf-8') 解析: ★打印函数 导入print_fun (以下代码在py2与py3都可正常执行) from __future__ import print_function str_1 = "hello world" print(str_1) ★除法 division让python2也使用py3的除法规则(浮点数运算) (以下代码在py2与py3都可正常执行) from __future__ import division print('100 码力 | 213 页 | 3.53 MB | 1 年前3
The DevOps Handbookbe the experts who educate the rest of the organization on how not to make the mistakes in the future 4. Accept that there is always a discretionary space where humans can decide to take action or lies in hindsight 5. Propose countermeasures to prevent a similar accident from happening in the future and ensure these countermeasures are recorded with ta target date and an owner for follow-up. iii0 码力 | 9 页 | 25.13 KB | 6 月前3
Open Discussion on Project Planningreleases. DON’T make detailed plans beyond a program’s ability to control or accurately predict future circumstances o Agile methodology does not force programs to establish their full scope, requirements0 码力 | 2 页 | 49.30 KB | 6 月前3
The Phoenix Projectcall from the CEO. The company's new IT initiative, code named Phoenix Project, is critical to the future of Parts Unlimited, but the project is massively over budget and very late. The CEO wants Bill to0 码力 | 3 页 | 154.45 KB | 6 月前3
The DevOps HandbookPrevents creation of institutional knowledge about incidents and learning needed to prevent them in the future ii. Use for fact-based problem-solving e. ENABLE CREATION OF PRODUCTION METRICS AS PART OF DAILY0 码力 | 8 页 | 24.02 KB | 6 月前3
The DevOps Handbooksystems, adding more inspection steps and approval processes actually increases the likelihood of future failures. The effectiveness of approval processes decreases as we push decision-making further0 码力 | 8 页 | 22.57 KB | 6 月前3
The DevOps HandbookWorst effect – lose the ability to learn from mistakes and diminish integrating that learning into future work d. Google Web Server (GWS) team was struggling with changes – Hard line: no changes would0 码力 | 8 页 | 23.08 KB | 6 月前3
共 9 条
- 1













