Tag: Summary

Agile Scrum on a page, summary of core focus areas

Agile Scrum on a page, summary of core focus areas

Scrumban project management summary and detailed historical timeline by era and year

Scrumban is a hybrid Agile project management framework that blends the structured planning and roles of Scrum with the continuous flow and visualization of Kanban. Originally designed as a transition method for teams moving from Scrum to Kanban, it has evolved into a popular, distinct approach for teams needing to manage unpredictable work (e.g., support, maintenance) while maintaining prioritized planning. It focuses on pull-based workflows, limiting Work-in-Progress (WIP), and continuous improvement. 

Scrumban Summary

  • Best Used For: Teams needing more flexibility than Scrum (no rigid sprints) but more structure than Kanban (needs planning cycles).
  • Key Features: Visual board (Kanban), Work-in-Progress (WIP) limits, on-demand or iterative planning, and a pull-based workflow.
  • Differences from Parent Frameworks:
    • vs. Scrum: No set sprint length or rigid roles; work is pulled continuously rather than planned in batches.
    • vs. Kanban: Uses planning meetings and team retrospectives, whereas classic Kanban is purely continuous. 

Detailed Historical Timeline of Scrumban

1. The Pre-Scrumban Era (Pre-2008)

  • 1950s (Kanban Origin): Toyota develops Kanban to optimize manufacturing production processes, focusing on Just-in-Time (JIT) production.
  • 1986 (Scrum Concept): Takeuchi and Nonaka introduce the “rugby” approach to product development in the Harvard Business Review, fostering flexible, team-based development.
  • 1995 (Scrum Introduced): Ken Schwaber and Jeff Sutherland formalize the Scrum framework for software development.
  • 2001 (Agile Manifesto): Release of the Agile Manifesto, establishing core agile principles.
  • 2004 (Kanban in Software): David J. Anderson suggests applying Kanban practices to software development to improve workflow.
  • 2000-2007 (Evolution): Microsoft teams begin experimenting with “feature crews” that mix structured planning with continuous delivery, planting the seeds for hybrid approaches. 

2. Conception and Definition (2008–2010)

  • 2008: Corey Ladas coins the term “Scrumban” and introduces the concept in his work, proposing it as a mechanism for teams to transition from Scrum to Kanban, or as a sustainable hybrid for maintaining focus while reducing iteration overhead.
  • 2008: Ajay Reddy discusses the “Scrumban (R)evolution,” emphasizing that Scrumban is a distinct, powerful approach, not merely a blend.
  • 2009: Ladas publishes “Scrumban: Essays on Kanban Systems for Lean Software Development,” providing the definitive framework for the approach. 

3. Formalization and Adoption (2011–2019)

  • Early 2010s: The methodology gains popularity in specialized software areas, such as maintenance and support teams, where unpredictable bugs demand faster flexibility than two-week sprints.
  • 2016: Ajay Reddy releases “The Scrumban [R]Evolution: Getting the Most Out of Agile, Scrum, and Lean Kanban,” providing practical guidelines for applying the methodology.
  • 2018-2019: Adoption expands beyond software development into agile marketing and HR, looking for reduced bureaucracy. 

4. Mature Hybrid & Continued Growth (2020s–Present)

  • 2020s: Scrumban is recognized as a standard agile framework within major project management tools (e.g., Jira, Miro, Monday).
  • 2025-2026: Further refinement as teams integrate AI-driven task management with visual Kanban workflows to increase throughput and automate WIP tracking. 

Core Principles of Modern Scrumban (2026 Perspective)

  1. Pull System: Work is pulled by team members when capacity allows, rather than pushed into the team.
  2. Visual Board: All tasks are visualized to show bottlenecks.
  3. WIP Limits: Restricting the number of active tasks at any stage to improve efficiency.
  4. No Required Roles: Teams can keep Scrum roles (Product Owner, Scrum Master) or remove them, depending on their needs.
  5. Adaptive Planning: Planning occurs on-demand or at short intervals, not just in strict timeboxed sprints.

Scrumban project management summary and detailed historical timeline by era and year

PERT Program Evaluation & Review Technique summary & detailed historical timeline by era & year

