Culture First, Tools Last: Building Successful Collaborative Communities

Post on 22-Jan-2018

291 views 1 download

Transcript of Culture First, Tools Last: Building Successful Collaborative Communities

Guy Martin Director – Open@ADSK @guyma | @AutodeskOSS

Culture First, Tools LastBuilding Successful Collaborative Communities

My Perspective

▪ Tool Selection Drivers ▪ Culture, Process & Tools ▪ Tool Rollout Examples ▪ Things to Consider

Topics

Tool Selection Drivers

Collaboration Tool Stakeholders

What Drives Tool Selection?

$$ Adaptability

StandardizationProductivity

Culture, Processes & Tools

▪ Collaboration Style ▪ Awaiting permission vs. taking initiative

▪ Transparency ▪ Decisions/communications private or open

▪ Meritocracy ▪ Top-down or driven by valuable contributors

Existing Culture

▪ Contribution ▪ Tightly controlled or open

▪ Governance ▪ Tightly controlled or meritocratic

▪ Organizational ▪ Top-down, bottom-up, mixed

Existing Processes

▪ Knowledge Sharing ▪ People sharing or ‘documenting’

▪ Reuse ▪ Data being referenced or abandoned

▪ Metrics ▪ What works (or doesn’t)

Existing Tools

Tool Rollout Examples

The Good

Contenders Winner Why?

AutodeskCorporateReal-timeChat

The Not-so-Good

Incumbents Mandated Challenges

• Cultureofsilos• Process/devpracticesnotalignedwithtool• Monolithiccodearchitectures

AutodeskInternalSourceControl/Sharing

Things to Consider

Audit Your Culture

AskingPermission BeggingForgiveness

Siloed/Insular Transparent/Collaborative

ProductManagementDriven

EngineeringDriven

OpenClosed

▪ People bringing in tools (‘Shadow IT’) ▪ People building their own tools ▪ Why?

▪ No knowledge of what’s going on elsewhere? ▪ Desire for control? ▪ Speed of deployment?

Tools Landscape

▪ Shared responsibility/control ▪ Code ▪ Processes ▪ Policies ▪ Information ▪ Tools

▪ Engagement drives collaboration ▪ Review prevents ‘anarchy’

Build a ‘Pull Request’ Culture

▪ Resist vendor pressure ▪ They don’t always live your reality

▪ Allow some experimentation/flexibility ▪ Cull tools that aren’t working

▪ Follow the community ▪ Explore areas of critical mass

Align Tools with Reality

AdapttheTooltotheUser,nottheUsertotheTool

▪ Iterate as quickly as is practical ▪ Choose customizable tools

▪ Allow all stakeholders to drive process/tool customization

▪ Practice patience – your culture won’t change overnight

Release Early, Release Often