https://wiki.tintu.in/index.php?action=history&feed=atom&title=Agile_Scrum 2026-04-16T12:07:57Z Revision history for this page on the wiki MediaWiki 1.42.3 https://wiki.tintu.in/index.php?title=Agile_Scrum&diff=2&oldid=prev 2024-10-29T11:22:20Z

<p>Created page with &quot;== Agile == &#039;&#039;&#039;Agile&#039;&#039;&#039; is a project management principle focused on completing projects efficiently through continuous delivery and early access. This approach enables teams to gather feedback and adapt to rapid changes. Agile is most commonly applied in &#039;&#039;&#039;software development&#039;&#039;&#039;. === Key Agile Methodologies === Agile can be implemented in different ways, with the two most popular being &#039;&#039;&#039;Scrum&#039;&#039;&#039; and &#039;&#039;&#039;Kanban&#039;&#039;&#039;. Each approach supports Agile principles but differ...&quot;</p> <p><b>New page</b></p><div>== Agile ==<br /> <br /> &#039;&#039;&#039;Agile&#039;&#039;&#039; is a project management principle focused on completing projects efficiently through continuous delivery and early access. This approach enables teams to gather feedback and adapt to rapid changes. Agile is most commonly applied in &#039;&#039;&#039;software development&#039;&#039;&#039;.<br /> <br /> === Key Agile Methodologies ===<br /> <br /> Agile can be implemented in different ways, with the two most popular being &#039;&#039;&#039;Scrum&#039;&#039;&#039; and &#039;&#039;&#039;Kanban&#039;&#039;&#039;. Each approach supports Agile principles but differs in methodology:<br /> <br /> ==== 1. Scrum ====<br /> * &#039;&#039;&#039;Sprint-based&#039;&#039;&#039;: Scrum uses structured timeframes, known as &#039;&#039;&#039;Sprints&#039;&#039;&#039;, during which teams plan, develop, and deliver specific application features.<br /> * &#039;&#039;&#039;Iteration-focused&#039;&#039;&#039;: Teams work in cycles, completing iterations at regular intervals and reassessing priorities at the end of each Sprint.<br /> <br /> ==== 2. Kanban ====<br /> * &#039;&#039;&#039;Continuous workflow&#039;&#039;&#039;: Unlike Scrum, Kanban does not operate in fixed-duration sprints; instead, work progresses continuously.<br /> * &#039;&#039;&#039;Task visualization&#039;&#039;&#039;: Kanban emphasizes visualizing tasks and managing workflow without set time restrictions, allowing for continuous adjustments as tasks move across different stages.<br /> <br /> === Summary of Differences ===<br /> <br /> {| class=&quot;wikitable&quot;<br /> |+ &#039;&#039;&#039;Scrum vs Kanban&#039;&#039;&#039;<br /> ! Aspect<br /> ! Scrum<br /> ! Kanban<br /> |-<br /> | &#039;&#039;&#039;Timeframe&#039;&#039;&#039;<br /> | Sprint-based (time-boxed)<br /> | Continuous (no set duration)<br /> |-<br /> | &#039;&#039;&#039;Focus&#039;&#039;&#039;<br /> | Iterative delivery<br /> | Ongoing workflow management<br /> |-<br /> | &#039;&#039;&#039;Process&#039;&#039;&#039;<br /> | Planned iterations<br /> | Task-based progress tracking<br /> |}<br /> <br /> === Advantages of Agile ===<br /> <br /> The Agile approach promotes:<br /> * &#039;&#039;&#039;Early and continuous delivery&#039;&#039;&#039; of functional software.<br /> * &#039;&#039;&#039;Adaptability&#039;&#039;&#039; to change through iterative cycles.<br /> * &#039;&#039;&#039;Customer satisfaction&#039;&#039;&#039; through consistent feedback integration.</div>

Tintucraju