Software Development, in 2015

Talk at Ochanomizu University, Program for Leading Graduate Schools, about mechanics to encourage teamwork for software development.

Transcript

1. Software Development,
 in 2015 Soutaro Matsumoto Ubiregi Inc.
2. Soutaro Matsumoto • Received PhD in 2010 • Co-founder of Ubiregi • Programmer
7. As a Programmer • Sketch ideas • Read articles • Discussion with teammate • Write programs with teammate • Deliver our product to customers
8. As a PhD Student • Sketch ideas • Read papers • Discussion with supervisor • Write programs for my experiments • Write papers
9. As a Programmer • Sketch ideas • Read articles • Discussion with teammate • Write programs with teammate • Deliver our product to customers
10. My Team • 14 Programmers • 3 Designers • ~20 Sales, Biz-dev, Support, Back office
11. Software Development • Analysis • Implementation • Project Management
12. Analysis • Write down requirements • Design data structure • Sketch people/UI
14. 
    8IJUF
    #PBSET
15. 1PTUJU
    PO
    UIF
    XBMM
18. Tools • Use tools everyone can use • Primitive tools for abstraction
19. IUUQTXXXGBDFCPPLDPNQIPUPQIQ GCJETFUB UZQFUIFBUFS
20. Implementation • UI Design • Programming
21. UI Design • Sketch • Paper Prototyping • Graphic Tools • Prototyping Tools
23. Sketch • To share and verify functionality • Use whiteboard and bold pen to control level of abstraction
25. Paper prototyping w 4LFUDI
    6*
    PO
    QBQFS
    w 6TF
    QJFDFT
    PG
    QBQFST
    UP
    TJNVMBUF
    6*
    JOUFSBDUJPO
    w 7FSJGZ
    JOUFSBDUJPOT
27. Graphic Tools w %POF
    CZ
    EFTJHOFST
    w 1SFQBSF
    JNBHF
    SFTPVSDFT
    GPS
    QSPEVDUJPO
    w 4LFUDI
    JT
    B
    HSFBU
    UPPM
    GPS
    6*
    EFTJHO
29. Prototyping Tools w *OUFSBDUJWF
    QSPUPUZQF
    XJUIPVU
    QSPHSBNNJOH
    w 5FTU
    6*
    qPX
    w 8F
    MJLF
    'MJOUP
30. UI Design • Share ideas and collect feedbacks • Test rapidly with non-technical people
31. Programming • Git & GitHub • Automated Test & Continuous Integration
32. 14 Programmers, Working Together 1. Owns copies of the code on the computers 2. Write code separately 3. Review and revise the changes 4. Collect the changes
34. GitHub • Web service for software development • One of the best places to collaborate with programmers
36. • Review the change • Discuss by comments • Apply the change once approved • Changes are filed for future references
37. ❤ Emoji
39. Test and CI • Test is a program to ensure the program is working correctly • Continuous Integration ensures every changes are tested
41. Build Software Together • Allow coding separately • Infrastructure to review the changes • Help to be sure nothing broken •
42. Project Management • Agile, SCRUM • Retrospective • Estimating & Planning
45. • Post-it for each features • Put them on the wall for wider perspective • Status of the features • Priority of the features • Put numbers for estimation
50. Retrospective • Review the week • Share experience in the team • Encourage to share tips/hacks
52. KPT w ,FFQ
    5IJOHT
    UP
    TIBSF
    w 1SPCMFN
    5IJOHT
    UP
    JNQSPWF
    w 5SZ
    JNQSPWFNFOU
53. Estimating • Predicate when a feature can be delivered • Encourage sharing analysis in the team
57. References • Lean UX――ϦʔϯࢥߟʹΑΔϢʔβΤΫεϖϦΤϯεɾσβΠϯ - http://www.oreilly.co.jp/books/ 9784873116617/ • ϓϩτλΠϐϯά࣮ફΨΠυ εϚϗΞϓϦͷޮ཰తͳσβΠϯख๏ - http://book.impress.co.jp/books/ 1114101013 • Flinto - https://www.flinto.com • Sketch 3 - http://bohemiancoding.com/sketch/ • GitHub - https://github.com • Travis CI - https://travis-ci.org • ΞδϟΠϧαϜϥΠʵୡਓ։ൃऀ΁ͷಓʵ • ΞδϟΠϧϨτϩεϖΫςΟϒζɹڧ͍νʔϜΛҭͯΔʮ;Γ͔͑ΓʯͷखҾ͖ • ͜Ε͚ͩ! KPT • Team Geek――GoogleͷΪʔΫͨͪ͸͍͔ʹͯ͠νʔϜΛ࡞Δͷ͔ - http://www.oreilly.co.jp/books/ 9784873116303/