1917
Gantt applies bar charts at Frankford Arsenal
Henry Gantt used bar charts to relate work and time in production scheduling. The form became a durable way to present project dates, though the bars alone do not express full network logic.
← IT Project Manager career guide
Management and support
IT Project Manager timeline
How the field of a IT Project Manager got here: the sourced milestones from every published course of this career, on one axis.
1917 to 2025
157 milestones across 16 courses
- Core
- Supporting
- Specialization
The axis stretches toward recent years, where most milestones fall. Bars count milestones per year; dots are single milestones.
Before 1990
19 milestones
1957
Critical Path Method enables network-based progress reading
Walker and Kelley developed CPM for DuPont maintenance work. Progress could be read against a governing sequence rather than against disconnected bar dates alone.
1957
Critical Path Method is developed
Morgan Walker and James Kelley developed CPM for DuPont maintenance projects. The method made a project's governing sequence and available timing flexibility calculable.
1957
U.S. defense programs adopt schedule performance measures
The U.S. Navy and then other defense organizations began applying schedule and cost performance measures to projects and contracts. These programs supplied the administrative setting from which formal earned value control developed.
1958
PERT and activity-on-node networks emerge
The U.S. Navy's Polaris planning effort produced PERT while John Fondahl developed an early activity-on-node representation. These approaches expanded network scheduling beyond deterministic bar displays.
1958
PERT emerges on Polaris
The U.S. Navy Polaris effort produced PERT as a networked planning method. Large programs needed shared visibility of activities that competed for scarce technical capacity.
1962
PERT Cost uses the Cost of Work Report
PERT Cost included the Cost of Work Report, an early form of the earned value concept. It connected planned and completed work with cost reporting.
1967
DoD issues C S C S C criteria
DoD Instruction 7000.2 imposed 35 Cost Schedule Control Systems Criteria on selected acquisitions. Earned value became part of a formal contractor management-control framework.
1968 Oct
NATO software engineering conference
The Garmisch conference framed software development as an engineering problem and discussed specifications, documentation, and evaluation against requirements. It established a context for treating requirements as an engineering concern rather than an informal pre-coding activity.
1969 Oct
Project Management Institute is founded
PMI created a standing forum for shared project control practice, including how progress and performance are communicated across industries.
1980 Dec 12
United States law confirms copyrightability of computer programs
A statutory amendment confirmed that computer programs fall within United States copyright law. Licensing became a principal way for copyright owners to authorize copying, modification, and distribution of software.
1981
FIPS 87 published
NIST published Guidelines for ADP Contingency Planning, establishing federal guidance for planning recovery of automated data processing capabilities.
1982
Executive contingency guide published
NIST published SP 500-85 to give managers an executive guide to automatic data processing contingency planning.
1983 Sep
GNU Project announced
Richard Stallman's announcement proposed a complete Unix-compatible system that users could share. The project made software freedom and reusable licensing central engineering concerns.
1984
IEEE 830 software requirements specification standard
IEEE 830 established a standard reference for software requirements specifications. It made the structure and quality of a specification an explicit, reviewable engineering artifact.
1985
Backup alternatives guide published
NIST published SP 500-134 on selecting automatic data processing backup process alternatives, adding strategy selection to the contingency-planning record.
1985 Oct
Free Software Foundation founded
The Free Software Foundation was created to support the GNU Project. License stewardship and enforcement gained a dedicated institution.
1986 Jan
The New New Product Development Game published
Takeuchi and Nonaka described a holistic, overlapping product development approach using a rugby metaphor. The article became one of the influences cited in Scrum's later history.
1989 Feb
GNU GPL version 1 published
GPL version 1 consolidated source availability and same-license conditions for GNU software. Distributors had a reusable copyleft license instead of program-specific notices.
1990s
22 milestones
1991 Jun
GNU GPL version 2 published
GPL version 2 revised the copyleft terms and stated that distribution must stop when other obligations prevent compliance. It became a long-lived license for major free-software projects.
1993
Scrum developed at Easel Corporation
Jeff Sutherland and colleagues developed Scrum at Easel Corporation. This established an empirical team framework before the Agile Manifesto supplied a broader name for related approaches.
1993
UK programme-management guidance begins
UK government guidance developed during 1993 through 1995 treated coordinated programmes as a distinct management problem rather than a larger project.
1993 Jan
First IEEE requirements engineering symposium
IEEE held the first International Symposium on Requirements Engineering in San Diego. The event gave requirements engineering a dedicated international research forum.
1994 Apr
First IEEE requirements engineering conference
The first International Conference on Requirements Engineering met in Colorado Springs. The conference series complemented the symposium with a second venue focused on the discipline.
1994 Apr
WTO Government Procurement Agreement adopted
The Agreement established international rules for covered government procurement. It made procurement transparency and non-discrimination part of a multilateral framework.
1995
NIST SP 800-12 introduces computer security guidance
NIST published a general computer security handbook. It provided a public foundation before later risk-specific guidance.
1995
Scrum is co-presented at OOPSLA
Ken Schwaber and Jeff Sutherland co-presented Scrum at OOPSLA, making an early formal definition public.
1995
Scrum presented at OOPSLA
Ken Schwaber presented Scrum publicly at the OOPSLA conference in Austin. The framework entered wider software-development discussion before the Agile Manifesto.
1995
Scrum receives its first formal public definition
Ken Schwaber and Jeff Sutherland co-presented Scrum at OOPSLA. Iterative planning and inspection offered a formal alternative to completing one detailed predictive schedule before delivery.
1996
First PMBOK Guide edition is published
PMI published the first PMBOK Guide as a shared body of project management knowledge. Resource-related planning processes entered a common professional vocabulary used in certification and method design.
1996
First PMBOK Guide published
PMI introduced the PMBOK Guide, giving project management a shared reference for practices and terminology.
1996
Industry ownership consolidates the criteria
The government-industry transition reduced the earlier 35 criteria to 32 and moved toward an industry-owned standard. The change shifted emphasis from a defense-only specification toward a common EVMS framework.
1996
NIST SP 800-14 publishes security principles
NIST published generally accepted principles and practices for securing information technology systems. Security practice gained defined management expectations.
1996
PRINCE2 introduces structured progress reports
PRINCE2 established highlight and checkpoint reporting as standard management products so boards could manage by exception between stage boundaries.
1997
Goldratt publishes Critical Chain
Eliyahu Goldratt's Critical Chain treated resource contention as part of the governing project path. The method shifted attention from task padding toward resource-feasible sequences and buffers.
1997 Jul 5
Debian Free Software Guidelines ratified
Debian adopted criteria for free redistribution, source availability, modification, and non-discrimination. Those guidelines became the basis for the Open Source Definition.
1998 Feb
Open source named and OSI formed
The open source label was coined in February, and the Open Source Initiative formed later that month. OSI adapted the Debian guidelines into the Open Source Definition.
1998 Apr
Third IEEE requirements engineering conference
ICRE 1998 continued the alternating conference and symposium series. The recurring events strengthened a shared research and practice community around elicitation, specification, and validation.
1998 Jun
ANSI EIA 748 issued
The first EIA-748 Earned Value Management Systems standard was issued in June 1998. Its 32 guidelines became the central system reference used by government and industry.
1999
Managing Successful Programmes formalized
The first Managing Successful Programmes guide consolidated earlier UK programme guidance into a named method.
1999 Oct
OSI publishes its first formal approved-license list
The approved list gave developers and organizations a shared catalog of licenses reviewed against the Open Source Definition. Approval status became distinct from a project's own licensing claim.
2000s
41 milestones
2000
PMBOK Guide 2000 Edition released
The 2000 edition extended the 1996 guide with updated practices, tools, techniques, and clarifications.
2000
PMBOK Guide frames project communications management
The 2000 edition described processes for timely generation, collection, dissemination, and disposition of project information, anchoring status work in a communications knowledge area.
2001
Agile Manifesto is published
The Agile Manifesto stated principles for iterative software work, including regular reflection and adjustment. Scrum later became widely used within this broader agile context.
2001
NIST SP 800-26 supports self-assessment
NIST published a questionnaire-based self-assessment guide. Assessment became a repeatable control-management activity.
2001 Feb
Agile Manifesto is published
Seventeen practitioners published values for adaptive software development, including responding to change over following a plan. Project forecasts increasingly had to support refinement rather than imply frozen certainty.
2001 Feb
Agile Manifesto published
The manifesto articulated values that favored collaboration, working software, customer collaboration, and responding to change.
2001 Feb
Manifesto for Agile Software Development signed
Seventeen practitioners met at Snowbird and published the Manifesto for Agile Software Development. It expressed common value preferences across several existing lightweight approaches.
2002
NIST SP 800-30 frames IT risk assessment
NIST published a risk-management guide for information technology systems. It described assessment methods and control-selection recommendations.
2002 Jun
NIST SP 800-34 published
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 SP 800-30 published
NIST documented a risk-management process for identifying, assessing, mitigating, and continually evaluating information-technology risk.
2002 Aug
Conference and symposium merge into annual RE
The separate IEEE conference and symposium series merged into the annual International Requirements Engineering Conference. The merged series became a continuing venue for the field.
2003
PMI charters program and portfolio standards
PMI created its Program and Portfolio Management Standards effort and established common definitions before developing separate standards.
2003 May
PMI paper codifies a status communication framework
Berzkalns published a practical stakeholder-needs, metrics, plan, gather, compile, and disseminate cycle for project status communication at PMI Global Congress EMEA.
2004
NIST SP 800-37 links assessment to authorization
NIST published guidance using risk and control assessments to inform a senior official's approval of a system's security posture.
2004
PMBOK Guide Third Edition highlighted competing demands
PMI described the triple constraint as a framework for evaluating competing demands in project work.
2004 Jan
Apache License 2.0 published
Apache License 2.0 supplied a reusable permissive license with express patent terms, NOTICE handling, and change-marking conditions. It gave projects a standard alternative to custom permissive text.
2004 Mar
EU public procurement directive adopted
Directive 2004/18/EC consolidated rules for public works, supply, and service contracts. It gave European public buyers a common procedural baseline.
2004 Oct
Microsoft XIT uses a pull system
A pull system was designed for Microsoft's XIT Sustaining Engineering group, with Test treated as the bottleneck. It established an early software-service application before a physical board was involved.
2005
NIST SP 800-53 establishes control baselines
NIST published a control catalog with low, moderate, and high baselines. Teams gained a starting point adjustable for system-specific risk.
2005
PMI publishes its first EVM practice standard
PMI published a practice standard that described EVM elements and their application beyond government contracting. A later second edition revised this 2005 publication.
2005
The XIT system is reframed as kanban
After discussion with Donald Reinertsen, the XIT implementation was revisited as a kanban system. The change made the approach easier to explain and shifted attention to WIP limits.
2006
Knowledge-work kanban is presented publicly
The completed XIT story was presented publicly as a virtual kanban system implementation. This made the approach visible beyond its original team.
2006
PMI paper pairs digital dashboards with earned value metrics
Forman and Discenza described digital dashboards as at-a-glance project performance displays fed by underlying data, including earned value metrics for active project control.
2006 May
First ISO software asset management process standard
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 May 8
PMI releases its first program and portfolio standards
Separate standards formalized the difference between coordinating related components and selecting a strategic investment mix.
2006 Sep
Corbis designs a kanban system
Corbis designed a system to replace a project-centric process for minor application upgrades. An expedite capability introduced an alternative class of service.
2006 Sep
NIST SP 800-84 finalized
The publication organized test, training, and exercise programs so plans and capabilities could be verified and improved through recorded evidence.
2007
The recognizable Kanban Method emerges
The six practices, capacity allocation, and classes of service emerged from the Corbis work. The method connected WIP limits and visualized risks to service decisions.
2007 Jan
A visible card wall supports improvement
A card wall was added at Corbis as flow variation became difficult to interpret. It supported further improvement and made workflow visualization a practical intervention.
2007 Jun
The full Corbis implementation is presented
A conference presentation covered classes of service, lead-time histograms, operations review, and improvement events. These made flow evidence part of the method's public practice.
2007 Jun 29
GNU GPL version 3 published
GPL version 3 updated copyleft terms for patents, user products, and source delivery after a public drafting process. Reviewers now had to record an exact GPL version and any later-version option.
2008
NIST SP 800-53A formalizes assessment procedures
NIST published guidance for assessment plans and procedures. Controls could be tested for operating as intended rather than assumed from their existence.
2008
PMBOK Fourth Edition centers performance reporting
Performance reporting was described as collecting and distributing status, measurements, and forecasts within communications management, reinforcing reports as a control process output.
2008
PMBOK Guide Fourth Edition released
PMI released the fourth edition as part of a simultaneous update of four standards.
2008
PMI publishes second editions
PMI expanded its portfolio and program guidance, including a broader set of portfolio processes and updated professional practice.
2008 Aug
Scrumban scenarios are presented
Detailed implementation scenarios included applying Kanban to Scrum teams and projects. The presentation became a foundation for the approach later called Scrumban.
2009
GAO publishes its first Cost Estimating and Assessment Guide
GAO established a government-wide best-practice framework for reliable cost estimates and EVM-based program control. The guide connected earned value results to schedule, risk, and estimate quality.
2009 Mar
GAO publishes its Cost Estimating and Assessment Guide
GAO established a government-wide methodology for reliable cost estimates tied to WBS, schedules, risk, and performance measurement. The guide made documented assumptions and cross-checks central assessment criteria.
2009 Mar
GAO publishes the Cost Estimating and Assessment Guide
GAO tied credible cost estimates to schedules, WBS, and resources. The guide reinforced that time and cost claims are weak when staffing feasibility is unexamined.
2009 May
The first Lean Kanban conference convenes
The first Lean Kanban conference was held in Miami after community discussion. It created a forum for sharing practice beyond individual organizations.
2009 Nov
SWID tags standardized software identification
ISO/IEC 19770-2 defined machine-readable software identification tags. It standardized an inventory input while explicitly leaving entitlement reconciliation to other processes.
2010s
51 milestones
2010
First Scrum Guide is written
The Scrum Guide's authors wrote its first version to provide a shared definition of Scrum for readers worldwide.
2010
First Scrum Guide published
Ken Schwaber and Jeff Sutherland published the first official Scrum Guide. A concise public reference made the framework's accountabilities, events, artifacts, and rules easier to distinguish from local custom.
2010
NIST SP 800-37 Revision 1 defines the RMF
NIST expanded certification and accreditation into the Risk Management Framework. Risk management was described as a system life-cycle process.
2010 Feb
SPDX specification drafting begins
A Linux Foundation work group began drafting a standard for package and license information. Compliance data started moving from project-specific spreadsheets toward interoperable identifiers and documents.
2010 May
Kanban is published for technology businesses
David J. Anderson's book Kanban - Successful Evolutionary Change for Your Technology Business was published. It gave practitioners a dedicated reference for implementing kanban systems in knowledge-work settings.
2010 May
NIST SP 800-34 Revision 1 published
The revision updated contingency planning for federal information systems and supplied impact-analysis and plan templates for different impact levels.
2011
ISO/IEC/IEEE 29148 first edition
ISO/IEC/IEEE 29148 consolidated requirements-engineering guidance for systems and software life cycles. It connected requirements work to the lifecycle process standards it supports.
2011
NIST SP 800-137 addresses continuous monitoring
NIST published continuous-monitoring guidance. Monitoring became an ongoing activity rather than a point-in-time check.
2011
NIST SP 800-39 connects organization and system views
NIST published guidance for organization, mission, and information-system risk. Local assessments became connected to wider governance.
2011
PMI issues the second EVM practice standard
PMI revised its practice standard with a second edition. The edition continued a sector-neutral route for applying the method to different project situations.
2011
Scrum Guide receives an early revision
The official revision history records changes between the 2011 and 2013 Guides, establishing a maintained public reference.
2011 Mar
Government ICT Strategy published
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 Apr
UK Government Major Projects Portfolio created
The Major Projects Authority created a cross-government portfolio for the largest and riskiest projects, adding centralized transparency and assurance.
2011 Nov
Lean Kanban University becomes a trade association home
Lean Kanban University was positioned as the home of a trade association for standardized Kanban training. Sixteen founding firms joined as charter members.
2012
PMBOK Guide Fifth Edition offered for presale
PMI announced the fifth edition in its 2012 annual report as the next update to its project-management guide.
2012 Feb
First G-Cloud supplier framework went live
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 framework opens to UK public buyers
G-Cloud created a route for public bodies to buy cloud services. It shifted attention toward reusable frameworks and digital service marketplaces.
2012 Feb
The Lean Kanban University association launches
Founding members agreed a governing charter in Utrecht and launched the association publicly. The milestone marked a more formal global training community.
2012 Jun
SAM processes organized into implementation tiers
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
ISO 21500 establishes international context
ISO published common project-management guidance and began a wider standards family covering programs, portfolios, governance, and related practices.
2012 Sep
NIST SP 800-30 Revision 1 published
The revision organized risk assessment into preparation, conduct, and maintenance, reinforcing assessment as an ongoing input to risk-management decisions.
2013
Artifact transparency is added
The 2013 revision added an Artifact Transparency section, reinforcing that inspection depends on a trustworthy view of work.
2014 Mar
Directive 2014/24/EU adopted
The directive replaced the 2004 EU public-procurement directive. It updated the legal framework for public purchasing and procurement procedures.
2014 Apr
Revised WTO procurement agreement enters into force
The revised Agreement entered into force for the parties that accepted it. It updated the international procurement framework and expanded its coverage.
2015
Government Commercial Function formed
The Government Commercial Function brought commercial roles into a cross-government function. It established a central capability for commercial standards and improvement.
2015 Feb
ESFA records digital procurement lessons
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 Aug
ITAM and SAM vocabulary consolidated
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 Aug 14
ISO 21504 adds portfolio guidance
ISO published its first portfolio-management standard, emphasizing alignment of work and resources with organizational objectives.
2015 Oct
SWID roles and exchange refined
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.
2015 Dec
GAO publishes the Schedule Assessment Guide
GAO formalized ten best practices for comprehensive, well-constructed, credible, and controlled schedules. The guide joined deterministic network checks with resource and schedule-risk analysis.
2015 Dec
GAO Schedule Assessment Guide is issued
GAO-16-89G published best practices for updating schedules with actual progress and logic, maintaining baselines, and communicating forecast versus baseline performance.
2016
Scrum Values are added
The 2016 revision added commitment, courage, focus, openness, and respect as the values supporting transparency, inspection, and adaptation.
2016 Jan
PMI publishes cross-layer governance guidance
PMI's governance practice guide addressed governance frameworks across portfolios, programs, projects, and the wider organization.
2016 Apr
Entitlement schema standardized
ISO/IEC 19770-3 introduced common entitlement terms, associated metrics, and a transport format. It also kept original license documentation authoritative for legal interpretation.
2017
PMBOK Guide Sixth Edition incorporated agile content
PMI updated the sixth edition with agile content and published the Agile Practice Guide with the Agile Alliance.
2017
Uses of Scrum are expanded in the Guide
The 2017 revision described Scrum's use beyond software development, including work on products, operations, and complex domains.
2017 Sep
Resource-utilization measurements structured
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
PMI portfolio standard becomes principle-based
The fourth portfolio edition reflected the practice's evolution and emphasized applicability across organizations and delivery approaches.
2017 Nov
Scrum Guide revised
The 2017 revision continued the guide's update sequence after the 2011, 2013, and 2016 editions. It kept the framework as a maintained reference rather than a frozen set of ceremonies.
2017 Dec
ISO/IEC 19770-1 became an ITAM management-system standard
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
NIST SP 800-37 Revision 2 broadens the RMF
NIST updated the Risk Management Framework for information systems, organizations, security, and privacy. The update strengthened lifecycle accountability.
2018 Feb
ISO 31000 second edition published
ISO published the second edition of its risk-management guidelines, presenting principles, a framework, and a process applicable across organizations and sectors.
2018 Apr
ISO 21508 published
ISO published international guidance for EVM terms, processes, basic system requirements, analysis, and integration. The standard applied across organization types, sectors, project sizes, and levels of complexity.
2018 Oct
UK GovS 002 Project Delivery standard is first published
The UK functional standard set government-wide expectations for portfolios, programmes, and projects. Resource, capacity, and capability management was stated as a planning-and-control practice that forces replanning when supply is short.
2018 Nov
ISO/IEC/IEEE 29148 second edition
The second edition of ISO/IEC/IEEE 29148 replaced the 2011 edition. It specified requirements-engineering processes and information items for systems and software work.
2018 Dec
PMI connects delivery to benefits realization
PMI's benefits guide traced benefits from organizational strategy through project deliverables and measurable value.
2019 Feb
Outsourcing Playbook published
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 Mar
DoD updates its EVMS interpretation guide
DoD issued an updated interpretation guide for assessing compliance with the EIA-748 guidelines. The guide aligned system review with current integrated program-management practice.
2019 Mar
Global Digital Marketplace shares multi-supplier lessons
Government Digital Service described work to adapt digital marketplace practices internationally. The work linked procurement transparency with digital-sector development.
2019 Jun
PMI issues its third scheduling practice standard
PMI updated its schedule-model guidance with detailed treatment of CPM, PERT, rolling-wave planning, simulation, and adaptive approaches. The edition placed predictive and adaptive scheduling in one practice framework.
2019 Jun
PMI issues the third scheduling practice standard
PMI updated scheduling practice guidance with resource optimization alongside CPM, PERT, and adaptive approaches. Resource-feasible scheduling remained part of mainstream professional method, not a niche add-on.
2020s
24 milestones
2020 Jan
Industry-practice mapping guidance published
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 Jan
PMI issues its second project estimating practice standard
PMI updated its estimating standard for both plan-driven and change-driven adaptive life cycles. Estimation refinement became explicit across different delivery approaches.
2020 Mar
GAO updates the Cost Estimating and Assessment Guide
GAO expanded and modernized its best practices for cost estimating and earned value management. The update included software cost estimating and a revised treatment of program-control evidence.
2020 Jun
Outsourcing Playbook updated
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
Playbook rebranded as the Sourcing Playbook
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 Sep
GAO publishes the Agile Assessment Guide
GAO documented practices for Agile adoption, execution, and program monitoring in federal IT. The guide connected incremental software delivery with cost forecasting and program oversight.
2020 Sep
The Sourcing Playbook published
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
Current Scrum Guide is released
The November 2020 Guide clarified the Scrum Team as self-managing and retained the framework's focus on empirical adaptation.
2020 Nov
Scrum Guide 2020 clarifies inspection events
The 2020 Scrum Guide restated Daily Scrum and Sprint Review as progress inspection toward goals, shaping how iterative teams produce evidence that external status packs must still translate.
2020 Nov
Scrum Guide 2020 released
The current official Scrum Guide was released in November 2020. It defines Scrum through the 2020 accountabilities, events, artifacts, and commitments used in this course.
2020 Dec
The Kanban Guide published
The December 2020 Kanban Guide defined a minimal reference for managing flow and improving delivery. It gave practitioners a shared baseline for the workflow and flow metrics discussed here.
2021
NASA publishes its consolidated EVM implementation handbook
NASA consolidated EVM application, implementation, and use guidance for programs, projects, contracts, and subcontracts. The handbook provided an end-to-end operational reference for NASA organizations.
2021 Mar
Digital, Data and Technology Playbook published
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 May
Third annual Playbook update issued
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
GovS 002 version 2.0 is published
The UK updated the Project Delivery functional standard while keeping resource and capacity expectations inside planning and control. The revision kept capacity constraints visible in the approved government reference model.
2021 Aug
PMBOK Guide Seventh Edition published
The seventh edition organized guidance around principles and performance domains across predictive, adaptive, and hybrid approaches.
2021 Aug
SPDX becomes ISO IEC 5962:2021
The SPDX specification became an international standard. Machine-readable component and license information gained a standards-based exchange format for software supply chains.
2022 Feb
ISO aligns updated program and portfolio guidance
Second editions of ISO 21503 and ISO 21504 aligned program and portfolio guidance with the shared ISO 21500 context and concepts.
2023 Oct
Procurement Act 2023 received Royal Assent
The Act established the new procurement regime that later changed the supporting guidance and operational preparation for contracting authorities and suppliers.
2023 Oct
Procurement Act 2023 receives Royal Assent
The Act created a new statutory procurement framework for England, Wales, and Northern Ireland. It set the direction for later implementation guidance and procedures.
2024 May
SEBoK adds a requirements management article
SEBoK version 2.10 added a dedicated Requirements Management article during its systems engineering and management updates. The change reflected requirements management as an explicit part of current systems-engineering guidance.
2025 Feb
Procurement Act 2023 came into force
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
Procurement Act 2023 comes into force
The new regime took effect on 24 February 2025. Buyers and suppliers began using the framework in live procurement activity.
2025 May
The Kanban Guide updated
The May 2025 guide continued the public Kanban reference as a living document. Its timing remains outside the most recent twelve months, preserving this tab as history rather than release news.