From ba79de989695fdcf52919f11e0051faf38d8db20 Mon Sep 17 00:00:00 2001 From: krishnahacks26 Date: Sun, 17 May 2026 10:48:26 +0530 Subject: [PATCH] docs: Add detailed Introduction to Agile chapter with examples --- app/agile/content/chapter1.tsx | 132 +++++++++++++++++++++++++++++++++ 1 file changed, 132 insertions(+) create mode 100644 app/agile/content/chapter1.tsx diff --git a/app/agile/content/chapter1.tsx b/app/agile/content/chapter1.tsx new file mode 100644 index 0000000..2e5bd5c --- /dev/null +++ b/app/agile/content/chapter1.tsx @@ -0,0 +1,132 @@ +export const Ch1Content = () => { + return ( +
+

+ Agile is a modern approach to + software development that focuses on delivering small, working pieces of + software frequently, rather than delivering everything at once after a + long time. It encourages teams to collaborate closely, adapt to changes, + and continuously improve their process. +

+ +
+

What is Agile?

+
    +
  • + Iterative Development: Work + is divided into small cycles called iterations. Each iteration + produces a working piece of software. For example, instead of + building an entire app in 1 year, you build and release small + features every 2 weeks. +
    • +
  • + Customer Collaboration: The + customer is involved throughout the project, not just at the + beginning and end. This ensures the final product matches their + actual needs. +
    • +
  • + Responding to Change: Agile + welcomes changing requirements even late in development. If a + customer changes their mind, the team adapts rather than sticking + to an outdated plan. +
    • +
  • + Working Software: The + primary measure of progress is working software, not documents or + reports. +
    • +
+
+ +
+

Agile Manifesto — 4 Core Values

+

+ In 2001, 17 experienced software developers came together and wrote + the Agile Manifesto — a document that defines the core values and + principles of Agile development. +

+
    +
  • + Individuals & Interactions{" "} + over Processes & Tools — People and communication matter more than + following strict processes or using specific tools. +
    • +
  • + Working Software over + Comprehensive Documentation — A working product is more valuable + than hundreds of pages of documentation. +
    • +
  • + Customer Collaboration over + Contract Negotiation — Work closely with customers throughout, + rather than just following a fixed contract. +
    • +
  • + Responding to Change over + Following a Plan — Be flexible and adapt to changes rather than + rigidly following an outdated plan. +
    • +
+
+ +
+

12 Agile Principles

+

+ The Agile Manifesto also includes 12 principles that guide Agile + teams in their day-to-day work: +

+
    +
  • Satisfy the customer through early and continuous delivery of working software
    • +
  • Welcome changing requirements, even late in development
    • +
  • Deliver working software frequently, from every few weeks to every few months
    • +
  • Business people and developers must work together daily
    • +
  • Build projects around motivated individuals and trust them to get the job done
    • +
  • Face-to-face conversation is the most efficient way to share information
    • +
  • Working software is the primary measure of progress
    • +
  • Maintain a sustainable, constant pace of development
    • +
  • Continuous attention to technical excellence enhances agility
    • +
  • Simplicity — maximizing the amount of work not done — is essential
    • +
  • The best architectures emerge from self-organizing teams
    • +
  • Regularly reflect on how to become more effective and adjust accordingly
    • +
+
+ +
+

Agile vs Waterfall

+

+ Before Agile, most teams used the{" "} + Waterfall model — a linear + approach where each phase (requirements, design, development, testing) + is completed before moving to the next. Here is how they differ: +

+
    +
  • + Flexibility: Waterfall has + fixed requirements — Agile welcomes change at any stage +
    • +
  • + Delivery: Waterfall delivers + everything at the end — Agile delivers working software every few + weeks +
    • +
  • + Customer Involvement:{" "} + Waterfall involves customers only at start and end — Agile involves + them throughout +
    • +
  • + Risk: Waterfall has high + risk as problems are found late — Agile catches issues early + through frequent releases +
    • +
  • + Example: Building a house + uses Waterfall (fixed plan). Building an app uses Agile (features + added gradually based on feedback) +
    • +
+
+
+ ); +}; \ No newline at end of file