The Program Evaluation and Review Technique (PERT) is a project management tool developed in the late 1950s to analyze and represent the tasks involved in completing a complex project. It is designed to handle uncertainty in project scheduling by using three time estimates (optimistic, pessimistic, and most likely) to calculate the expected duration of tasks. 

Summary of PERT Project Management

  • Origin: Developed in 1958 by the U.S. Navy Special Projects Office to manage the Polaris missile submarine program, which involved thousands of contractors.
  • Purpose: To schedule, organize, and coordinate tasks within complex, non-repetitive projects, allowing for the identification of the critical path.
  • Key Feature (Three-Time Estimate): Unlike traditional methods, PERT uses a probabilistic approach.
  • Visual Structure: A PERT chart acts as a network diagram, using nodes (circles/rectangles) for events and arrows for tasks and dependencies.
  • Impact: Credited with shortening the Polaris project timeline by two years.

Detailed Historical Timeline of PERT (1950s–Present)

The Era of Development (1950s)

  • 1957: The groundwork for network scheduling began in the US, with DuPont developing the Critical Path Method (CPM) and preliminary research into PERT concepts beginning.
  • 1958: Birth of PERT. The U.S. Navy Special Projects Office officially develops PERT for the Polaris missile project to manage high uncertainty in R&D.
  • 1958: The first two publications, Program Evaluation Research Task, Summary Report, Phase 1 and 2, are written (primarily by Charles F. Clark) to document the technique.
  • 1959: Willard Fazar of the Navy officially introduces PERT to the public in The American Statistician, detailing the use of three time estimates. 

The Expansion and Mainframe Era (1960s–1970s) 

  • 1960s: PERT is widely adopted by NASA and the U.S. Department of Defense for large, schedule-driven projects.
  • 1962: The US Department of Defense mandates the use of Work Breakdown Structures (WBS) for projects, reinforcing PERT application.
  • 1965: PERT is applied to the planning and organization of the 1968 Winter Olympics in Grenoble.
  • 1970s: PERT/CPM software packages begin to be used on mainframe and minicomputers. 

The PC and Software Era (1980s–1990s)

  • 1980s: With the advent of personal computers, PERT software becomes accessible, leading to adoption in software development and manufacturing.
  • 1984: The Theory of Constraints (TOC) is introduced, which later influences critical chain methodologies, adding to network scheduling techniques.
  • 1987: The Project Management Institute (PMI) publishes the first white paper on the Project Management Body of Knowledge (PMBOK), including network techniques.
  • 1997: Critical Chain Project Management (CCPM) is introduced as a new approach to managing resources and task uncertainty, building on PERT/CPM principles. 

The Digital and Agile Era (2000s–Present)

  • 2000s: PERT charts become a standard feature in project management software (MS Project, Primavera), automating the calculation of critical paths.
  • 2012: ISO 21500:2012 provides guidance on project management, incorporating network analysis techniques.
  • 2017/2021: PMBOK releases 6th and 7th editions, integrating PERT and network scheduling with agile and adaptive environments.
  • Present: While overshadowed by Agile (Scrum/Kanban) in software, PERT remains crucial for complex construction, R&D, and defense projects, often used in hybrid approaches. 

Key Components of a PERT Chart

  1. Event (Node): A milestone representing the start or completion of a task.
  2. Activity (Arrow): The actual task required to move from one event to another.
  3. Critical Path: The longest sequence of dependent tasks, determining the minimum project duration.
  4. Float (Slack): The amount of time a task can be delayed without delaying the overall project. 

Six Sigma project management summary and detailed historical timeline by era and year

Six Sigma is a disciplined, data-driven methodology and project management strategy designed to improve process performance, eliminate defects, and minimize variation. Pioneered at Motorola in the 1980s, it aims for a near-perfection standard of no more than 3.4 defects per million opportunities (DPMO). It is often used in combination with Lean principles (Lean Six Sigma) to simultaneously eliminate waste and reduce variation. 

Six Sigma Project Management Summary

Six Sigma project management relies on a structured, five-phase framework known as DMAIC (pronounced “duh-may-ick”) for improving existing processes: 

  • Define: Identify the project goals and customer deliverables (Critical to Quality – CTQ).
  • Measure: Quantify the current process performance and gather baseline data.
  • Analyze: Determine the root causes of defects and variation.
  • Improve: Implement and verify solutions that eliminate the root causes.
  • Control: Standardize the new process and implement monitoring to ensure long-term sustainability. 

