Agile Planning & Project Management

A comprehensive demonstration of Agile project management methodologies, featuring sprint planning, Kanban boards, and issue tracking using GitHub Projects.

---

📌 Project Overview

This repository serves as a practical implementation of Agile Software Development practices. It demonstrates how to effectively organize, track, and manage a software project from inception to delivery using Epics, User Stories, and a Kanban workflow.

By applying industry-standard project management frameworks, this project highlights the ability to break down complex features into manageable iterations, assign story points, and track progress transparently.

---

🏗️ Agile Workflow & Architecture

graph LR
    subgraph NewIssues ["🆕 New Issues (0)"]
        direction TB
        E1[/"(No Active Issues)"/]
    end

    subgraph Icebox ["🧊 Icebox (2)"]
        direction TB
        I1["#2 Must allow multiple counters"]
        I2["#6 Need the ability to remove counter"]
    end

    subgraph ProductBacklog ["📋 Product Backlog (3)"]
        direction TB
        P1["#8 Completing Deploy Service to the Cloud<br>(technical debt)"]
        P2["#4 Counters can be reset<br>(enhancement)"]
        P3["#7 Need the ability to update a counter to a new value<br>(enhancement)"]
    end

    subgraph SprintBacklog ["🏃 Sprint Backlog (0)"]
        direction TB
        E2[/"(No Active Issues)"/]
    end

    subgraph InProgress ["🚧 In Progress (0)"]
        direction TB
        E3[/"(No Active Issues)"/]
    end

    subgraph ReviewQA ["👀 Review/QA (0)"]
        direction TB
        E4[/"(No Active Issues)"/]
    end

    subgraph Done ["✅ Done (0)"]
        direction TB
        E5[/"(No Active Issues)"/]
    end

    subgraph Closed ["🏁 Closed (3)"]
        direction TB
        C1["#5 Deploy service to the cloud<br>(technical debt)"]
        C2["#3 Must persist counter across restarts<br>(enhancement)"]
        C3["#1 Need a service that has a counter<br>(enhancement)"]
    end

    NewIssues --> Icebox --> ProductBacklog --> SprintBacklog --> InProgress --> ReviewQA --> Done --> Closed

    %% Custom Status Label Colors
    classDef techDebt fill:#fff3cd,stroke:#856404,stroke-width:2px,color:#000;
    classDef enhancement fill:#d4edda,stroke:#155724,stroke-width:2px,color:#000;
    classDef empty fill:#f8f9fa,stroke:#ced4da,stroke-width:2px,stroke-dasharray: 5 5,color:#6c757d;

    class P1,C1 techDebt;
    class P2,P3,C2,C3 enhancement;
    class E1,E2,E3,E4,E5 empty;

Loading

🎯 Key Methodologies Implemented

• Epics: Large-scale features broken down into smaller components.
• User Stories: End-user requirements formatted as "As a [role], I want [feature] so that [benefit]."
• Story Pointing: Estimating task complexity and effort.
• Kanban Board: Visual tracking of tasks moving from To Do ➔ In Progress ➔ Review ➔ Done.

---

🛠️ Skills & Tools Demonstrated

Category	Skill/Tool	Purpose
Project Management	Agile (Scrum/Kanban)	Framework for iterative software delivery
Tracking System	GitHub Projects / Issues	Creating and managing project backlogs
Documentation	Markdown	Writing clear acceptance criteria and issue templates
Planning	Sprint Planning	Organizing tasks into time-boxed iterations

---

📁 Repository Structure

agile-project-management/
├── .github/
│   └── ISSUE_TEMPLATE/    # Custom GitHub issue templates for user stories and bugs
├── demo.png               # Visual proof screenshot of the active Kanban board
├── user-story.md          # Markdown template/documentation for writing user stories
└── README.md              # Main project documentation

---

⚙️ Project Execution & Steps

1. Defining the Product Backlog

• Created high-level Epics to define major deliverables.
• Deconstructed Epics into actionable User Stories.
• Added detailed Acceptance Criteria to ensure quality and clear definitions of "Done."

2. Setting up the Kanban Board

• Initialized a project board with automated columns (New, Backlog, Ready, In Progress, Done).
• Linked the GitHub repository to the project board to automate issue tracking.

3. Sprint Planning & Execution

• Assigned priority levels and labels (e.g., enhancement, bug, documentation) to tasks.
• Moved tasks through the workflow to simulate an active development sprint.

---

📸 Workflow Verification

Note: Below is a snapshot of the active Zenhub Kanban board demonstrating the organized Agile workflow and issue tracking from Epics to closure.

---

📄 License

This project is licensed under the MIT License - see the LICENSE file for details.

👤 Author

Hamed Payanda

• GitHub: @HAMED-PAYANDA
• Completed as part of the IBM Full-Stack Software Developer Professional.