For Enterprise Architects involved in SAP implementation projects, the ability to structure and prioritize vast volumes of customer requirements is a critical success factor. Within the TOGAF® ADM, Requirements Management mandates prioritization based on business value and impact on organizational goals.
This article explains how to apply TOGAF-based requirements prioritization and demonstrates practical use cases in SAP S/4HANA implementation projects.
TOGAF® Requirements Management Fundamentals
The Requirements Management phase in TOGAF® ADM is a continuous, central activity that spans all phases of architecture development.
Its core objectives include:
- Stakeholder alignment
- Requirements collection and documentation
- Traceability establishment
- Prioritization
- Change management
Key Principles for Requirements Prioritization
TOGAF® recommends structured evaluation based on the following criteria:
- Business value: Contribution to business outcomes
- Business or technical risk: Impact of failure
- Implementation difficulty: Complexity and feasibility
- Likelihood of success: Potential for quick wins
- Regulatory compliance: Legal obligations and deadlines
- Dependency relationships: Links to other high-value requirements
- Urgency: Time sensitivity
- Stakeholder agreement: Level of consensus
Using these criteria enables objective and data-driven prioritization.
MoSCoW Method for SAP Projects
The MoSCoW method is widely used in TOGAF®:
- Must Have: Critical for system functionality (e.g., core SAP processes, compliance)
- Should Have: Important but not mandatory
- Could Have: Optional enhancements
- Won’t Have: Deferred to future releases
SAP S/4HANA Case Study (Automotive Supplier)
Phase 1: Strategic Requirements
Business goal: Reduce product release cycle from 6 months to 2 weeks.
Prioritized requirements:
Must Have:
- Global product master data platform
- Standard SAP S/4HANA integration across manufacturing, logistics, finance
Should Have:
- PLM integration for engineering change management
- Design-to-cost optimization
Could Have:
- AI-based demand forecasting
- Mobile applications
Won’t Have:
- Fully autonomous supply chain optimization
Phase 2: Portfolio-Level Scoring
Quantitative scoring (1–5 scale):
Example:
- Product master API: High value, low risk → Must
- PLM integration: Medium complexity → Should
- AI forecasting: High risk → Could
Phase 3: Project-Level Definition
Example requirement:
“Expose product data from legacy systems via RESTful APIs.”
Details:
Must Have:
- SAP tables (MARA, MARC)
- OData/REST APIs
- OAuth 2.0 authentication
Should Have:
- Master Data Governance (MDG)
- Version control
Managing Trade-offs
Stakeholders often expect “more, faster, cheaper.” Enterprise Architects must clarify trade-offs.
Effective strategies include:
- Start small to reduce risk
- Predefine priorities to handle issues
Value vs. Effort Matrix
A Value vs. Effort matrix helps prioritize:
- High value, low effort → prioritize first
- Align decisions with OKRs
Traceability Across Four Levels
TOGAF® requires traceability across:
- Strategy: Improve agility
- Portfolio: Product master API initiative
- Project: API development
- Solution: JSON format, OAuth 2.0, <200ms response
Requirements vs. Architecture Boundary
- Requirements define “what”
- Architecture defines constraints
- Design defines “how”
Example: Standardizing REST APIs enforces architectural consistency.
Compliance and Value-Driven Governance
Compliance should ensure:
- Business problems are solved
- Architecture intent is followed
- Controls are met
- Stakeholder approval is obtained
Practical Advice for Enterprise Architects
- Stop at the right level of detail
- Apply “ruthless minimization” of information
- Focus on decision-making support
Stop modeling when:
- Stakeholder concerns are addressed
- Implementation guidance is sufficient
- Gaps for decision-making are identified
Conclusion
TOGAF-based requirements prioritization enables structured SAP implementation using MoSCoW, scoring models, and traceability.
The key is value-driven governance—focusing not just on compliance, but on delivering real business outcomes.
Please also refer to our procurement and purchasing blog.
It discusses the value of managing and operating the Source-to-Pay (S2P) process in an integrated, end-to-end manner.
The Importance of S2P for Automotive Parts Manufacturers
Enterprise Architect – Skills and Responsibilities (general description of the EA role, skills, and typical activities across organizations)
https://www.leanix.net/wiki/ea/enterprise-architect
Reference Links
This article is based on the following reliable sources and industry best practices.
TOGAF Framework Resources
- Visual Paradigm Guides, “Understanding TOGAF’s Requirement Management Phase and Its Role in the TOGAF ADM”
https://guides.visual-paradigm.com/understanding-togafs-requirement-management-phase-and-its-role-in-the-togaf-adm/
(February 3, 2026) - Shioda, Crea Vision, “Guide to Applying TOGAF 10 (Part 3)” [Japanese]
https://note.com/crea_vision/n/n02eb35d7d916
(March 22, 2026) - Shioda, Crea Vision, “Guide to Applying TOGAF 10 (Part 1)” [Japanese]
https://note.com/crea_vision/n/n5cc3f4f80524
(March 8, 2026) - Visual Paradigm Guides, “TOGAF Guide: Why Every Enterprise Architect Should Know It”
https://guides.visual-paradigm.com/ja/togaf-guide-why-every-enterprise-architect-should-know-it/
(February 4, 2026)
Requirements Prioritization Methodologies
- Business Analyst Learnings, “MoSCoW: Requirements Prioritization Technique”
https://www.businessanalystlearnings.com/ba-techniques/2013/3/5/moscow-technique-requirements-prioritization
(March 4, 2013) - Jayasinghe, Dilushi, “MoSCoW Prioritization Method” LinkedIn
https://www.linkedin.com/pulse/moscow-prioritization-method-dilushi-jayasinghe–tkefc
(November 18, 2025) - Visual Paradigm, “MoSCoW Prioritization Framework Tool”
https://www.visual-paradigm.com/features/moscow-prioritization-framework-tool/ - DSDM Consortium, “MoSCoW Prioritisation – DSDM Project Framework”
https://www.agilebusiness.org/dsdm-project-framework/moscow-prioritisation.html
(October 9, 2022) - The Knowledge Academy, “MoSCoW Analysis: Understanding the Prioritisation Method”
https://www.theknowledgeacademy.com/blog/moscow-analysis/
(December 31, 2008)
SAP Implementation Practice
- Feliponi, Luiz Carlos, “Prioritizing at Scale in an SAP Environment” LinkedIn
https://www.linkedin.com/pulse/prioritizing-scale-sap-environment-luiz-carlos-feliponi-dwsff
(July 23, 2024) - Ignite SAP, “Requirements Gathering in SAP Projects”
https://ignitesap.com/requirements-gathering-in-sap-projects/
(April 14, 2025) - SAP Help Portal, “Requirement Prioritization”
https://help.sap.com/docs/SAP_ERP_SPV/967e1c2a6a8c4183b7e07d28e7574445/ab7db65334e6b54ce10000000a174cb4.html
Additional Resources
- Blog Reflektis, “Requirements Management and TOGAF – From the Mist”
https://blog.reflektis.nl/requirements-management-togaf/
(January 15, 2022) - Scribd, “Requirements Management in ADM Phase” (PDF)
https://www.scribd.com/document/777615503/Requirements-Management-phase
(July 28, 2025) - ProductPlan, “MoSCoW Prioritization | Glossary”
https://www.productplan.com/glossary/moscow-prioritization
(April 20, 2026)
Disclaimer
Parts of this article were developed with reference to generative AI suggestions and were reviewed, refined, and supplemented based on the author’s professional expertise and judgment.
Leave a Reply