| Name | Use | Description |
| SCRUM | Agile Framework | Structured, iterative framework using time-boxed sprints (1–4 weeks) to deliver incremental product updates. |
| Kanban | Visual Workflow Management | Continuous-flow method emphasizing visual boards, work-in-progress (WIP) limits, and bottleneck reduction. |
| Jira | Issue & Project Tracking Tool | Enterprise platform for planning, tracking, and managing Agile projects, backlog grooming, and release cycles. |
| Git | Distributed Version Control System | Source control system for tracking code changes, enabling parallel branch development, and managing merges. |
| CI/CD | Automation Pipeline Technique | Continuous Integration and Continuous Deployment practice to automate code building, testing, and production deployment. |
| Scrumban | Hybrid Methodology | Combines the structured sprint iteration of Scrum with the continuous flow and WIP limits of Kanban. |
| Extreme Programming (XP) | Agile Engineering Practice | Software-focused Agile method prioritizing frequent releases, pair programming, unit testing, and refactoring. |
| Lean Project Management | Process Optimization Strategy | Focuses on maximizing customer value while eliminating waste (muda) in workflows and resource usage. |
| Waterfall | Traditional PM Methodology | Sequential, linear project approach divided into distinct phases (Requirements, Design, Implementation, Testing, Maintenance). |
| PRINCE2 | Structured PM Framework | Process-driven methodology focusing on business justification, clear roles, and stage-by-stage management control. |
| PMBOK (PMI) | Standardized PM Guide | Comprehensive framework structured around knowledge areas (Scope, Schedule, Cost, Quality, Risk, Stakeholders). |
| Objectives & Key Results (OKRs) | Strategic Goal-Setting Strategy | Alignment framework defining ambitious goals (Objectives) alongside measurable outcomes (Key Results). |
| Key Performance Indicators (KPIs) | Performance Measurement Technique | Quantitative metrics used to track project performance, team efficiency, and business health. |
| Confluence | Knowledge & Documentation Tool | Team workspace for centralizing project documentation, technical specs, meeting notes, and architecture diagrams. |
| Trello | Lightweight PM Tool | Simple, visual card-based Kanban tool for task tracking and personal/team workflow management. |
| Asana | Cross-Team Work Management Tool | Flexible project platform offering task tracking, timeline views, workloads, and dependency mapping. |
| Monday.com | Visual Work OS Platform | Customizable workflow platform for managing operations, projects, automations, and resource allocation. |
| ClickUp | Productivity & PM Suite | Multi-functional workspace combining task management, doc editing, sprint planning, and time tracking. |
| Azure DevOps | Lifecycle & PM Tool | Microsoft cloud suite integrating boards, repos, CI/CD pipelines, and artifact repositories. |
| GitHub Actions | CI/CD & Automation Strategy | Integrated workflow automation tool directly inside GitHub repositories for builds, tests, and deployments. |
| Gantt Charts | Timeline & Dependency Technique | Bar chart visualization illustrating project schedules, work packages, task durations, and critical paths. |
| Critical Path Method (CPM) | Scheduling & Analysis Technique | Step-by-step technique to identify the longest sequence of dependent tasks determining the minimum project duration. |
| Work Breakdown Structure (WBS) | Scope Management Technique | Hierarchical decomposition of total project scope into smaller, manageable components and deliverables. |
| User Stories | Requirement Definition Technique | Short descriptions of features written from the end-user perspective (“As a [user], I want [goal] so that [reason]”). |
| Planning Poker (Fibonacci Estimation) | Consensus-Based Estimation Technique | Gamified technique using Fibonacci cards ($1, 2, 3, 5, 8, \dots$) to estimate relative effort or story points. |
| Sprint Planning | Scrum Ceremony | Time-boxed meeting to select backlog items and establish the target scope for an upcoming sprint. |
| Daily Standup / Daily Scrum | Agile Alignment Ceremony | Brief daily meeting (15 min) where team members align on progress, daily targets, and blockers. |
| Sprint Review / Demo | Inspection & Stakeholder Ceremony | End-of-sprint meeting to present working increment to stakeholders and gather feedback. |
| Sprint Retrospective | Continuous Improvement Ceremony | Team-focused meeting post-sprint to discuss successes, bottlenecks, and actionable process improvements. |
| Burndown / Burnup Charts | Progress Tracking Technique | Visual charts tracking work remaining or completed over time to predict sprint/release completion. |
| Velocity Tracking | Metric & Forecasting Technique | Measures the amount of work (story points) a team completes per sprint to improve future estimation. |
| Definition of Done (DoD) | Quality Assurance Technique | Explicit list of criteria (tests, documentation, code review) required before a task is marked complete. |
| Definition of Ready (DoR) | Requirements Criteria Technique | Clear prerequisites a backlog item must meet before being pulled into an active sprint. |
| Continuous Integration (CI) | Software Development Strategy | Automated practice where developers merge code frequently into a central repo, triggering auto-builds and tests. |
| Trunk-Based Development | Git Branching Strategy | Version control strategy where developers merge small updates frequently into a single main branch. |
| Gitflow | Git Branching Strategy | Branching model utilizing separate long-lived branches (main, develop, feature, release, hotfix). |
| Risk Matrix & Analysis | Risk Management Technique | Visual assessment tool mapping the probability and impact of potential risks to prioritize mitigation strategies. |
| RAID Log | Risk & Governance Tracking Tool | Structured log tracking Risks, Assumptions, Issues, and Dependencies throughout the project lifecycle. |
| Root Cause Analysis (5 Whys) | Problem-Solving Technique | Iterative interrogative technique used to dig past symptoms to the underlying cause of a problem. |
| RACI Matrix | Responsibility Assignment Technique | Chart defining team roles across tasks: Responsible, Accountable, Consulted, and Informed. |