Key Project Roles (The Belt System):

  • White/Yellow Belt: Basic awareness and team members.
  • Green Belt: Leads projects, assists Black Belts.
  • Black Belt: Leads complex projects, acts as change agent.
  • Master Black Belt: Coaches Black/Green Belts, oversees strategy.

Detailed Historical Timeline by Era and Year

Pre-1980s: Foundational Quality Efforts 

  • 1799: Eli Whitney introduces the concept of interchangeable parts (standardization) to produce muskets, reducing variation.
  • 1920s: Walter Shewhart at Bell Laboratories shows that 3-sigma process control is necessary to reduce variation.
  • 1950s: Toyota Production System (TPS) develops to create efficiency and quality. 

1980s: Origin and Development (The Motorola Era) 

  • 1981: Motorola leadership (Bob Galvin) initiates a push for increased quality, arguing that traditional 3-sigma defects (thousands) were insufficient, prompting a push for DPMO.
  • 1985: Engineer Bill Smith pens a paper proposing the term and methodology of Six Sigma.
  • 1986: Bill Smith officially introduces Six Sigma at Motorola, with Mikel Harry and Bob Galvin as co-contributors.
  • 1987: Motorola formally founds the Six Sigma improvement program, targeting a 10-fold reduction in defects.
  • 1988: Motorola receives the first Malcolm Baldrige National Quality Award.
  • 1989: Motorola establishes the Six Sigma Research Institute. 

1990s: Expansion and Standardization (The GE/Allied Signal Era) 

  • 1990: Motorola introduces the concept of Black Belts to formally lead improvement projects.
  • 1993: Motorola registers Six Sigma as a trademark.
  • 1994: AlliedSignal adopts Six Sigma, with CEO Larry Bossidy leading the effort.
  • 1995: Jack Welch adopts Six Sigma at General Electric (GE), optimizing the DMAIC approach and boosting its popularity.
  • Late 1990s: Over 2/3 of Fortune 500 companies start Six Sigma initiatives. 

2000s: Integration with Lean (The Lean Six Sigma Era) 

  • 2000s: Global adoption of Six Sigma by companies like Sony, Jaguar, Samsung, and Adidas.
  • 2002: Michael George publishes “Lean Six Sigma,” combining the speed of Lean (waste reduction) with the quality of Six Sigma (variation reduction).
  • Mid-2000s: Six Sigma expands beyond manufacturing into services, healthcare, and finance. 

2010s – Present: Digitalization and Advanced Analytics

  • 2010s: Integration of data-driven Six Sigma with technology, including real-time monitoring and advanced data analytics.
  • Present: Incorporation of Big Data, Machine Learning, and AI to enhance analytical capabilities and predictive maintenance within the DMAIC framework. 

Key Contributors to Six Sigma

  • Bill Smith: “Father of Six Sigma,” developed the concept at Motorola.
  • Bob Galvin: CEO of Motorola, supported and pushed the adoption of the methodology.
  • Mikel Harry: Co-developed the methodology and helped establish the Six Sigma Institute.
  • Jack Welch: Former CEO of GE, championed the strategy, proving its power outside of manufacturing.
  • Larry Bossidy: CEO of Allied Signal, instrumental in early adoption.

Six Sigma project management summary and detailed historical timeline by era and year

Scrum Agile Framework summary and detailed historical timeline by era and year

Scrum is an Agile framework for managing complex, innovative product development through small, cross-functional teams working iteratively in short time-boxes called Sprints. Inspired by a 1986 “rugby” approach to product development, it was formalized in the early 1990s by Jeff Sutherland and Ken Schwaber to improve team productivity and deliver value quickly.

Scrum is based on empiricism—transparency, inspection, and adaptation—and is defined by specific roles (Product Owner, Scrum Master, Developers), events (Sprint Planning, Daily Scrum, Sprint Review, Retrospective), and artifacts (Product Backlog, Sprint Backlog, Increment). 

Detailed Historical Timeline

The Conceptual Era (Pre-1990s)

  • 1986: Takeuchi and Nonaka publish “The New New Product Development Game” in Harvard Business Review. They introduce the “rugby” approach—a team working together, passing the ball back and forth, to increase speed and flexibility. 

