technologies and operations, including the challenges associated with information assurance. Agile development practices can help the DoD to transform IT acquisition by delivering capabilities faster and responding in an increasingly complex environment. Agile has emerged as the leading industry software development methodology, and has seen growing adoption across the DoD and other federal agencies. Agile practices tailoring program structures and acquisition processes to the program characteristics. Agile development can achieve these objectives through:  Focusing on small, frequent capability releases 

autonomous robotic vacuum cleaner that can navigate homes, is launched 10/05: A Stanford team build a driverless car named Stanley; it completes a 132-mile course, winning the DARPA AI Will Likely Do in Ten Years, per ChatGPT Source: ChatGPT (5/15/25) AI = Circa 2035?36 AI Development Trending = Unprecedented37 Machine-Learning Model* Trending = In 2015... Industry Surpassed Academia Models by Sector – 2003-2024, per Stanford HAI Annual New Notable Machine-Learning Models AI Development Trending = Unprecedented38 AI Developer Growth (NVIDIA Ecosystem as Proxy) = +6x to 6MM Developers

that 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 and when we realize that the costs and risks of custom development have been radically reduced, the economics often now favor custom development. Governance and Oversight: Governance has traditionally from strategic objectives and produce investment themes that accomplish those objectives. When combined with Agile and Lean practices, this approach can focus IT planning, reduce risk, eliminate waste

feasible.  History – How I Got Here?  Contentious relationship existed between development and operations.  Left development because I was frustrated that it took so much time to get my products into production teams involved in snowflake environment support.  The practice team wasn’t the same as the game time team.  Segregated technical and business functions  Development  Operations (Operational Waterfall) product team wherever possible. Control our destiny  Started to engineer solutions for issues related to product configuration and deployment  Built a strong relationship with development (built empathy)

gives that small team ways to speed up its inspecting and adapting process to maximize its impact. Continuous Delivery and DevOps place the entire value stream in the hands of that small team so that it can art in lean thinking – and be empowered as a team to own the entire value delivery process. Brining Lean Principles to Software Development: Kanban is David Anderson’s approach to bringing bringing Lean principles into software development while driving fear out of the transformation process through incremental change. Anderson provides four rules for implementing Kanban: 1. Start with existing

approach: iterative development OpenAI is organized around three teams. Our Research Team advances the foundations of AI, developing new models and capabilities. Our Applied Team turns those models models into products, like ChatGPT Enterprise and our API. And our Deployment Team takes these products into companies to address their most pressing use cases. We use iterative deployment to learn quickly are best-placed to improve 
 it with AI. 06 Unblock your
 developers Automating the software development lifecycle can multiply 
 AI dividends. 07 Set bold 
 automation goals Most processes involve

TVM community and contribute new infrastructure and features. octom|.ai @octoml Q octoML Founding Team - The Octonauts - 四人全外日 Luis Ceze Jason Knight Tianqi Previouslr 1BM Research consuling Nenana Intel orMicrosof Apple Qualcomm 40+ years of combined experience in computer systems design and machine learning tr tvm 。 @zxnet 和os 全 Infrastructure Improvements to TVM o_uTVM: support for microcontrollers in TVM o_ Virtual Machine and dynamic NNs support (w/ AWS folks) o_ Improved NLP support, with focus on transformers QQ octoML Core

production instances v. Keep developers’ environments most current e. MODIFY OUR DEFINITION OF DEVELOPMENT “DONE” TO INCLUDE RUNNNING IN PRODUCTION-LIKE ENVIRONMENTS i. In general, the longer the interval Google Web Server (GWS) team was struggling with changes – Hard line: no changes would be accepted into GWS without accompanying automated tests. Spread Testing Grouplet team approach. Google – single 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

Requirements are a way of controlling the development team by constraining their creativity. Instead of requirements, we want to charge the team—the joint business/IT team, that is— with delivering business changes to the whole ball of EA.  It has a robust, automated regression test suite, so that new development does not cause expensive break-fix activity.  It has good monitoring tools in place.  It is it. This obvious fact is neat, plausible, and in most cases, wrong. The economics of software development have changed: Changed in a way that now favors “building” over “buying.” There are now ways of

INFRASTRUCTURE i. Remove the silos of information – Developers don’t just log what’s interesting to development. Operations don’t just monitor what’s up or down. ii. Modern Monitoring architecture 1. Data everyone in the value stream iii. Promotes responsibility 1. The team has nothing to hide from its visitors (customers, stakeholders)2. The team has nothing to hide from itself: it acknowledges and confronts iii. More exotic - Fast Fourier Transforms or Kolmogorov-Smirnov 4. Ch. 16 – Enable Feedback So Development and Operation Can Safely Deploy Code a. USE TELEMETRY TO MAKE DEPLOYMENTS SAFER i. Actively monitor