Embed Size (px)
DESCRIPTION
Scrum is a ‘light-weight” methodology and is usually easily adopted by small organizations. However, when working with large-scale and even global organizations, Scrum adoption is anything but easy or “light-weight”. The majority of barriers to adoption, however, aren’t related to developers, development practices or skill but are rooted in the organization. This presentation explores the top 20 barriers to scrum adoption and organizational transformation. It includes a mindmap with dozens more. Contact me if you would like a full-size pdf of the mindmap.
Citation preview
Organizational Barriers and Impediments to
Big Scrum Implementations
Darian RashidAgile Trainer and [email protected]
Module-Based Scrum Teams and Horizontal Slices
GUI scrum team
Business Logic Scrum team
Database Scrum team
“As the system, I’d like to manage my memory so that my memory is managed”
“How do I demo a driver?”
ORG
Distributed Teams
ORG
“The sun never sets on our development empire”
Hardware and Embedded Systems
ORG
Used as an excuse NOT to practice Scrum
Department of Facilities
ORG
“Tear down these cubes!”
Security Policies
“utkubmiT”
ORG
Individual Evaluations and Incentives
Management
Velocity Used to Compare Teams
Management
Fear and Safety
Management
• Fear of raising issues
• “The daily beatings”
PO Decisions Are Pushed to the Devevelopment Team(s)
Product
Ownership
Hmmm…Chinese or Italian
tonight?
Multiple Backlogs And/Or Product Owners For the Same Team
Product
Ownership
Product Owner Proxys (POPs)
Product
Ownership
Product
Ownership
Little or No Release Planning
ScrumMasters Not Empowered
ScrumMasters
Part Time and Rotating “Admin”ScrumMasters
ScrumMasters
Little or No Infrastructure
Technical
Defects are Counted Toward Velocity
Quality
Manager == PO &&Manager == SM &&Manager == Technical Lead
@^$%&!!!
Bottom-Up Deployment
“Scrum is a practice for developers”
Leadership
