How to successfully build an app with a decentralized team

Working remote is something that a lot of developers need to do. May it be permanent, a few days a week or simply visiting clients we need to be able to keep communicating with our team, even if they are offline. How do we share code, divide tasks or have discussions when not everyone is online or available at all times. In this presentation we will see what tools are out there and how they can be used by your team to work together. Even for people that work together in the same room a lot of these tools provide structure and a good starting point on how to develop applications with a team.

Transcript

1. http://www.egeniq.com info@egeniq.com @egeniq Mobile Down South, June 7th, 2013 Thijs Damen How to successfully build an app with a decentralized team 1 Saturday, June 8, 13
2. About Me ‣ Software Engineer ‣ Android, iOS, HTML5 ‣ @thijsdamen ‣ thijs@egeniq.com 2 2 Saturday, June 8, 13
3. About Egeniq Mobile Development Knowledge Distributed 3 3 Saturday, June 8, 13
4. Working decentralized 4 4 Saturday, June 8, 13
5. Development kit ‣Macbook ‣27” Thunderbolt display ‣Proper chair and desk (if required) ‣iPhone, iPad ‣Android tablet, android phone ‣Software 5 5 Saturday, June 8, 13
6. Communication 6 6 Saturday, June 8, 13
7. Tools for communication ‣Skype • Practical • Fast • Reaches everyone (chat) 7 7 Saturday, June 8, 13
8. Know Your Coworkers ‣Learn to read people. • That’s brilliant. • That’s BRILLIANT!!! :-) :-) • ... that’s brilliant. :-( 8 8 Saturday, June 8, 13
9. Tools for communication ‣Telephone • When things get emotional or political • Always available 9 9 Saturday, June 8, 13
10. Tools for communication ‣E-mail • Asynchronous • Larger messages • Easier to find back 10 10 Saturday, June 8, 13
11. Tools for communication ‣Google Hangout ‣Jabber/IRC ‣Yammer 11 11 Saturday, June 8, 13
12. Daily stand-up meetings ‣ What did I accomplish yesterday? ‣ What will I do today? ‣ What obstacles are impeding my progress? 12 12 Saturday, June 8, 13
13. Bi-weekly meetings 13 ‣ Face to face interaction ‣ Demos, presentations, interviews ‣ Having fun together 13 Saturday, June 8, 13
14. Flexible offices 14 ICTU Offices The Hague 14 Saturday, June 8, 13
15. Working in the cloud 15 15 Saturday, June 8, 13
16. Storage in the cloud 16 ‣Google Drive • Real-time collaboration • Functional/Technical/Interaction designs ‣Google Calendar ‣GMail 16 Saturday, June 8, 13
17. Storage in the cloud 17 ‣ Large files ‣ Resources, fonts, templates etc ‣ Project files - Functional/Technical designs - Graphical designs 17 Saturday, June 8, 13
18. Story based project management 18 ‣Pivotal Tracker • Story based • Collaboration 18 Saturday, June 8, 13
19. Pivotal Tracker 19 19 Saturday, June 8, 13
20. Source Control 20 20 Saturday, June 8, 13
21. Git ‣Distributed 21 21 Saturday, June 8, 13
22. Git - Distributed ‣No single point of failure ‣Work offline ‣Adaptable workflow 22 22 Saturday, June 8, 13
23. Git ‣Distributed ‣Incredibly fast 23 23 Saturday, June 8, 13
24. Git vs. SVN benchmark 24 24 Saturday, June 8, 13
25. Git ‣Distributed ‣Incredibly fast ‣Merging is easy 25 25 Saturday, June 8, 13
26. Git ‣Distributed ‣Incredibly fast ‣Merging is easy ‣Can be hard to learn • Hard to read documentation • Access to very (!) powerful commands 26 26 Saturday, June 8, 13
27. Git - Rebasing 27 Merge Rebase 27 Saturday, June 8, 13
28. Do not rebase commits that you have pushed to a public repository 28 28 Saturday, June 8, 13
29. Git ‣Distributed ‣Incredibly fast ‣Can be hard to learn ‣Submodules 29 29 Saturday, June 8, 13
30. Git ‣Distributed ‣Incredibly fast ‣Can be hard to learn ‣Submodules ‣Pull Requests 30 30 Saturday, June 8, 13
31. Git - Pull Requests 31 31 Saturday, June 8, 13
32. Given enough eyeballs, all bugs are shallow 32 - Eric S. Raymond 32 Saturday, June 8, 13
33. Git - Pull Requests 33 33 Saturday, June 8, 13
34. Code reviews safe money 34 ‣ In a software-maintenance organization, 55 percent of one-line maintenance changes were in error before code reviews were introduced. After reviews were introduced, only 2 percent of the changes were in error. ‣ IBM's 500,000 line Orbit project used 11 levels of inspections. It was delivered early and had only about 1 percent of the errors that would normally be expected. ‣ The Aetna Insurance Company found 82 percent of the errors in a program by using inspections and was able to decrease its development resources by 20 percent. Use cases found in Code Complete by Steve McConnell 34 Saturday, June 8, 13
35. Continuous integration 35 35 Saturday, June 8, 13
36. Continuous integration ‣Build automation ‣Build validation ‣Build distribution Alternatives for build automation: Jenkins Alternatives for distribution: TestFlight, HockeyApp General alternatives: CISimple 36 36 Saturday, June 8, 13
37. “To improve is to change; to be perfect is to change often” 37 - Winston Churchill 37 Saturday, June 8, 13
38. Thank you! Questions? http://www.egeniq.com info@egeniq.com @egeniq http://www.egeniq.com thijs@egeniq.com @thijsdamen 38 Saturday, June 8, 13
39. Credits The following pictures were used in this presentation. All images are licensed with a creative common license. • World map - http://www.flickr.com/photos/shaireproductions/8098699979 • Kids ‘calling’ - http://www.flickr.com/photos/22409393@N03/5399855440 • Source code - http://www.flickr.com/photos/toolmantim/6170448143 • GIT vs SVN Benchmarks - http://git-scm.com/about/small-and-fast • Gears - http://www.flickr.com/photos/sidehike/459483568/ For more information about: • Pivotal Tracker - http://www.pivotaltracker.com • Buildozer - http://www.buildozer.com 39 Saturday, June 8, 13