Agility without Complexity: Fast and Efficient

Agility without Complexity: Fast and Efficient

• 1.
  AT1 Concurrent Session 11/12/15 10:00am “Agility without Complexity:Fast and Efficient” Presented by: Geoff Perlman Xojo, Inc. Brought to you by: 340 Corporate Way, Suite 300, Orange Park, FL 32073 888-268-8770 · 904-278-0524 · info@techwell.com · www.techwell.com
• 2.
  Geoff Perlman Xojo, Inc. Founderand CEO of Xojo, Inc., makers of Xojo, Geoff Perlman started his adventure into software development on a VAX mainframe when he was ten years old. Since then, Geoff has worked for companies as large as AT&T and as small as a one-man shop. While working in Silicon Valley, he authored a book on database development and taught programming to thousands of people. For most of his career, Geoff has been running companies he founded, always focused on finding the simplest way to solve complex problems.
• 3.
  Becoming Agile without Complexity 1 GeoffPerlman Founder and CEO Xojo, Inc. 2 What will I talk about? • What we do • How we used to do it • How we do it now • What tools do we use to do it • What you need to do it right 3 What do we do? 4
• 4.
  5 What is Xojo? •RAD tool • Object-oriented language (dot syntax) • Cross between VB and Java • Native controls • Compile to native 32 & 64 bit code • Native apps 6 Supported Platforms • Linux • OS X • Windows • Web • iOS • Raspberry Pi (most SBCs) 7 1997 • 68K and PowerPC • Mac only • 1 Developer • 100,000 lines of C++ 8
• 5.
  Today • x86 andARM • 6 Platforms • 5 Developers • > 500,000 lines of C++, Xojo and Javascript 9 Users 25% 50% 25% Hobbyists Citizens Professionals 10 How we used to do it 11 12
• 6.
  13 14 • Notresponsive enough to end users • Changing requirements caused havoc • Poor communication between developers • Hard to stay motivated • Bad for business 15 How we do it now 16
• 7.
  Smaller & Shorter 17 Smaller& Shorter • 4 releases per year (1 per quarter) • Minor releases if needed • Easier to manage • Easier to estimate • More responsive to users • No death march 18 Standard Agile 19 Standard Agile • Release Planning Meeting • 1 to 2 Week Sprints • Pre-Sprint Planning Meeting • Daily Scrum Meeting • Sprint Retrospective Meeting • Post-mortem Meeting 20
• 8.
  21 Time-Tracking 22 23 Simple Agile 24
• 9.
  Simple Agile • Plan3 - 4 releases ahead • Daily Scrum • Post-Mortem Meeting 25 Daily Scrum • 5 to 15 minutes • What will I accomplish today? • Am I blocked? • Quick Team Decisions 26 What tools do we use to do it? 27 Prior to 2005 • Xojo written entirely in C++ • Bug fixes took longer • Changing the UI like pulling teeth • Betas several weeks apart • Engineers lacked sympathy 28
• 10.
  RAD Tools 29 30 2005and Beyond • Rewrote the Xojo IDE in Xojo • Much faster IDE UI development • Much faster framework development • Engineers spend more time using Xojo • Hiring customers 31 Betas 32
• 11.
  Betas • Beta 1- Branch for next release • Beta 1 - Announce ship date to beta testers • Weekly Betas 33 Feedback 34 35 36
• 12.
  37 Productivity Boosters 38 Unit Testing 39 AutomatedBuilds 40
• 13.
  What you needto do it right 41 What you need to do it right • Trust • Buy-in from everyone • Daily Scrum • Good communications • Code maintenance • Continuous testing • Release more often 42 Standard Agile • Release Planning Meeting • 1 to 2 Week Sprints • Pre-Sprint Planning Meeting • Daily Scrum Meeting • Sprint Retrospective Meeting • Post-mortem Meeting 43 Simple Agile • Plan 3 - 4 releases ahead • Daily Scrum • Post-Mortem Meeting 44
• 14.
  xojo.com/agile 45