feat: Add Agile Methodology documentation

[Krishna-Sah26]

Related Issue

Fixes #18

---

Description

Added Agile Methodology as a new subject with 5 chapters:

• Chapter 0: Course Outline
• Chapter 1: Introduction to Agile & Agile Manifesto
• Chapter 2: Scrum Framework
• Chapter 3: Kanban
• Chapter 4: User Stories & Estimation

---

Type of Change

• Bug fix
• New feature
• Documentation update
• UI/UX improvement
• Refactor

---

Screenshots / Demo

[Add localhost:3000/agile/ch0 ka screenshot]

---

How Has This Been Tested?

Tested locally using npm run dev.
Visited localhost:3000/agile/ch0 through ch4.
All chapters are loading correctly with proper navigation.

---

Checklist

• My code follows the project structure and conventions
• I have tested the changes locally
• I have linked the related issue properly
• I have added screenshots where applicable
• No existing functionality was broken

---

AI Usage

• I have used AI tools (Claude), and I have reviewed,
  verified and understood all generated code/content
  before submitting this PR

If AI tools were used, briefly explain how:

Used Claude for documentation drafting and code
structure guidance. All content reviewed and verified.

---

Additional Notes

More chapters can be added in future PRs as per
Admin's suggestion to keep PRs small and focused.

[vercel]

@Krishna-Sah26 is attempting to deploy a commit to the PushkarScripts Team on Vercel.

A member of the Team first needs to authorize it.

[pushkarscripts]

Thanks for the contribution. The overall project structure and integration looks good so far.

However, the documentation currently feels more like short revision notes/keyword summaries rather than detailed beginner-friendly learning material.

Before this can be reviewed further, please:

• split the contribution into smaller module/topic-wise PRs instead of covering all chapters at once
• add more detailed explanations and practical examples wherever required
• focus more on teaching/explaining concepts instead of only listing points

The current structure is fine overall. The main improvements needed are around content depth and reviewability.

[Krishna-Sah26]

Thank you for the feedback! I will close this PR and submit smaller, more detailed PRs chapter by chapter. Will improve content depth as suggested.

…

On Sat, May 16, 2026 at 12:41 AM Pushkar Singh ***@***.***> wrote: *pushkarscripts* left a comment (pushkarscripts/openCSE#24) <#24 (comment)> Thanks for the contribution. The overall project structure and integration looks good so far. However, the documentation currently feels more like short revision notes/keyword summaries rather than detailed beginner-friendly learning material. Before this can be reviewed further, please: - split the contribution into smaller module/topic-wise PRs instead of covering all chapters at once - add more detailed explanations and practical examples wherever required - focus more on teaching/explaining concepts instead of only listing points The current structure is fine overall. The main improvements needed are around content depth and reviewability. — Reply to this email directly, view it on GitHub <#24 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BR4BEDISVS45FETPQAWNFZT425TWNAVCNFSM6AAAAACY7KAIFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DINRSGY2DGNRWGI> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>