--- description: TELOS Feasibility Assessment โ€” 5 dimensi kelayakan proyek (Technical, Economic, Legal, Operational, Schedule) --- # /feasibility_study - TELOS Framework Assessment **Sumber:** TOPIC_004 > 04_feasibility_assessment.md (ยง4.1 TELOS Framework) --- ## ๐Ÿ“‹ Kapan Menggunakan Workflow Ini - Sebelum **commit resources** (budget, team) - Saat evaluasi **go/no-go decision** - Untuk **project proposal** kepada stakeholders - Sebelum **charter approval** --- ## ๐ŸŽฏ TELOS Overview ``` +-----------------------------------------------------------------+ | TELOS FRAMEWORK | | (5 Dimensions of Feasibility) | +-----------------------------------------------------------------| | | | +--------------+ | | | T - TECHNICAL | Can we build it? | | | | (Technology, skills, infrastructure) | | +--------------+ | | v | | +--------------+ | | | E - ECONOMIC | Can we afford it? | | | | (Cost, ROI, budget) | | +--------------+ | | v | | +--------------+ | | | L - LEGAL | Are we legally allowed? | | | | (Compliance, IP, regulations) | | +--------------+ | | v | | +--------------+ | | | O - OPERATIONAL| Will it fit our operations? | | | | (Workflow, adoption, maintenance) | | +--------------+ | | v | | +--------------+ | | | S - SCHEDULE | Can we deliver on time? | | | | (Timeline, deadlines, resources) | | +--------------+ | | | | โœ“ ALL PASS -> Project is FEASIBLE | | โœ— ANY FAIL -> Reconsider or mitigate | | | +-----------------------------------------------------------------+ ``` --- ## ๐Ÿ› ๏ธ STEP-BY-STEP WORKFLOW ### STEP 1: T - Technical Feasibility (15 min) **Key Question:** Bisakah kita build ini? **Checklist:** - [ ] Required tech stack exists & mature - [ ] Team has required skills (or can learn) - [ ] Infrastructure adequate - [ ] Integration with existing systems feasible - [ ] Architecture can handle expected load **Score:** \_\_\_/5 (1=Major blockers, 5=Fully capable) --- ### STEP 2: E - Economic Feasibility (15 min) **Key Question:** Apakah financially viable? **Checklist:** - [ ] Budget sufficient for development - [ ] ROI positive (target >100%) - [ ] Payback period acceptable (<2 years startup, <3 years enterprise) - [ ] Ongoing costs sustainable **Use:** `/cost_benefit` for detailed analysis **Score:** \_\_\_/5 (1=Not viable, 5=Highly profitable) --- ### STEP 3: L - Legal Feasibility (10 min) **Key Question:** Apakah legal & compliant? **Checklist:** - [ ] GDPR/CCPA compliance (if applicable) - [ ] No patent/trademark infringement - [ ] Open source licenses compatible - [ ] Industry regulations met (HIPAA, PCI-DSS, etc.) **Score:** \_\_\_/5 (1=Legal blockers, 5=Fully compliant) --- ### STEP 4: O - Operational Feasibility (10 min) **Key Question:** Apakah fit dengan operasi? **Checklist:** - [ ] Users can adopt this solution - [ ] Fits current workflows - [ ] Maintenance sustainable (team, skills) - [ ] Support processes defined **Score:** \_\_\_/5 (1=Major resistance, 5=Easy adoption) --- ### STEP 5: S - Schedule Feasibility (10 min) **Key Question:** Bisakah selesai tepat waktu? **Checklist:** - [ ] Timeline realistic for scope - [ ] Resources available when needed - [ ] Dependencies identified - [ ] Buffer included (20-30%) **Score:** \_\_\_/5 (1=Impossible timeline, 5=Comfortable buffer) --- ## ๐Ÿ“‹ TELOS ASSESSMENT TEMPLATE ```markdown ## TELOS FEASIBILITY ASSESSMENT ### Project: \***\*\_\_\*\*** ### Date: \***\*\_\_\*\*** --- | Dimension | Key Question | Score (1-5) | Notes | | ------------------- | ----------------- | ----------- | ----- | | **T** - Technical | Can we build it? | /5 | | | **E** - Economic | Can we afford it? | /5 | | | **L** - Legal | Legally allowed? | /5 | | | **O** - Operational | Fit operations? | /5 | | | **S** - Schedule | Deliver on time? | /5 | | | **TOTAL** | | /25 | | --- ### DECISION | Total Score | Recommendation | | ----------- | ----------------------------------- | | 20-25 | โœ… PROCEED โ€” Project is feasible | | 15-19 | ๐ŸŸก CONDITIONAL โ€” Address weak areas | | 10-14 | ๐ŸŸ  HIGH RISK โ€” Significant concerns | | <10 | โŒ DO NOT PROCEED โ€” Not feasible | **Final Decision:** โ–ก PROCEED โ–ก CONDITIONAL โ–ก DO NOT PROCEED **Key Risks/Mitigations:** 1. 2. 3. **Sign-off:** \***\*\_\_\*\*** Date: \***\*\_\_\*\*** ``` --- ## ๐Ÿ’ก Quick TELOS Checklist | Dimension | Pass Criteria | | ------------------- | ------------------------------- | | **T** - Technical | Technology & skills available | | **E** - Economic | ROI positive, budget sufficient | | **L** - Legal | No legal blockers | | **O** - Operational | Users can adopt | | **S** - Schedule | Timeline realistic | --- ## ๐Ÿ“ Output File **Setelah workflow selesai, AI WAJIB generate file markdown:** **Path:** `AI-Agent/Output/Planning/[ProjectName]/06_feasibility_report.md` **Template Output:** ```markdown # [Project Name] - Feasibility Report **Date:** [YYYY-MM-DD] **Framework:** TELOS **Recommendation:** [PROCEED / CONDITIONAL / DO NOT PROCEED] --- ## TELOS Assessment Summary | Dimension | Key Question | Score | Notes | | ------------------- | ----------------- | -------- | ------- | | **T** - Technical | Can we build it? | X/5 | [Notes] | | **E** - Economic | Can we afford it? | X/5 | [Notes] | | **L** - Legal | Legally allowed? | X/5 | [Notes] | | **O** - Operational | Fit operations? | X/5 | [Notes] | | **S** - Schedule | Deliver on time? | X/5 | [Notes] | | **TOTAL** | | **X/25** | | --- ## Detailed Analysis ### T - Technical Feasibility (Score: X/5) - [x] Required tech stack exists & mature - [ ] Team has required skills - [ ] Infrastructure adequate - [ ] Integration feasible **Key Risks:** [Description] **Mitigation:** [Action] --- ### E - Economic Feasibility (Score: X/5) - [x] Budget sufficient - [ ] ROI positive (>100%) - [ ] Payback period acceptable - [ ] Ongoing costs sustainable **Budget Summary:** - Development: $X - Monthly costs: $X/mo - Expected ROI: X% --- ### L - Legal Feasibility (Score: X/5) - [x] GDPR/CCPA compliance - [ ] No IP infringement - [ ] Licenses compatible - [ ] Industry regulations met **Legal Notes:** [Description] --- ### O - Operational Feasibility (Score: X/5) - [x] Users can adopt - [ ] Fits current workflows - [ ] Maintenance sustainable **Adoption Notes:** [Description] --- ### S - Schedule Feasibility (Score: X/5) - [x] Timeline realistic - [ ] Resources available - [ ] Buffer included (20-30%) **Timeline:** [X] weeks/months --- ## Recommendation | Score Range | Meaning | This Project | | ----------- | ----------------- | ------------ | | 20-25 | โœ… PROCEED | | | 15-19 | ๐ŸŸก CONDITIONAL | | | 10-14 | ๐ŸŸ  HIGH RISK | | | <10 | โŒ DO NOT PROCEED | | **Final Recommendation:** [PROCEED / CONDITIONAL / DO NOT PROCEED] **Key Conditions (if applicable):** 1. [Condition 1] 2. [Condition 2] --- ## Next Steps - [ ] Proceed to /tech_stack_eval for tech decision - [ ] Complete /cost_benefit for detailed ROI - [ ] Create /create_charter ``` --- ## ๐Ÿ“š Referensi - MindTools, Project Management Body of Knowledge - TOPIC_004/04_feasibility_assessment.md (Lines 16-70)