High Bandwidth High Bandwidth Communication for Communication for DevelopersDevelopers

Martín Nahuel Rabaglia@sr_humo

Agenda

What is High Broad width Communication?What is Software Engineering?

Agile Communication Dimensons

Who am I?

•Information System Engineer

•Software Engineer @ R/GA

•Product Architect @ Smartbits

•4 years with Agile

Experience

Great Agile Team Great Agile Team

•High Bandwidth CommunicationHigh Bandwidth Communication

•Passion

•Lush of Jeffries

•Agile engineering

High Bandwidth CommunicationHigh Bandwidth Communication

•Have a team room with White boards

•Share all knowledge.

•Responsive and responsible developers

•Select the right tools to communicate

and many others…

What is software engineering?

What is software engineering?

What really What really matters?matters?

Solution Solution Development Development

Process Process

Communication Communication ProcessProcess==

The quality of solution The quality of solution depends on the fidelity with depends on the fidelity with

which the which the team communicates and team communicates and conveys the message.conveys the message.

What really What really matters?matters?

DimensionsDimensions

Individual Dev Team

External Team The Others

Let´s start!Let´s start!

Individual Dev Team

External Team The Others

Documentation is dead, Documentation is dead, long live documentationlong live documentation

Individual

•Objects and Methods namesObjects and Methods names

•Unit Test NamesUnit Test Names

public void must_return_filled_likes()public void must_return_filled_likes()

public void like_test()public void like_test()

UnderstandingUnderstanding

Individual

•COMMITSCOMMITS

•ISSUE RESOLUTIONISSUE RESOLUTION•What?What?•When?When?•Why?Why?Be clear!Be clear!

Individual Dev Team

External Team The Others

WHITE BOARD!WHITE BOARD!

DEV TEAM

QUALITY = TRUSTQUALITY = TRUST•Design breaks for Design breaks for communicationcommunication•StyleStyle•TestTest•Tech DebtTech Debt

DEV TEAM

FUN = TRUSTFUN = TRUST

DEV TEAM

Individual Dev Team

External Team The Others

Experts, not gods

Experts, not gods

•Adapt to your messages to your Adapt to your messages to your receivers.receivers.

•Simplify Diagrams (bad UML!)Simplify Diagrams (bad UML!)

EXTTEAM OTHERS

•Schedule MeetingsSchedule Meetings

•Notify Events (Releases)Notify Events (Releases)

•Discuss StrategyDiscuss Strategy

MAILMAIL

EXTTEAM OTHERS

•Resolve Doubts > Issue TrackerResolve Doubts > Issue Tracker

•Send assets > Shared FoldersSend assets > Shared Folders

•Document Functionality > BacklogsDocument Functionality > Backlogs

•Spaghetti Mailing > Phone!Spaghetti Mailing > Phone!

MAIL > NO!MAIL > NO!

EXTTEAM OTHERS

IMIM

EXTTEAM OTHERS

•Be Instantaneous.Be Instantaneous.

•Polite, but not friendly Polite, but not friendly

•If not response use another toolIf not response use another tool•Mail to questions.Mail to questions.•Phone to urgents.Phone to urgents.

•Always over communicate Always over communicate (ask,ask,ask)(ask,ask,ask)

•You are not working alone. Let You are not working alone. Let everybody knows everybody knows •WhatWhat•WhenWhen•Why /Why not .Why /Why not .

Changes HandlingChanges Handling

EXTTEAM OTHERS

ToolsTools

EXTTEAM OTHERS

How To Make it How To Make it happen?happen?

““Practice, Practice, Practice”Practice, Practice, Practice”

Improved processes are started with the establishment

of small specific goals specific goals and incremental improvements.incremental improvements.

Questions?

Thank You

@sr_humo