Scrum Takes Shape (1990–1999) 

  • 1993: First Scrum implementation: Jeff Sutherland, John Scumniotales, and Jeff McKenna at Easel Corporation apply these concepts to software development.
  • 1995: Ken Schwaber and Jeff Sutherland present a paper, “The SCRUM Development Process,” at the Object-Oriented Programming, Systems, Languages & Applications (OOPSLA) conference in Austin, Texas, formally introducing the framework.
  • 1996: Ken Schwaber and Mike Beedle refine the process, focusing on software development.
  • 1999: Mike Beedle, Martine Devos, Yonat Sharon, Ken Schwaber, and Jeff Sutherland publish “SCRUM: An extension pattern language for hyperproductive software development”. 

Agile and Formalization (2000–2009) 

  • 2001: Ken Schwaber, Jeff Sutherland, and 15 others create the “Agile Manifesto” in Snowbird, Utah. Schwaber and Beedle publish the first book on Scrum: Agile Software Development with Scrum.
  • 2002: Ken Schwaber, Mike Cohn, and Esther Derby found the Scrum Alliance to provide certifications.
  • 2004: Ken Schwaber publishes Agile Project Management with Scrum.
  • 2006: Jeff Sutherland founds Scrum Inc..
  • 2009: Ken Schwaber leaves the Scrum Alliance and founds Scrum.org to provide Professional Scrum accreditation. 

The Scrum Guide Era (2010–Present) 

  • 2010: First “Scrum Guide” is published by Ken Schwaber and Jeff Sutherland to define the framework, often revised in subsequent years (2011, 2013, 2016, 2017).
  • 2017: PRINCE2 Agile is published, adding governance layers for organizations using Scrum.
  • 2020: The latest Scrum Guide (November 2020) is released, focusing on a more minimal, less prescriptive definition, introducing the “Product Goal” and changing “Development Team” to “Developers”. 

Key Components of Scrum

  • Roles: Scrum Master (servant leader), Product Owner (backlog owner), Developers (build the product).
  • Events: Sprint (1–4 weeks), Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective.
  • Artifacts: Product Backlog, Sprint Backlog, Increment. 

Scrum Agile Framework summary and detailed historical timeline by era and year

SAFe Scaled Agile Framework summary and detailed historical timeline by era and year

The Scaled Agile Framework (SAFe) is a set of organization and workflow patterns intended to guide enterprises in scaling lean and agile practices across large-scale software and systems development. Created by Dean Leffingwell in 2011, it combines Agile development, Lean product development, and systems thinking to enable alignment, collaboration, and delivery across hundreds or thousands of practitioners. 

SAFe Project Management Summary

SAFe structures project management across multiple levels to bring agility to the enterprise: 

  • Team Level: Scrum or Kanban teams operate in 2-week iterations (sprints) to deliver working software.
  • Program Level (Agile Release Train – ART): A “team of teams” (typically 50-125+ people) aligns to a common mission, planning, and releasing together on a fixed cadence, usually via Program Increments (PIs) lasting 8–12 weeks.
  • Portfolio Level: Aligns strategy to execution, managing investment themes (Epics) through Lean Portfolio Management.
  • Core Values & Principles: SAFe is grounded in 10 principles (e.g., “Take an economic view,” “Apply systems thinking”) and four core values: Alignment, Built-in Quality, Transparency, and Program Execution. 

Historical Timeline by Era and Version

The evolution of SAFe tracks the growing need for business agility and faster delivery in complex organizations. 

1. Foundation & Initial Concept (2007–2010)

  • 2007–2008: Dean Leffingwell publishes Scaling Software Agility, laying the foundation for enterprise agile patterns.
  • 2010: Agile Software Requirements is published, bridging Agile with enterprise needs. 

2. The Early Years: SAFe 1.0 – 2.0 (2011–2013) 

  • 2011: SAFe 1.0 released, initially termed “Agile Enterprise Big Picture,” focusing on applying Scrum/XP at scale.
  • 2012: SAFe 2.0 (October) released to restructure portfolio and program levels.
  • 2013: Initial refinements to the “Big Picture” to better integrate lean principles. 

