Editing Agile Methodology (section)

= Agile Methodology =
A set of iterative and collaborative approaches to **software development** and **project management**, emphasizing adaptability, customer feedback, and incremental delivery.

== Remembering (Knowledge / Recall) 🧠 ==
Foundational terms, actors, and artifacts associated with agile practice.

=== Core terminology & definitions ===
* '''[https://wikipedia.org/wiki/Agile_software_development Agile software development]''' – A family of methods focused on iterative planning, continuous delivery, and cross-functional teamwork.
* '''[https://wikipedia.org/wiki/Scrum_(software_development) Scrum]''' – A widely used agile framework structured around sprints, roles, and ceremonies.
* '''[https://wikipedia.org/wiki/Kanban Kanban]''' – A flow-based method emphasizing visualization and work-in-progress limits.
* '''Agile Manifesto''' – Statement of values and principles published in 2001.
* '''Sprint''' – A short, time-boxed development cycle.

=== Key components / actors / elements ===
* '''Roles''' – Product Owner, Scrum Master, Development Team.
* '''Artifacts''' – Product Backlog, Sprint Backlog, Increment.
* '''Ceremonies''' – Daily Stand-up, Sprint Planning, Review, Retrospective.
* '''Stakeholders''' – Customers, end-users, product sponsors.

=== Canonical models, tools, or artifacts ===
* '''[https://wikipedia.org/wiki/User_story User stories]''' – Brief, user-focused requirements.
* '''Task boards / Kanban boards''' – Visual workflow representation.
* '''Burn-down charts''' – Remaining work over time.

=== Typical recall-level facts ===
* Origin: Early 2000s, formalized by the Agile Manifesto.
* Domain: Software engineering, project management.
* Common examples: Scrum sprints, Kanban flow systems.

----

== Understanding (Comprehension) 📖 ==
Conceptual relationships and operational foundations.

=== Conceptual relationships & contrasts ===
* Agile vs. traditional '''[https://wikipedia.org/wiki/Waterfall_model Waterfall model]''' – iterative vs. linear sequencing.
* Relationship to lean thinking and just-in-time flow.
* Part of broader adaptive methodologies including XP and Crystal.

=== Core principles & paradigms ===
* Continuous customer collaboration.
* Emphasis on working software over comprehensive documentation.
* Adaptive planning with short feedback loops.
* Empowered, cross-functional teams.

=== How it works (high-level) ===
* '''Inputs''' – Product vision, backlog items, stakeholder needs.
* '''Processes''' – Iterative planning → development → review → retrospective.
* '''Outputs''' – Incremental features, feedback-driven backlog updates.

=== Roles & perspectives ===
* '''Product Owner''' – Prioritizes customer value.
* '''Team members''' – Commit to achievable sprint goals.
* '''Scrum Master / facilitators''' – Remove impediments, ensure process health.
* '''Stakeholders''' – Provide ongoing feedback and validation.

----

== Applying (Use / Application) 🛠️ ==
Concrete usage patterns and workflows.

=== "Hello, World" example ===
* Create a minimal backlog with a single user story.
* Run a short planning session.
* Execute a 1–2 day mini-sprint.
* Demo the result and capture feedback.

=== Core task loops / workflows ===
* Groom backlog → Plan sprint → Execute → Review → Retrospect.
* Daily coordination through stand-ups.
* Continuous refinement based on stakeholder input.

=== Frequently used actions / methods / techniques ===
* Writing user stories (“As a user… I want…”).
* Breaking stories into tasks.
* Estimating via planning poker.
* Maintaining a visible board.
* Running retrospectives.

=== Real-world use cases ===
* Software feature development in cross-functional teams.
* Managing marketing campaign cycles.
* Rapid prototyping in startups.
* Complex systems requiring incremental risk mitigation.

----

== Analyzing (Break Down / Analysis) 🔬 ==
Structure, trade-offs, and diagnostic insights.

=== Comparative analysis ===
* vs. Waterfall: flexibility vs. predictability.
* vs. Lean: similar flow focus, but lean stresses waste elimination.
* vs. DevOps: agile focuses on development rhythms; DevOps extends into deployment/operations.

=== Structural insights ===
* Iteration as fundamental unit of planning.
* Dual-loop structure: delivery loop (sprint) + improvement loop (retro).
* Dependency on empowered teams and fast feedback.

=== Failure modes & root causes ===
* Cargo-cult agile: ceremony without mindset.
* Overloaded backlogs with unclear prioritization.
* Excessive work-in-progress blocking flow.
* Inconsistent stakeholder participation.

=== Troubleshooting & observability ===
* Monitor lead time, cycle time, throughput.
* Inspect sprint burndown for volatility.
* Listen for recurring impediments in stand-ups.
* Use retro action items as health indicators.

----

== Creating (Synthesis / Create) 🏗️ ==
Designing and extending agile practices.

=== Design patterns & best practices ===
* Split large stories into INVEST-compliant items.
* Keep WIP low to maximize flow.
* Establish clear Definition of Done.
* Use lightweight documentation aligned with user needs.

=== Integration & extension strategies ===
* Combine with DevOps pipelines for continuous delivery.
* Pair with lean portfolio management for strategic alignment.
* Integrate UX research cycles into sprints.
* Adapt ceremonies for distributed teams.

=== Security, governance, or ethical considerations ===
* Incorporate secure coding tasks within backlogs.
* Ensure compliance stories are visible and prioritized.
* Protect team well-being through sustainable pace.

=== Lifecycle management strategies ===
* Evolve processes through regular retrospectives.
* Adjust sprint length as team maturity changes.
* Migrate legacy processes incrementally to avoid disruption.

----

== Evaluating (Judgment / Evaluation) ⚖️ ==
Assessing effectiveness and fit.

=== Evaluation frameworks & tools ===
* Team health checks and maturity models.
* Velocity trends (used cautiously).
* Flow metrics: cycle time, throughput, WIP.
* Stakeholder satisfaction surveys.

=== Maturity & adoption models ===
* Often mainstream in software engineering.
* Scaled variants such as SAFe, LeSS, and Scrum@Scale.
* Barriers: organizational inertia, unclear product ownership.

=== Key benefits & limitations ===
* Benefits: adaptability, early value, reduced risk.
* Limitations: requires engaged stakeholders, disciplined teams.
* Weak in environments demanding fixed long-term scope up front.

=== Strategic decision criteria ===
* Choose agile when requirements evolve and feedback is frequent.
* Avoid when heavy regulatory constraints require extensive upfront detail.
* Consider hybrid models for mixed-context projects.

=== Holistic impact analysis ===
* Encourages transparency and autonomy.
* Can reshape organizational culture toward experimentation.
* Future trajectory: stronger integration with DevOps, AI-assisted planning, and continuous discovery.

----

[[Category:Software Development]]
[[Category:Project Management]]
[[Category:Agile Methods]]