Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
The Successful Shipper
Search
Keavy McMinn
June 15, 2017
8
340
The Successful Shipper
Keavy McMinn
June 15, 2017
Tweet
Share
More Decks by Keavy McMinn
See All by Keavy McMinn
Principles of Awesome APIs and How to Build Them.
keavy
121
16k
Improving your workflow with the GitHub API
keavy
9
670
Integrations
keavy
3
440
How to mend a broken identity
keavy
0
140
Better work, through better feedback.
keavy
1
320
Internal Tools
keavy
9
1.4k
Must. Try. Harder.
keavy
0
300
Career Health Check
keavy
0
210
From Artist To Programmer
keavy
1
310
Featured
See All Featured
Bash Introduction
62gerente
604
210k
Music & Morning Musume
bryan
41
5.6k
The MySQL Ecosystem @ GitHub 2015
samlambert
243
12k
Why Our Code Smells
bkeepers
PRO
331
56k
Facilitating Awesome Meetings
lara
42
5.6k
A Philosophy of Restraint
colly
197
16k
Adopting Sorbet at Scale
ufuk
68
8.6k
Reflections from 52 weeks, 52 projects
jeffersonlam
345
19k
Bootstrapping a Software Product
garrettdimon
PRO
302
110k
BBQ
matthewcrist
80
8.8k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
352
28k
The World Runs on Bad Software
bkeepers
PRO
61
6.7k
Transcript
The Successful Shipper Ship It, Gothenburg, Sweden Keavy McMinn |
GitHub @keavy
Definition of a successful shipper
Why being a shipper is important to me
Why being a shipper is important to me
Value
What does successful look like?
None
Successful
The “Hero” Coder
Narrow focus
Not sustainable
Exclude others from recognition High profile features
None
Results AND communication A different version of successful
Results
Anti-Pattern: Focus on shipping a big feature Results
Anti-Pattern: Focus on shipping a big feature Results
None
Anti-Pattern: Focus on shipping a big feature Results
Ship Responsibly! Results
Anti-Pattern: Focus on shipping a big feature Results
Anti-Pattern: the hero coder gets all the credit Results
Anti-Pattern: the hero coder gets all the credit Results
Anti-Pattern: the hero coder gets all the credit Results
Process and relationships Communication
Process and relationships Communication
Anti-Pattern: Communication about the project hits blockage Processes
Anti-Pattern: Communication about the project hits blockage Processes
Anti-Pattern: Communication about the project hits blockage Processes
Anti-Pattern: Communication about the project hits blockage Processes
Anti-Pattern: Communication about the project hits blockage Processes
Anti-Pattern: Communication about the project hits blockage Processes
Anti-Pattern: Communication about the project hits blockage Processes
Anti-Pattern: Communication about the project hits blockage Processes
None
None
Anti-Pattern: The focus is on building the wrong thing Processes
Anti-Pattern: The focus is on building the wrong thing Processes
Relationships
Anti-Pattern: Internal people dependencies are slowing you down Relationships
Trickle Down Effect Relationships
Anti-Pattern: Internal people dependencies are slowing you down Relationships
Anti-Pattern: Internal people dependencies are slowing you down Relationships
Anti-Pattern: Internal people dependencies are slowing you down Relationships
Anti-Pattern: Internal people dependencies are slowing you down Relationships
Anti-Pattern: Your boss blocks you shipping Relationships
Anti-Pattern: Your boss blocks you shipping Relationships
Anti-Pattern: Your boss blocks you shipping Relationships
Anti-Pattern: Your boss blocks you shipping Relationships
Balance between results, processes and relationships Successful shippers...
• Value all the tasks • Ensure everyone gets credit
• Communicate all the time • Focus on the problem, not your solution • Value all the people • Nurture allies and sponsors
None
Thanks! Ship It, Gothenburg, Sweden Keavy McMinn | GitHub @keavy
None