Welcome to PMConnection

     

Menu
· Home
· The Project Management Search Engine
· Exclusive Articles

Related Sites
There isn't content right now for this block.

Related Products
   
 

The Self-Driving Project: Using Artificial Intelligence to Deliver Project Success

 
  
 
Citizen Development: The Handbook for Creators and Change Makers
  
 
 
A Guide to the Project Management Body of Knowledge: PMBOK 7th Edition 2021
  

 
PMP Project Management Professional Exam Study Guide
    
 

 
Microsoft Project Step by Step


  

 
Microsoft Project
  

  

 
Managing Enterprise Projects: Using Project Online and Microsoft Project Server

Program and PMO: DAD vs SAFe vs Scrum
Posted on Tuesday, January 09 @ 00:01:01 EST by webadmin

PMConnection Articles


The following table has been developed to quickly compare the three different methodologies of DAD, SAFe and Scrum along-side their seven respective domains of; roles, processes, artifacts, benefits, complexity, usage, and tools.


Domain

DAD

SAFe

Scrum

Details

What is DAD?

What is SAFe?

What is Scrum?

Roles

Primary Roles:

• Team Lead

• Product Owner

• Architecture Owner

• Team Member

• Stakeholders

Secondary Roles

• Independent Testers

• Specialists

• Domain  Expert

• Technical Expert

• Integrator

Team:

• Product Owner

• Scrum Master

• Team

Program:D

• Product Management

• Release Train Engineer

• System Architect

Large Solution:

• Solution Management

• Solution Train Engineer

• Solution Architect

Portfolio:

• Lean Portfolio Management

• Epic Owners

• Enterprise Architect

• Product Owner

• Scrum Master

• Team

Processes

Inception      

• Form Initial Team

• Develop Common Vision

• Align with Enterprise Direction

• Explore Initial Scope

• Identify Initial Technical Strategy

• Develop Initial Release Plan

• Secure Funding

• Form Work Environment

• Identify Risks

• Develop Initial Test Strategy

Construction

• Produce a Potentially Consumable Solution

• Address Changing Stakeholder Needs

• Move Closer to a Deployable Release

• Improve Quality

• Prove Architecture Early

Transition    

• Ensure the Solution is Consumable

• Deploy the Solution

Ongoing        

• Grow Team Members

• Govern Delivery Team

• Leverage and Enhance Existing Infrastructure

• Address Risk

• Improve Team Process and Environment

• Coordinate Activities

Portfolio

• Establish Strategic Themes

• Define Epics

• Create Portfolio Backlog

• Create Portfolio Kanban

• Align Budgets to Value Streams

Large Solution

• Define Capabilities

• Create Large Solution Backlog

• Create Large Solution Kanban

• Conduct Solution Planning

• Conduct Solution Demo

Program

• Define Features

• Create Program Backlog

• Create Program Kanban

• Conduct WSJF

• Conduct PI Planning

• Establish PI Objectives

• Conduct System Demos

• Conduct Inspect and Adapt

Team

• Define User Stories

• Create Team Backlog

• Prioritize User Stories

• Create Sprint Backlog

• Execute Sprint

• Conduct Daily Standups

• Conduct Review

• Conduct Sprint Retrospective

• Define User Stories

• Create Sprint Backlog

• Conduct Sprint Planning

Execute Sprint

• Conduct Daily Standups

• Conduct Sprint Review

• Determine if shippable product

• Conduct Retrospective

Artifacts

• Initial Vision and Funding

• Business Roadmap

• Technology Roadmap

• Initial Requirements

• Release Plan

• Initial Architectural Vision

• Iteration Backlog

• Consumable Solution

• Funding and Feedback

 

Portfolio

• Investment Themes

• Business and Architecture Epics

• Portfolio  Backlog

• Portfolio Vision

Metrics

Program

• Product Roadmap

• Vision

• Program Backlog

• Team Backlog

• NFR's

• Architecture Runway

• Business and Architecture Features

• Metrics

Team

• Team Backlog

• Team PSI Objective

• Sprint Goals

• Working Software

• Spikes

• Metrics

• Product Backlog

• Sprint Backlog

• Burn-Down Chart

• Increment

Benefits

• Proven, well documented and flexible

• Clear roles, artifacts and events

• Scalable from 2, 3 or 4 levels

• Hybrid framework

• Flexible

• Phases with milestones support large scale agile delivery

• Geared for individual teams or small organizations

• Easier to implement than DAD or SAFe

• The basis or the foundation in which both DAD and SAFe are built upon

Complexity

Medium

High

Low

Usage

Scalable throughout entire organization – Not prescriptive.

Scalable throughout entire organization – Very prescriptive.

Team Level

Tools

• Microsoft TFS

• Blueprint

• The Enterprise • Transformation Advisor

• MethodPark Stages

• IBM Rational Method Composer (RMC)

• Atlassian - JIRA

• Microsoft - InCycle

• CA Technologies - CA Agile Central

• VersionOne - VersionOne

• Allocable

• One2Team

• Sciforma

• Target Process

• SmartCore

• AgileZen

• VersionOne

• CA Agile Central

• YouTrack

• GitLab

• JIRA






Note: You may find this book helpful:



 
Related Links
· More about PMConnection Articles
· News by webadmin


Most read story about PMConnection Articles:
300 Project Manager Interview Questions


Article Rating
Average Score: 5
Votes: 2


Please take a second and vote for this article:

Excellent
Very Good
Good
Regular
Bad


Options

 Printer Friendly Printer Friendly


Associated Topics

PMConnection Articles



Copyright 2005-2024 PMConnection.com. All Rights Reserved.
http://www.pmconnection.com a
PHP-Nuke Copyright © 2005 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.12 Seconds