MITRE Defense Agile Acquisition Guide - Mar 2014integrated, tested, and demonstrated (aka: iteration) Daily Scrum - Team synchronization meeting to plan activities and assess progress and impediments3 A release comprises a series of sprints. As an example velocity: the number of story points the team can complete in a sprint. This enables the team to plan the amount of work to accomplish in the next sprint and continually measure its performance. Teams First, Agile requires dedicated government involvement throughout the entire process in order to plan and integrate multiple releases, oversee development cycles, manage evolving requirements, facilitate0 码力 | 74 页 | 3.57 MB | 5 月前3
A Seat at the Table - IT Leadership in the Age of Agilitymust become. Uncertainty and Risk: Third, underlying all of these changes – all of the problems with plan-drive approaches, all of the advantages of Agile approaches – is a confusion about how to deal with thinking simply says that we should empower small teams to inspect and adapt rather than stick to a plan. Lean thinking gives that small team ways to speed up its inspecting and adapting process to maximize should reject the plan-driven approach to IT is that it espouses all the wrong values. What is the value of rigidity and executing according to plan if you could be improving on the plan or responding0 码力 | 4 页 | 379.23 KB | 5 月前3
A Seat at the Table - IT Leadership in the Age of Agilityio/JeaO2 Risk The presence of uncertainty is the simple reason why Agile approaches work better than plan-driven approaches—it is also the reason why a good IT leader will often have to make “wrong” decisions uncertainty, your choices will often turn out to be wrong.Agile and plan-driven models have very different ways of dealing with uncertainty. Plan driven approaches, even Waterfall, have always acknowledged that eventuality whose impact required mitigation. The basic plan would remain valid, and the risk of the unexpected could be managed within the plan by itemizing potential risks, actively working to prevent0 码力 | 7 页 | 387.48 KB | 5 月前3
A Seat at the Table: IT Leadership in the Age of Agility - Part 2alongside you.” – Mark Schwartz Last Time in Part One Planning: The idea that we should make a plan and then stick to it is a terrible idea in an environment of uncertainty and change. It has dominated the features that have been deployed. we would carefully set boundaries for planning. A detailed plan is a less effective basis for governance than validated learning based on actual delivery. The more budget—I can decide whether the business case for the investment is still attractive. Often, the plan for the future is to continue exploring the ideas originally brainstormed in the impact map. That0 码力 | 7 页 | 387.61 KB | 5 月前3
Government Excerptstate does is make decisions. We want to find a way to leave less paper on a desk.”1 The governor’s plan has five points that could have been plucked from any campaign platform: 1. A “world-class”0 码力 | 3 页 | 414.99 KB | 5 月前3
Gluon DeploymentAffiliates. All rights reserved. Amazon Trademark 1. AWS has most TVM contributors from industry. 2. We plan to build TVM team in China, based in Shanghai, Beijing and Shenzhen. 1. Applied Scientist and SDE0 码力 | 8 页 | 16.18 MB | 5 月前3
TVM@Alibaba AI LabsKernel ALIOS TVM Alibaba Al.Labs 阿里巴巴人工智能实验室 7= 590一I) rm 一 下Er (mm) =肪+2mxaM0 [5 (全-2)+o| current plan 1 = int16 * int16 erflow-aware int16 = int8 xint8 ent pl 1=int8 int8 * int8 int32 = int16 1 +0 码力 | 12 页 | 1.94 MB | 5 月前3
DoD CIO Enterprise DevSecOps Reference Design - Summaryof DevSecOps is to automate, monitor, and apply security at all phases of the software lifecycle: plan, develop, build, test, release, deliver, deploy, operate, and monitor. In DevSecOps, testing and security0 码力 | 8 页 | 3.38 MB | 5 月前3
The Goal - A Process of Ongoing ImprovementTesting before Manual Testing & QA Time and Batch sizes From the moment material comes into the plan to the minute it goes out the door as part of a finished product, you can divide that time into four0 码力 | 6 页 | 100.81 KB | 5 月前3
The DevOps Handbookinfrastructure and services for items that are causing disproportionate amounts of failure and unplanned work; plan for elimination or replacement iii. Create “buoys, not boundaries”; navigate the channel, mark the0 码力 | 9 页 | 25.13 KB | 5 月前3
共 23 条
- 1
- 2
- 3













