Executive and leadership
How the field of a Chief Technology Officer got here: the sourced milestones from every published course of this career, on one axis.
1917 to 2025
265 milestones across 28 courses
The axis stretches toward recent years, where most milestones fall. Bars count milestones per year; dots are single milestones.
29 milestones
1917
The United States Army introduced group-administered mental tests to screen roughly 1.75 million First World War recruits. Large-scale standardized selection dates from this program, and so does the criticism that followed it.
1947 Jun
Kurt Lewin's paper examined social equilibria and social change. Its field-theory framing became an early foundation for planned-change work.
1950
The Act required Federal agencies to establish appraisal systems and used three summary levels. It made formal appraisal a defined personnel process rather than an informal supervisor practice.
1954
Peter Drucker's Management by Objectives established a results-oriented precursor that later influenced Andy Grove's approach at Intel.
1958
The Act provided training to improve performance and prepare employees for advancement. It made development an explicit companion to appraisal in the Federal system.
1962
The Act required an acceptable-level-of-competence determination for within-grade increases and allowed additional increases for high-quality performance. It linked appraisal outcomes to pay decisions.
1964 Jul 2
Title VII prohibited employment discrimination based on race, color, religion, sex, and national origin and created the EEOC. Recruitment and hiring became explicit parts of federal equal employment enforcement.
1964 Jul 2
The Civil Rights Act of 1964 prohibited employment decisions based on race, color, religion, sex, or national origin. Every later selection procedure in United States practice operates under this constraint, including the requirement that assessments be job-related.
1967
The ADEA prohibited covered employment discrimination against older workers. Hiring criteria and selection procedures therefore had to account for age discrimination as well as Title VII protections.
1968 Apr
Melvin Conway published “How Do Committees Invent?”, arguing that a system design reflects the communication structure of the organization that produces it. Communication paths became a technical design concern.
1971 Mar 8
The Supreme Court held that facially neutral practices such as tests and diploma requirements are unlawful under Title VII when they freeze the status of a protected group, unless the employer shows the practice is job-related. Job-relatedness became the burden of the employer, not a courtesy.
1972
Congress gave the EEOC authority to sue private employers and extended Title VII across the federal government and qualifying state and local agencies. Enforcement became a stronger operational constraint on recruiting and selection.
1972 Dec
Parnas described decomposing modules around design decisions likely to change. The idea made change isolation a concrete architectural concern.
1973
Section 501 prohibited federal-government discrimination against qualified people with disabilities. Disability access and job qualification became linked concerns in covered hiring.
1978
Agencies had to develop appraisal systems based on job-related performance standards and encourage employee participation in setting those standards. Appraisal results became inputs to training, rewards, promotion, retention, and removal decisions.
1978
Congress clarified that discrimination based on pregnancy, childbirth, or related medical conditions is sex discrimination. Hiring practices could not treat pregnancy as a disqualifying proxy.
1978 Aug 25
Federal agencies adopted common guidance for evaluating adverse impact and validating employee selection procedures. Employers gained a formal framework for connecting tests and screens to jobs.
1978 Aug 25
The EEOC, Civil Service Commission, Department of Labor, and Department of Justice jointly adopted the Uniform Guidelines, codifying validation strategy, adverse-impact analysis, and the four-fifths rule of thumb. They remain the operative federal framework for evaluating selection procedures.
1979 Nov
Intel used a company-wide objective and measurable design-win results to coordinate its response to microprocessor competition without changing the product itself.
1981
NIST published Guidelines for ADP Contingency Planning, establishing federal guidance for planning recovery of automated data processing capabilities.
1982
NIST published SP 500-85 to give managers an executive guide to automatic data processing contingency planning.
1984
The system introduced five summary rating levels and required joint participation in setting standards for covered supervisors and managers. The rules explicitly prohibited forced rating distributions.
1985
NIST published SP 500-134 on selecting automatic data processing backup process alternatives, adding strategy selection to the contingency-planning record.
1986 Jan
Takeuchi and Nonaka described self-organizing project teams and overlapping development phases as an alternative to sequential product development. Their rugby metaphor later influenced Scrum.
1987
Willyard and McClees published the first journal paper on technology roadmapping, making Motorola's product-technology approach visible beyond the company.
1987
Zachman's framework organized architecture descriptions by perspectives and interrogatives. It established the need for coordinated enterprise views.
1989
The first ITIL publication began a shared body of guidance for managing IT services. Later editions expanded from process guidance toward integrated product and service value systems.
1989 Jul
Kodak assigned data-center, telecommunications, and desktop responsibilities to several providers. The arrangement became a prominent example of outsourcing as a strategic operating-model choice.
1989 Sep
Fred Davis published measures for perceived usefulness and perceived ease of use as determinants associated with information-technology acceptance.
26 milestones
1990 Jul
Michael Hammer argued that organizations should redesign obsolete work rather than use information technology to accelerate it. This established an early distinction between process transformation and technology installation.
1990 Jul 26
The ADA extended employment protections for qualified people with disabilities in covered private, state, and local employment. Application access, inquiries, tests, and accommodation became core hiring-process concerns.
1991
The Civil Rights Act of 1991 added jury-trial rights and damages in specified intentional discrimination cases. Documented, job-related hiring decisions carried greater practical importance.
1991
A United States workshop brought industry, universities, government agencies, consortia, and laboratories together to chart semiconductor technology needs.
1992
Industry coordination produced a public sector-level roadmap that established shared technology targets beyond one company.
1992
Work on architectural styles and abstractions separated system-level structure from individual program modules. Architecture became a subject that could be described and analyzed directly.
1992 Jan
Kaplan and Norton presented a framework that balanced financial measures with customer, internal-process, and learning perspectives. Executive reporting gained a broader structure than financial results alone.
1994
The SEI introduction presented architectural representations and styles for reasoning about complex systems. It gave practitioners vocabulary beyond implementation diagrams.
1994 Apr
The Agreement established international rules for covered government procurement. It made procurement transparency and non-discrimination part of a multilateral framework.
1995
Revised regulations allowed agencies to develop programs for their own needs and cultures, with two to five summary levels. The change moved away from one uniform operating design.
1995
NIST published a general computer security handbook. It provided a public foundation before later risk-specific guidance.
1995
The Open Group published the first TOGAF version, built on the US Department of Defense TAFIM methodology, as a technical architecture framework.
1995 May
Harvard Business Review published Leading Change — Why Transformation Efforts Fail, organizing recurring failures observed across major change efforts.
1995 Oct
Ken Schwaber and Jeff Sutherland presented Scrum as a team-based process for complex software development. It formalized a cohesive unit around iterative delivery and shared accountability.
1996
COBIT began as control objectives for IT auditors. Its later editions expanded into a framework for governance and management of enterprise information and technology.
1996
John Kotter's book presented an eight-stage approach for leading organizational transformation and sustaining changed behavior.
1996
NIST published generally accepted principles and practices for securing information technology systems. Security practice gained defined management expectations.
1996
Jeff Hiatt developed ADKAR as an individual-change model. Prosci later used it to diagnose awareness, desire, knowledge, ability, and reinforcement.
1996
An SEI report describes a tool embodying the Software Architecture Analysis Method and preserving scenarios and design rationale while exploring alternatives.
1997
EIRMA documented a multilayer framework spanning external influences, deliverables, technologies, know-how, and resources, with time as the defining parameter.
1997
Philips published a product-technology structure that considered markets, products, and technologies together over time.
1998
The meta-analysis "The validity and utility of selection methods in personnel psychology" tabled validity coefficients for common selection methods and ranked cognitive ability tests at .51 and structured interviews at .51. For two decades it anchored advice about which assessments carry predictive weight.
1998 Jul
The SEI publishes the Architecture Tradeoff Analysis Method for evaluating how candidate architectures satisfy interacting quality attributes and for identifying risks.
1999
FEAF gave US federal agencies a common construct for architecture descriptions across business, data, applications, and technology.
1999
John Doerr introduced OKRs to Google's founders, extending the method from Intel into a growing software company.
1999
Five regional trade organizations cooperated on the first international semiconductor roadmap and a recurring global planning process.
47 milestones
2000 Sep
IEEE 1471 defined architecture description around stakeholders, concerns, viewpoints, and views. It made the audience and purpose of a representation explicit.
2001
T-Plan packaged a fast-start workshop method for linking market, product, and technology views into a first roadmap.
2001
NIST published a questionnaire-based self-assessment guide. Assessment became a repeatable control-management activity.
2001
TOGAF 7, the Technical Edition, narrowed the framework toward technical architecture before the broader enterprise scope arrived with version 8.
2001 Feb
Seventeen practitioners published values favoring individuals, working software, customer collaboration, and response to change. These values challenged heavyweight, plan-driven delivery models.
2001 Feb
Seventeen practitioners produced the Manifesto for Agile Software Development. Its principles emphasized daily business-developer work, motivated individuals, self-organizing teams, and regular adaptation.
2001 Feb
The Agile Manifesto placed people and collaboration alongside working software as software-delivery values. It established a widely used foundation for treating team conditions as part of delivery practice.
2001 Feb
The manifesto formalized an adaptive software-development movement that valued responding to change, shaping the environment in which living roadmaps replaced fixed long-range plans.
2001 Feb
Seventeen practitioners published values favoring working software, customer collaboration, interactions, and response to change. Iterative learning became a documented alternative to heavyweight delivery plans.
2002
The Act required standards and metrics for assessing human-capital management and created the Chief Human Capital Officers Council. Performance systems became part of a broader accountability framework.
2002
NIST published a risk-management guide for information technology systems. It described assessment methods and control-selection recommendations.
2002
TOGAF 8 expanded the framework from technical architecture to enterprise architecture, the scope the ADM still organizes today.
2002
TOGAF Version 8 applied its development method to business, data, application, and technical architecture.
2002 Jun
The guide defined a seven-step information-technology contingency planning process that joined impact analysis, preventive controls, strategies, plan development, exercises, and maintenance.
2002 Jul
NIST documented a risk-management process for identifying, assessing, mitigating, and continually evaluating information-technology risk.
2003
Tableau commercialized a visual query approach developed at Stanford. Interactive visual analysis became more accessible to business users.
2003
An updated 8.1 release corrected and clarified the version 8 enterprise-architecture material.
2003 Sep
Venkatesh and co-authors compared eight prominent acceptance models and formulated a unified view of technology acceptance and use.
2004
Motorola reported work toward a common process, software solution, and information architecture for roadmapping across the enterprise.
2004
NIST published guidance using risk and control assessments to inform a senior official's approval of a system's security posture.
2004 Mar
Directive 2004/18/EC consolidated rules for public works, supply, and service contracts. It gave European public buyers a common procedural baseline.
2005
US federal guidance defined strategic sourcing around analyzing spend and using the evidence to make acquisition decisions more effectively.
2005
ISO published the first ISO/IEC 27001 edition, establishing an information security management system standard. It made risk-based management and continual improvement a formal management-system path for information security.
2005
NIST published a control catalog with low, moderate, and high baselines. Teams gained a starting point adjustable for system-specific risk.
2005
A construction-informatics study reports retrospective case studies of tracking decisions during architectural design, treating decision history as an explicit concern.
2005 Dec
The first international ISO/IEC 20000 specification defined requirements for an integrated service management system and managed service delivery.
2006
Prosci published ADKAR — A Model for Change in Business, Government and Our Community, making the individual-outcome model available in book form.
2006
Stephen Few's book formalized dashboard design around rapid monitoring and effective visual communication. It gave practitioners a focused reference for reducing clutter and strengthening comparisons.
2006
NIST published Information Security Handbook: A Guide for Managers. It connected information-security program governance with management roles, controls, and performance measures.
2006
The Open Group released TOGAF 8.1.1 as the consolidated 8.x edition, around which TOGAF became a registered trademark of The Open Group.
2006 Mar
API-accessed storage made externally operated infrastructure available as a metered service, adding a standardized product model to technology sourcing choices.
2006 May
ISO/IEC 19770-1 established a standards-based process framework for software asset management. License controls gained a defined organizational process context beyond isolated inventory reports.
2006 Aug
Amazon announced on-demand compute capacity through a web service. Infrastructure could increasingly be provisioned as a variable service rather than only through owned data-center investment.
2006 Sep
The publication organized test, training, and exercise programs so plans and capabilities could be verified and improved through recorded evidence.
2007
ISO/IEC 42010 carried the architecture-description concepts into an international standard. Teams could use a common framework for organizing views around concerns.
2007
NIST issued the final update to SP 800-100. Its handbook framing kept governance and management distinct from operational security work.
2007 Jan
Apple combined a phone, internet communications, and a touch interface in one device. Mobile access raised expectations for integrated digital products and services across channels.
2008
NIST published guidance for assessment plans and procedures. Controls could be tested for operating as intended rather than assumed from their existence.
2008 Sep 25
The amendments broadened how disability is interpreted and took effect in 2009. Covered hiring processes had to apply the expanded definition when handling applicants and accommodation.
2008 Dec 11
WCAG 2.0 established durable web accessibility requirements that also apply to browser-delivered reports, controls, charts, and status cues.
2009
The first devopsdays brought together software-development and operations communities. The event series made cross-functional delivery and operations a shared professional conversation.
2009
Revised regulations required supervisor and manager training on mentoring, improving employee performance, conducting appraisals, and assisting employees with unacceptable performance.
2009
TOGAF 9 added a formal Content Metamodel linking ADM artifacts, an architecture repository, and the Enterprise Continuum, moving the framework from guidance toward a structured method.
2009
TOGAF Version 9 became the certification baseline for the 9.x line and its later revisions.
2009 Feb
ArchiMate 1.0 made a shared notation for describing and analyzing enterprise architecture available as an Open Group standard.
2009 Oct
The first Devopsdays brought development and operations concerns into one practitioner forum. It marked the spread of an operating approach centered on collaboration and delivery flow.
2009 Nov
ISO/IEC 19770-2 defined machine-readable software identification tags. It standardized an inventory input while explicitly leaving entitlement reconciliation to other processes.
92 milestones
2010
The context, container, component, and class diagram types were named. The set gave software teams a compact hierarchy for explaining structure at different zoom levels.
2010
NASA identified fourteen space technology areas, technical challenges, and relevant missions as the basis for agency roadmaps.
2010
NIST expanded certification and accreditation into the Risk Management Framework. Risk management was described as a system life-cycle process.
2010 May
The revision updated contingency planning for federal information systems and supplied impact-analysis and plan templates for different impact levels.
2011
The GEAR model connected organizational alignment, accountability, engagement, and results. It recommended linking employee performance management to organizational performance management.
2011
The German initiative connected digital networks, cyber-physical systems, and production. Digital transformation leadership expanded beyond online channels into operating technology and industrial processes.
2011
NIST published continuous-monitoring guidance. Monitoring became an ongoing activity rather than a point-in-time check.
2011
NIST published guidance for organization, mission, and information-system risk. Local assessments became connected to wider governance.
2011
The C4 name made the four-level diagramming approach identifiable and teachable. It emphasized communicating a software system with a small, consistent set of views.
2011
The 9.1 revision corrected and consolidated the version 9 material and became the long-stable edition many certified tools and courses targeted.
2011
The Open Group records Version 9.1 as the 2011 revision to the established TOGAF method.
2011 Feb
Volunteers formally incorporated the Association of Change Management Professionals, establishing a professional body for the discipline.
2011 Mar
The strategy set a central direction for government ICT and its implementation over the following two years. It made technology purchasing and reuse a cross-government management concern.
2011 Oct
The strategy treated on-demand cloud resources as a route to a more flexible and cost-effective public-sector technology estate.
2011 Nov
The joint revision superseded IEEE 1471 and ISO/IEC 42010:2007. It continued the stakeholder, concern, viewpoint, and view model for systems and software architecture.
2011 Nov
Documenting Architecture Decisions presents short, modular decision records as a practical way to retain context in agile software projects.
2012
COBIT 5 consolidated governance guidance and linked enterprise and IT strategy through a comprehensive set of practices, tools, and models.
2012
Fagerholm and Münch described developer experience as developers thoughts and feelings about work in their project environment. The publication made the human experience of development an explicit software-engineering topic.
2012
Janna Bastow and Simon Cast created the format to organize product direction by confidence horizons instead of fixed feature dates.
2012 Jan
ArchiMate 2.0 added a more closely aligned language for integrated enterprise models, including motivation and migration paths.
2012 Feb
The framework introduced an online route for public-sector organizations to buy commodity IT services. Shorter, catalog-based cloud purchases changed the supplier arrangements contract managers had to operate.
2012 Feb
G-Cloud created a route for public bodies to buy cloud services. It shifted attention toward reusable frameworks and digital service marketplaces.
2012 Apr
NASA published the completed roadmaps and related Technology Area Breakdown Structures for its space technology areas.
2012 May 22
Etsy publicly described blameless postmortems as a way for engineers to provide actions, observations, expectations, assumptions, and timelines without fear of punishment. The publication made contextual accounts a visible engineering practice.
2012 Jun
The second edition of ISO/IEC 19770-1 divided the integrated SAM baseline into tiers. Organizations could assess and implement license-management capability incrementally across platforms.
2012 Sep
The revision organized risk assessment into preparation, conduct, and maintenance, reinforcing assessment as an ongoing input to risk-management decisions.
2012 Oct
Henrik Kniberg and Anders Ivarsson documented Spotify's squads, tribes, chapters, and guilds as a snapshot of an evolving organization. The vocabulary made product-team and functional overlays widely visible.
2013 Feb
The order directed development of a voluntary, risk-based framework for critical infrastructure cybersecurity. It created the policy origin for the NIST Cybersecurity Framework.
2013 May
Central-government technology decisions gained a default preference for public cloud, with departures requiring evidence and a value-for-money case.
2013 Jul 8
Microsoft described browser and mobile access to reports built from Excel-based modeling and visualization components. Cloud distribution became part of the mainstream BI design path.
2014
DORA reports that it operationalized and validated Westrum's organizational-culture model in 2014. The model connected information flow, cooperation, trust, bridging, and inquiry to software-delivery research.
2014
Etsy's progress report recorded more than 100 postmortems in 2014, each using collective timeline reconstruction and remediation planning. It documented the practice as an organizational program rather than an isolated incident ritual.
2014
Google SRE records a 2014 internal presentation about high-impact incidents and postmortem practice. It shows postmortem discussion becoming part of a broader engineering learning culture.
2014
The 2014 State of DevOps research linked culture and delivery practices with IT and organizational performance. Organization design increasingly became an empirical delivery-capability question, not only a charting task.
2014
The 2014 report presented DevOps as a cultural as well as technical shift and reported links between its practices and IT performance. It made developer and organizational conditions part of delivery improvement work.
2014
The annual State of DevOps research published a report in partnership with Puppet. It established a recurring empirical reference for software-delivery measurement.
2014 Feb
NIST released CSF 1.0 with the Core, Tiers, Profiles, and five original Functions. These constructs gave organizations a common way to communicate cybersecurity outcomes and risk-management posture.
2014 Mar
The directive replaced the 2004 EU public-procurement directive. It updated the legal framework for public purchasing and procurement procedures.
2014 Apr
The revised Agreement entered into force for the parties that accepted it. It updated the international procurement framework and expanded its coverage.
2014 Jul
The recommendation framed digital government as strategic use of technology and data to create public value. It emphasized whole-of-government coordination rather than transferring analog processes to online channels.
2014 Sep
The Standard for Change Management documented method-neutral, generally accepted practices and supported a shared professional vocabulary.
2014 Nov
The international standard supplied a cross-sector outsourcing life cycle and governance framework covering strategy, selection, transition, value delivery, and exit.
2015
The DORA research history lists a 2015 report in the Puppet partnership series. Repeated reporting made delivery practices measurable across survey cohorts over time.
2015
AWS makes its workload guidance public, establishing a framework for comparing architecture choices against operational, security, reliability, performance, and cost concerns.
2015
The fourth level changed from classes to code during 2015–2016. The change avoided implying that every codebase should be explained through class diagrams.
2015
Scrum.org released Evidence-Based Management as a framework for measuring and improving value delivery under uncertainty.
2015
The Government Commercial Function brought commercial roles into a cross-government function. It established a central capability for commercial standards and improvement.
2015
NASA revised the roadmap scope and applied greater standardization after internal and external review.
2015 Feb
A UK government digital team documented a move away from a single large IT contract toward component suppliers, market engagement, and supplier trials. It made procurement design part of delivery transformation.
2015 Apr 7
Laszlo Bock's account of Google's People Operations described structured interviews, work-sample tests, and scorecard-based debriefs to a mass audience. Structured hiring shifted from industrial-organizational practice to mainstream engineering management advice.
2015 Jul 24
Microsoft released the redesigned service and Power BI Desktop for general use. Reports, dashboards, semantic models, and custom visuals formed a broadly available reporting stack.
2015 Aug
ISO/IEC 19770-5 supplied an overview, foundation principles, and consistent vocabulary for the standards family. License-management records could use shared definitions across processes and tools.
2015 Oct
The second edition of ISO/IEC 19770-2 clarified tag producers and consumers and refined software identification for management tools. It retained the boundary between identification and reconciliation.
2016
The DORA research history lists the 2016 report in the same series. The series continued collecting evidence about software delivery practices and outcomes.
2016
The project license identifies 2016 copyright for command-line tooling that creates and manages repository-based Architecture Decision Records.
2016
The Google SRE book made its postmortem-culture chapter publicly available with criteria, blameless language, review, and sharing practices. It gave teams a documented SRE reference for treating incident reviews as learning work.
2016
Google published its engineering approach to operating reliable services across the full software lifecycle. The book made service levels, error budgets, toil, automation, and production ownership available as an operating vocabulary.
2016
Performance Management Plus added employee engagement to the prior model and encouraged supervisors to engage employees early and frequently through the performance period.
2016 Jan
The report found that technology adoption did not automatically produce broad benefits. Skills, accountable institutions, regulation, and access were identified as necessary complements.
2016 Feb 17
Aline Lerner's analysis of mock technical interviews reported that roughly 25 percent of candidates performed consistently across repeated interviews. The data gave engineering teams a measured reason to distrust a pass or fail read from a single sitting.
2016 Apr
ISO/IEC 19770-3 introduced common entitlement terms, associated metrics, and a transport format. It also kept original license documentation authoritative for legal interpretation.
2016 Jul
ArchiMate 3.0 introduced strategic concepts such as capability, resource, and outcome, plus physical-world modeling.
2016 Aug
Teresa Torres published the tree as a visual connection from a desired outcome through opportunities and solutions to experiments.
2016 Oct
The plan set a national strategic framing for AI research and development priorities. It made AI planning a cross-cutting policy and investment concern rather than only a technical research topic.
2016 Nov 17
Etsy published a facilitation guide that moved from the philosophy of blamelessness to running debriefings as a learned skill. It emphasized resisting premature causal stories and gathering multiple perspectives.
2017
The 2017 report was the last listed in the earlier Puppet partnership series. DORA later continued the research as a Google Cloud program.
2017 Sep
Survey research organized digital business transformation around customer experience and operational efficiency. Leaders gained a pathway model that made sequencing and operating-model disruption explicit.
2017 Sep
ISO/IEC 19770-4 defined an information structure for resource-utilization measurements. License positions could draw on standardized metric evidence beyond installation presence.
2017 Nov
Exit from large technology contracts became an explicit program of operational preparation rather than a termination clause left for the contract end.
2017 Dec
The third edition broadened the framework into requirements for establishing, maintaining, and improving an IT asset management system. License controls became part of a wider management-system scope.
2018
DORA's 2018 report described generative culture as cooperation, trust, voice, and learning, and associated it with stronger software-delivery and organizational outcomes. It made culture a measured capability in the DevOps research program.
2018
The workbook added a case study, templates, action-item guidance, incentives, and warning signs for a postmortem culture. It translated the earlier SRE philosophy into operating practices a team can adopt.
2018
NIST updated the Risk Management Framework for information systems, organizations, security, and privacy. The update strengthened lifecycle accountability.
2018
TOGAF 9.2 updated the Business Architecture and Content Metamodel material and removed obsolete content, making the framework easier to use and maintain.
2018
The Open Group records Version 9.2 as the 2018 update in the TOGAF 9.x series.
2018 Jan
The failure exposed dependencies that extend beyond individual contracts and reinforced the need to monitor supplier health and plan continuity.
2018 Feb
ISO published the second edition of its risk-management guidelines, presenting principles, a framework, and a process applicable across organizations and sectors.
2018 Apr
CSF 1.1 added emphasis on self-assessment and cybersecurity supply chain risk management. Governance programs gained a clearer reason to connect supplier dependencies to risk oversight.
2018 May 25
The General Data Protection Regulation became applicable across the European Union. Its rules on automated individual decision-making made data protection and explanation part of many AI governance discussions.
2018 Jun 5
WCAG 2.1 added guidance addressing more mobile, low-vision, and cognitive accessibility needs. Dashboard testing expanded beyond a desktop mouse-and-screen workflow.
2018 Aug
The 2018 report examined availability as a measurement of software performance. This extended the delivery discussion beyond release speed and immediate stability.
2018 Nov
AWS introduces a self-service tool for reviewing workloads against framework questions and producing improvement plans.
2018 Nov
COBIT 2019 added design factors and guidance for tailoring a governance system to enterprise context rather than applying one uniform configuration.
2019 Feb
Cloudability helped found the FinOps Foundation after practitioners sought a community for cloud-financial practices beyond vendor tooling.
2019 Feb
ITIL 4 introduced a service value system and a more holistic, value-oriented approach that integrated governance, practices, and continual improvement.
2019 Feb
The Playbook introduced guidance on risk allocation, pilots, performance indicators, resolution plans, and delivery-model decisions. These made lifecycle controls explicit in central-government outsourcing.
2019 Feb
New guidance emphasized evidence-based make-or-buy decisions, appropriate risk allocation, pilots, published performance measures, and resolution plans.
2019 Mar
Government Digital Service described work to adapt digital marketplace practices internationally. The work linked procurement transparency with digital-sector development.
2019 May
OECD members adopted principles for innovative and trustworthy AI. The principles gave organizations a widely recognized reference for accountability, transparency, robustness, safety, and human-rights considerations.
2019 May
OECD countries adopted the Recommendation on Artificial Intelligence. The principles provided an intergovernmental reference point for trustworthy-AI policy and governance work.
2019 Sep
The first edition established the four fundamental team types and three interaction patterns as an adaptive organizational-design model.
2019 Sep 7
The first edition of Team Topologies introduced four team types and three interaction modes for fast flow. It framed team structures and communication paths as designs that evolve with context.
71 milestones
2020
The 2020 revision continued the framework's evolution around goals, value, experimentation, and measures for work under uncertainty.
2020
NASA adopted a technical-discipline taxonomy and decoupled its breakdown structure from the roadmaps, changing how technology information supported decisions.
2020 Jan
ISO/IEC 19770-8 defined how industry practices can be mapped to and from the 19770 family. Organizations gained a structured way to relate their existing controls to the standards.
2020 Feb
The white paper set out a European approach organized around excellence and trust. It connected AI uptake with a future policy framework for risk and accountability.
2020 Feb
The framework connected access, use, innovation, jobs, inclusion, trust, and market openness. It treated digital transformation as a cross-domain system with tradeoffs rather than a technology program.
2020 Feb 19
The White Paper set out a European approach to excellence and trust in AI. It put options for a legislative framework for trustworthy AI into the policy path that led to the AI Act.
2020 Mar
Spotify released Backstage as a platform for developer portals that unifies tooling, services, and documentation. The release gave platform teams a reusable implementation route for software catalogs and developer portals.
2020 Jun
A shared template library made team-interaction modeling reproducible in Google Draw, Google Slides, and diagrams.net.
2020 Jun
The FinOps Foundation became part of the Linux Foundation, moving the practice into a broader open-source foundation structure.
2020 Jun
The update added delivery model assessments and strengthened guidance on value, risk, and supplier relationships. It shifted attention from contract award toward the choice and operation of the delivery model.
2020 Jun
Version two adopted the Sourcing Playbook name to cover insourcing, outsourcing, and mixed delivery models. The guidance framed supplier choices as part of a broader sourcing decision.
2020 Jun
The second version was rebranded to reflect a choice among internal, external, and combined delivery models rather than a presumption to outsource.
2020 Aug
Backstage introduced templates for creating software components with organization-specific standards built in. The feature connected portal discovery to repeatable self-service paths for new work.
2020 Sep
Google published Four Keys as an open-source pipeline for collecting change, deployment, and incident events. The project made event definitions and joins explicit implementation work.
2020 Sep
The UK government published commercial guidance covering delivery models, market management, evaluation, cost, risk allocation, and resolution planning. It emphasized procurement as an end-to-end commercial lifecycle.
2020 Nov
NIST described how cybersecurity risk registers can communicate system and organizational risks into enterprise risk management. The guidance made risk aggregation a governance concern rather than a system-by-system activity.
2021
Prosci reorganized its methodology to support accessible, actionable practice across sequential, iterative, and hybrid project lifecycles.
2021 Feb
Microsoft Research published the SPACE framework for developer productivity. It described productivity as multidimensional rather than reducible to one activity measure.
2021 Mar
Community contributors added templates for PowerPoint, diagrams.net, Miro, and Figma, extending the mapping practice across common tools.
2021 Mar
The UK government issued technology-specific guidance for sourcing and contracting digital, data, and technology projects. It connected commercial decisions with technology delivery concerns.
2021 Mar 6
Researchers published the SPACE framework across five productivity dimensions. It gave organization designers a way to evaluate change without reducing team performance to one activity metric.
2021 Apr
The Commission proposed harmonized rules on artificial intelligence. The proposal made risk-based obligations and governance structures a concrete compliance design problem.
2021 May
The Sourcing Playbook became the third annual refresh of the earlier Outsourcing Playbook. It set expectations for how contracting authorities and suppliers engage.
2021 Jul
NIST opened a request for information that began a public development process for an AI risk framework. The process focused organizational risk management on design, development, use, and evaluation of AI systems.
2021 Oct 28
The EEOC began an initiative focused on ensuring that artificial intelligence and other software used in employment decisions comply with federal civil-rights laws. Tool governance became a named selection-process concern.
2021 Nov
AWS introduces Custom Lenses so teams can apply internal best practices alongside the framework during workload reviews.
2021 Nov
DORA described reliability as the renamed and broader successor to availability. The change covered dimensions beyond availability, including response latency and content validity.
2021 Nov
The Technical Advisory Council approved the earlier cloud-financial-management definition later replaced by the 2024 wording.
2021 Dec
The concept paper made the proposed framework available for public review. It established the early structure that later drafts and workshops refined.
2021 Dec 30
The Journal of Applied Psychology published the re-analysis showing that common meta-analytic range-restriction corrections had inflated validity estimates by .10 to .20 points. Corrected, structured interviews rank first at about .42 and cognitive ability tests fall to about .31.
2022 Jan
NAV described platform products that reduce product-team cognitive load and a progression from early collaboration toward X-as-a-Service.
2022 Mar
Backstage 1.0 marked the project transition out of beta while its CNCF incubation signaled broader technical governance. The milestone reflected the maturation of an open-source option for developer-portal practice.
2022 Mar
Improbable described stream-aligned teams, team APIs, and time-bounded collaboration while evolving its multiplayer platform.
2022 Mar
The first complete draft moved the framework from concept into a reviewable operating model. Organizations could begin relating AI governance work to a common risk-management structure.
2022 Apr
The 10th Edition reorganized TOGAF into a modular structure with expanded guidance for tailoring.
2022 Apr
The 10th Edition split the standard into Fundamental Content and TOGAF Series Guides, separating enduring concepts from configurable practice and adding guidance for agile enterprises.
2022 May
Docker documented how it reshaped product development around Team Topologies concepts while rebuilding its organization.
2022 Sep
The 2022 report described High, Medium, and Low delivery-performance clusters rather than an Elite cluster. This changed how the report summarized survey results.
2022 Oct
ISO published the third edition of ISO/IEC 27001. Organizations applying the standard continued to use a requirements-based ISMS and risk-management approach.
2023
Google Research framed developer productivity as a human-centered measurement problem involving technological and sociological conditions. It reinforced the need to evaluate those conditions together.
2023 Jan
The open billing work migrated into the FinOps Open Cost and Usage Specification project, creating a vendor-neutral billing-data specification effort.
2023 Jan
NIST released the voluntary framework and companion playbook. Govern, Map, Measure, and Manage became a practical lifecycle structure for organizing AI risk work.
2023 Jan 26
NIST released the voluntary AI Risk Management Framework 1.0. Its Govern, Map, Measure, and Manage functions gave organizations a repeatable structure for lifecycle risk work.
2023 May 18
The EEOC issued technical assistance on assessing adverse impact for software, algorithms, and artificial intelligence used in employment selection under Title VII. Automated screening inherits the same job-relatedness and adverse-impact duties as any other test.
2023 Jul
The SEC adopted rules requiring covered public companies to describe cybersecurity risk management, strategy, governance, and incident disclosure. Board oversight and management roles became explicit disclosure subjects for those issuers.
2023 Jul 5
Enforcement of Local Law 144 began for covered automated employment decision tools. Employers using covered tools in the city faced bias audit and candidate-notice requirements.
2023 Jul 5
New York City began enforcing its requirement that employers using automated employment decision tools complete an independent bias audit, publish a summary, and give candidates notice. The first binding statute aimed specifically at automated hiring tools.
2023 Oct
The Act established the new procurement regime that later changed the supporting guidance and operational preparation for contracting authorities and suppliers.
2023 Oct
The Act created a new statutory procurement framework for England, Wales, and Northern Ireland. It set the direction for later implementation guidance and procedures.
2023 Oct 5
WCAG 2.2 added success criteria while retaining backward compatibility with earlier WCAG 2 versions. Report and dashboard teams gained a new current accessibility target for web delivery.
2023 Dec
The European Parliament and Council reached political agreement on the AI Act. Organizations could begin turning the emerging requirements into inventories, controls, and evidence plans before final adoption.
2023 Dec
The standard defined requirements for an AI management system. It placed AI risks and opportunities within a continual-improvement system of organizational policies and processes.
2023 Dec
The Technical Advisory Council approved wording that describes FinOps as an operational framework and cultural practice centered on business value, timely decisions, and collaboration.
2024
Google's incident-management guide places postmortems, corrective actions, broad sharing, and aggregate learning in the wider incident lifecycle. It presents blameless learning as part of an operating system for response and improvement.
2024 Feb
CSF 2.0 added Govern as a sixth Function and expanded the framework's scope beyond critical infrastructure. Governance became an explicit set of outcomes for strategy, expectations, policy, communication, and monitoring.
2024 Mar
The Parliament adopted the final legislative text at first reading. The Act established a role- and risk-based regulatory approach for AI systems in the European Union.
2024 Mar
The Foundation published revisions that updated the definition and reorganized Framework domains, capabilities, and Personas around current practice.
2024 Mar 13
Parliament adopted the Artificial Intelligence Act. The legislative text established the risk-based framework and obligations that governance programs would need to operationalize.
2024 May
CIS released Controls v8.1 with governance recommendations for policies, procedures, processes, and compliance evidence. The update connected prioritized safeguards more directly to governance practice.
2024 May
The 2024 guide connected input, activity, output, outcome, and impact measures and clarified the experiment loop used to inspect progress.
2024 May 21
The Council gave final approval to the regulation. This completed the legislative process before publication and entry into force.
2024 Jul
Telenet described using Team Topologies thinking to address structural friction after its earlier agile-at-scale adoption.
2024 Aug
The AI Act entered into force on 1 August 2024. Organizations developing or deploying relevant systems need to map obligations to their role and the system's risk context.
2024 Aug 1
Regulation (EU) 2024/1689 entered into force. Its obligations apply on a staged schedule, so governance programs need to track which duties apply to each system and date.
2024 Oct
The Technical Advisory Council approved Scopes to capture the technology cost and usage contexts to which practitioners apply FinOps concepts.
2024 Nov
Trade Me documented the conditions that led it to introduce a thinnest viable platform and the lessons from the change.
2025 Feb
The new regime took effect on 24 February 2025. Official learning materials included operational procurement staff and professionals who manage suppliers or contracts.
2025 Feb
The new regime took effect on 24 February 2025. Buyers and suppliers began using the framework in live procurement activity.
2025 Feb 2
The first AI Act application date brought prohibited AI practices and AI-literacy obligations into application. Governance teams needed an inventory capable of identifying affected uses.
2025 Mar
Framework 2025 made Scopes a core element and reflected a Cloud-plus approach that can include technology spending beyond public cloud.
2025 Aug 2
Governance rules and obligations for general-purpose AI models became applicable. Organizations using or providing these models needed evidence appropriate to their role in the value chain.