The Ihsan Agile Guide: Embedding Islamic Values in Agile Delivery

Ihsan Agile is an open-source Islamic Agile framework intentionally designed for modular adoption, overlaying existing Agile methods (Scrum, Kanban, SAFe) with principles drawn from The Qur'an and Sunnah. Teams can try a single practice, adopt one role, or implement the complete framework, whatever serves their context. No comprehensive adoption required. It embeds the Four Pillars (niyyah (intention), iḥsān (excellence with God-consciousness), maṣlaḥah (public benefit), and ṣidq (truthfulness)), alongside Five Core Principles (taqwā, Stewardship /amānah & khilāfah, shūrā, Service & Justice /ʿibādah & ʿadl, and tazkiyah) into team workflows and product decisions, ensuring that Islamic values become operational in everyday delivery practices. This framework helps Muslim-led teams align operational decisions with Islamic ethics through two complementary roles: Ihsan Agile Facilitator (IAF): Embeds ethical consciousness into how teams work, enriching Sprint Planning with Niyyah Check-ins, Retrospectives with Muhāsabah Reflection, and Definition of Done with ethical completeness criteria. Ihsan Agile Product Steward (IAPS): Extends Islamic values into what teams build and how technical decisions are made, reframing "technical debt" as "technical disclosure," ensuring genuine stakeholder consultation (shūrā), prioritising public benefit (maṣlaḥah), and maintaining transparent stewardship (amānah, khilāfah, and ṣidq) throughout the product lifecycle. New in Version 1.2: Ṣidq (Truthfulness) added as Fourth Pillar: Elevates honest communication and technical disclosure to foundational framework status, emphasising that transparency about capabilities, constraints, and limitations is not optional but structural to Islamic delivery practices. Psychological safety positioned as Islamic requirement: Demonstrates that ṣidq (truthfulness) requires agency, team members cannot speak honestly about blockers, risks, or constraints in environments that inhibit openness. Agile's emphasis on psychological safety and self-organising teams creates the structural conditions for practising ṣidq. Shariah consultation boundaries clarified: New section "Recognising When to Seek Shariah Consultation" distinguishes operational framework guidance from questions requiring scholarly expertise, clarifying both the framework's operational scope and appropriate pathways to scholarly guidance when fiqh questions arise. Refined interdependence relationships: Updated "How the Four Pillars Work Together" section shows how niyyah, iḥsān, maṣlaḥah, and ṣidq reinforce each other, with particular emphasis on how maṣlaḥah (beneficial outcomes) and ṣidq (truthful means) work together to ensure teams pursue genuine stakeholder benefit through transparent communication. Enhanced modularity guidance: Expanded practical guidance on modular adoption with "What You Don't Need to Do" section, emphasising that teams can benefit from individual practices without comprehensive framework implementation. Continued from Version 1.1: The following features introduced in v1.1 are carried forward and extended in v1.2: Ihsan Agile Product Steward (IAPS) role addressing critical gaps in conventional product ownership Technical Uncertainty Register (TUR) transforming hidden technical constraints into disclosed commitments that build stakeholder trust Gharar Assessment Checklist evaluating when technical shortcuts require stakeholder disclosure and consent Critical analysis showing how conventional technical debt frameworks create gharar (harmful uncertainty) through non-disclosure and normalise riba-based thinking through interest metaphors Practical guidance on technical disclosure as trust-building: teams take shortcuts for legitimate reasons; the question is whether those shortcuts remain hidden liabilities or become transparent realities Stakeholder Barakah Reviews ensuring genuine consultation with those affected by technical decisions Implementation guidance for Scrum, Kanban, and SAFe with phased adoption pathways Concrete worked scenarios and ready-to-use templates for TUR, Gharar Assessments, Ethical Definitions of Done, and Stakeholder Barakah Reviews May our systems be honest about their limits, not just efficient in their outputs.