3. Expansion: SAFe 3.0 – 4.0 (2014–2016) 

  • 2014: SAFe 3.0 introduced, introducing more emphasis on DevOps and faster, value-driven delivery.
  • 2016: SAFe 4.0 launched, introducing a dedicated “Value Stream” level for larger, complex systems and enhancing Kanban adoption. 

4. The Enterprise & DevOps Era: SAFe 4.5 – 4.6 (2017–2018) 

  • 2017: SAFe 4.5 released, emphasizing Lean Startup techniques, Lean UX, and faster, more flexible “Essential SAFe” configuration.
  • 2018: SAFe 4.6 updated to further incorporate the “Five Core Competencies of the Lean Enterprise”. 

5. Business Agility Era: SAFe 5.0 – 5.1 (2020–2021)

  • 2020: SAFe 5.0 (January) released, focusing on “Business Agility,” expanding agile principles beyond IT to the entire business (Human Resources, Finance, etc.).
  • 2021: SAFe 5.1 introduced, with enhanced focus on distributed teams, DevOps, and Accelerate metrics. 

6. AI & Continuous Learning Era: SAFe 6.0 (2023–Present) 

  • 2023: SAFe 6.0 (March) released, providing updated guidance on AI, Big Data, and Cloud technologies, while enhancing flow-based planning and accelerating value delivery.
  • 2024/2025: Focus on “AI-Empowered” SAFe, integrating artificial intelligence into the framework’s roles and ceremonies. 

SAFe Scaled Agile Framework summary and detailed historical timeline by era and year

PMP Project Management Professional summary and detailed historical timeline by era and year

Project Management Professional (PMP) history, as guided by the Project Management Institute (PMI), tracks the evolution from ancient craft systems to a modern, standardized profession combining predictive, agile, and hybrid approaches. Modern project management as a formal discipline emerged in the 1950s, with PMP certification officially launching in 1984. 

Summary of Project Management Eras

  • Pre-1950s (Craft Era): Large-scale construction (Pyramids, Great Wall) relied on master builders, intuitive planning, and heavy labor.
  • 1950s-1960s (Birth of Modern PM): Scheduling tools (CPM, PERT) and the Work Breakdown Structure (WBS) were developed for defense and construction.
  • 1969-1980s (Standardization Era): PMI was founded, and the PMP certification was introduced to create a shared professional language.
  • 1990s-2000s (Digital & Agile Era): Project software matured, the PMBOK Guide was published, and Agile techniques began reshaping software development.
  • 2010s-Present (Hybrid & AI Era): Focus on flexibility, stakeholder management, hybrid approaches, and AI integration. 

Detailed Historical Timeline

Ancient to Early 20th Century: Foundations

  • 2570 BC: Completion of the Great Pyramid of Giza, showing advanced resource planning.
  • 208 BC: Construction of the Great Wall of China, demonstrating large-scale logistical management.
  • 1917: Henry Gantt develops the Gantt Chart, a cornerstone of project scheduling. 

1950s-1960s: Birth of Modern Project Management 

  • 1957-1958: Development of key scheduling tools, Critical Path Method (CPM) and Program Evaluation Review Technique (PERT).
  • 1962: WBS approach mandated by the U.S. Department of Defense.
  • 1969: Project Management Institute (PMI) founded in Pennsylvania to standardize the profession. 

1970s-1980s: Professionalization and Certification 

  • 1975: Publication of The Mythical Man-Month by Fred Brooks, identifying software project risks.
  • 1984: First PMP certification exam administered by PMI.
  • 1986: Takeuchi and Nonaka introduce “Scrum” as a project management style.
  • 1987: First PMBOK Guide published as a white paper. 

1990s: PMBOK and Formalization 

2000s-2010s: Agile and Global Expansion 

  • 2001: Agile Manifesto written, emphasizing flexibility.
  • 2003: PMP exam revised to incorporate Agile techniques.
  • 2017: PMBOK 6th Edition released, integrating Agile and adaptive environments. 

2020s-Present: Modernization and AI

  • 2021: PMBOK 7th Edition released, shifting from process-based to principle-based standards.
  • 2024: PMI launches initiatives to incorporate Generative AI (PMIxAI) into project management. 

