Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Software Craftsmanship for Extremely Collaborat...

Software Craftsmanship for Extremely Collaborative Teams

What does software craftsmanship look like for teams that lack code ownership? Can one be a craftsman while jumping from project to project, team to team? The answer is Yes. Organizations with full-time pair programming, collective code ownership, and flat organizational structures not only support craftsmanship, but also harbor work environments where rigorous software development discipline is taught, enforced, and spread from team to team.

Joe Moore

August 26, 2014
Tweet

More Decks by Joe Moore

Other Decks in Technology

Transcript

  1. “In the early days of [agile] the dominant strain was

    Extreme Programming, which has a lot to say about technical practices”
  2. “Now the dominant agile strains are Scrum and Lean, which

    don't care very much about programming”
  3. XP

  4. TDD • RAPID ITERATIONS 
 • CUSTOMER FOCUS • CONTINUOUS

    INTEGRATION • COACHING • REFACTORING • SIMPLEST THING POSSIBLE • VELOCITY • X- FUNCTIONAL TEAMS • STORY ESTIMATES • RETROSPECTIVES
  5. RAMP UP THE NEW DEV TEACH THE OLD DEV NEW

    TRICKS FEWER REJECTED FEATURES DISTRACTED INCREASED COHESION C R O S S T R A I N I N G R I S K M I T I G AT I O N COMMUNICATION NAMING OF THINGS PROFESSIONAL DEVELOPMENT FASTER DELIVERY BETTER INTERVIEWS CONSTANT OF IMPROVEMENT OLD HIRES FRESH PERSPECTIVES SERIOUSLY THE LIST PAIR PROGRAMMING BENEFITS