The three categories of process blades in Disciplined Agile (DA) are:
* Disciplined DevOps:Focuses on integrating development and operations to streamline workflows, reduce bottlenecks, and ensure continuous delivery and deployment.
* Disciplined Agile IT:Encompasses practices that support IT functions, such as Enterprise Architecture, Data Management, IT Governance, and IT Operations.
* Disciplined Project Management Office (PMO):Provides strategic alignment, governance, and guidance to ensure that projects and initiatives align with organizational goals and deliver value.
Disciplined Agile Delivery (C) is a process blade itself, not a category, and Disciplined Kanban (D) is not a recognized process blade in DA.

"Organization distribution" is not a tactical scaling factor for a team in the context of Disciplined Agile (DA).
Tactical scaling factors focus on specific elements that impact the immediate team context, such as Team Size (A), Geographic Distribution (B), and Team Maturity (C). "Organization distribution" refers more broadly to the structure or distribution of the organization as a whole, rather than directly impacting the team's day-to- day operations or scaling concerns.
Top of Form
Bottom of Form

The primary risk addressed by thestakeholder vision milestoneisthat your primary stakeholders agree to your strategy. This milestone ensures alignment and consensus among key stakeholders regarding the project's overall vision, goals, and strategic approach. Achieving this agreement is critical to securing buy-in, support, and commitment from stakeholders, which helps to mitigate the risk of misalignment and conflicting expectations as the project progresses. Other risks, like architectural strategy viability, business case viability, or a realistic release plan, are addressed by other specific milestones or checkpoints in the Disciplined Agile framework.