Key Evolution Trends

  1. From Craft to Science: Moving from intuitive, “master builder” approaches to structured, data-driven methodologies (PERT/CPM).
  2. From Fixed to Adaptive: Transitioning from rigid “waterfall” plans to iterative Agile and Hybrid approaches.
  3. Standardization: The PMP credential has shifted from solely construction/engineering focus to a global, cross-industry benchmark.
  4. Technology Integration: The rise of Artificial Intelligence (AI) and automated tools for risk management and scheduling.

PMP Project Management Professional summary and detailed historical timeline by era and year

PMBOK Project Management Body of Knowledge summary and detailed historical timeline by era and year

The PMBOK (Project Management Body of Knowledge) Guide, published by the Project Management Institute (PMI), is the globally recognized standard for project management best practices. Its evolution reflects the shift from rigid, industrial-era scheduling to flexible, value-driven, and hybrid methodologies. 

Summary of PMBOK Evolution

  • 1980s (Origins): PMI sought to standardize knowledge, starting with a white paper in 1983 and the first “Body of Knowledge” document in 1987.
  • 1996 (1st Edition): The first official PMBOK Guide was published, introducing a foundational process framework.
  • 2000s (Expansion): The 2nd (2000) and 3rd (2004) editions expanded on integration and finalized the standard for project management.
  • 2010s (Integration): The 4th (2008) and 5th (2012) editions added stakeholder management and aligned with enterprise needs. The 6th Edition (2017) formally bridged predictive (waterfall) and agile practices.
  • 2020s (Transformation): The 7th Edition (2021) marked a massive shift from process-based to principle-based, focusing on project outcomes rather than just outputs. The 8th Edition (2025) reintroduces practical, tailored process guidance alongside principles. 

Detailed Historical Timeline by Era and Year

Ancient Era to Pre-Modern (Before 1950s)

  • 2570 BC: Completion of the Great Pyramid of Giza, requiring complex organization, planning, and control.
  • 208 BC: Construction of the Great Wall of China, demonstrating massive, orchestrated labour management.
  • 1917: Henry Gantt developed the Gantt chart, a foundational scheduling tool still used today.

The Foundation Era (1950s – 1960s) 

  • 1956: American Association of Cost Engineers (now AACE International) formed.
  • 1957: Critical Path Method (CPM) invented by Dupont.
  • 1958: Program Evaluation and Review Technique (PERT) developed by the U.S. Navy for the Polaris missile program.
  • 1962: U.S. Dept of Defense mandated the Work Breakdown Structure (WBS) approach.
  • 1969: Project Management Institute (PMI) founded to promote the profession and set standards. 

The Formalization Era (1970s – 1980s) 

  • 1975: PROMPTII method created (later becoming PRINCE).
  • 1984: Dr. Eliyahu M. Goldratt introduced the Theory of Constraints (TOC) in his book “The Goal”.
  • 1986: Scrum named as a project management style.
  • 1987: First PMBOK Guide published by PMI as a white paper, attempting to standardize practices. 

The Standardization Era (1990s – 2000s)

  • 1991: Navy A-12 Avenger II Program cancelled due to poor performance detected by EVM.
  • 1996: 1st Edition of the PMBOK Guide released, establishing it as the foundational standard.
  • 1997: Critical Chain Project Management (CCPM) invented.
  • 1998: PMBOK recognized as a standard by ANSI (American National Standards Institute) and IEEE.
  • 2000: 2nd Edition of the PMBOK Guide released, adding more practical, in-depth material.
  • 2001: Agile Manifesto written, focusing on adaptability in software development.
  • 2004: 3rd Edition of the PMBOK Guide released, changing focus from “generally accepted” to “good practice”. 

The Modern Age & Agility Era (2010s – Present)

  • 2008: 4th Edition of the PMBOK Guide released, improving consistency and introducing new processes.
  • 2012: 5th Edition of the PMBOK Guide released, introducing the 10th Knowledge Area: Project Stakeholder Management.
  • 2017: 6th Edition of the PMBOK Guide released, incorporating Agile, Iterative, and Adaptive methodologies into every knowledge area.
  • 2021: 7th Edition of the PMBOK Guide released, a major shift towards a principle-based, value-delivery approach.
  • 2025: 8th Edition of the PMBOK Guide released, reintroducing tailored, practical processes along with principles.

PMBOK Project Management Body of Knowledge summary and detailed historical timeline by era and year