Archimydes - Software Development as a Service
•Download as PPTX, PDF•
2 likes•1,090 views
Lightning Talk by Mohamed Ali at SpringOne Platform 2017
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Archimydes - Software Development as a Service
Similar to Archimydes - Software Development as a Service (20)
More from VMware Tanzu
More from VMware Tanzu (20)
Recently uploaded
Recently uploaded (20)
Archimydes - Software Development as a Service
- 2. THESIS: AGES OF ECONOMIC PRODUCTIVITY Agrarian Industrial Information 0 5,000,000 10,000,000 15,000,000 20,000,000 25,000,000 30,000,000 35,000,000 40,000,000 45,000,000 50,000,000 1 1000 1500 1600 1700 1820 1870 1913 1950 1973 2003 2016 World GDP - 1990 Dollars
- 3. THESIS: EACH AGE DRIVEN BY A CORE METRIC FACTORY OUTPUT CROP YIELD CODE VELOCITY
- 4. THESIS: HOW POWERFUL IS THE CORE METRIC? 19131700
- 5. THESIS: WHAT IS CODE VELOCITY • VELOCITY: THE SPEED OF “SOMETHING” IN A GIVEN “DIRECTION” • CODE VELOCITY: THE SPEED AT WHICH “CODE” IS DEVELOPED, DEPLOYED, and is EXECUTES IN ORDER “TO ATTAIN COMPETITIVE ADVANTAGE”
- 6. ROOT NYC: CODE VELOCITY TODAY CODE VELOCITY
- 7. ROOT NYC: BUILT AROUND CODE VELOCITY ADVISORY RESEARCH INVESTMENTSLABS
- 8. ROOT NYC: BUILT AROUND CODE VELOCITY ADVISORY RESEARCH INVESTMENTSLABS
- 9. BACKGROUND: POST DEPLOY FEATURE DEV • PRODUCT DEPLOYED TO PRODUCTION • PROJECT WAS OUTSIDE WARRANTY PERIOD • CLIENT WAS PRIMARILY IN SUPPPORT MODE • NEEDED OCASSIONAL FEATURE DEVELOPMENT • FAST • REASONABLE COST • BURSTY NATURE
- 10. OPTIONS: THE USUAL SUSPECTS • TIME AND MATERIAL CONTRACT • FIXED FEE ARRANGEMENTS • MANAGED SERVICE OPTION
- 11. A NEW OPTION: USER STORY CENTRIC PRICING
- 13. ARCHIMYDES: DESIGNED FOR CODE VELOCITY SUBMISSION REVIEW DEVELOPMENT ACCEPTANCE • 4 - 8 hours • 2 - 12 hours/user story • 2 - 12 hours/user story
- 14. STEP 1: SPRINT SUBMISSION
- 16. STEP 3: ACCEPTANCE VIEW
- 17. PRODUCT DEVELOPMENT: SEARCH MODE IDEAS CODE DATA MEASURE BUILD LEARN PRE-TRACTION - LEAN STARTUP Credit: Eric Ries
- 18. PRODUCT DEVELOPMENT: SCALE MODE POST-TRACTION – CODE FACTORY Develop Test Deploy User stories Sprint UI Design
- 19. ARCHIMYDES: USE CASES BUILD NEW FEATURES DEVELOP A MICROSERVICE RE-PLATFORM OR CLOUD ENABLE EXISTING APPS
- 20. WHERE WE ARE AND NEXT STEPS WHERE ARE WE: • https://www.archimydes.com • EATING OUR OWN DOG FOOD • EXECUTING CLIENT PROJECTS ON NODE & JAVA (SPRING) NEXT STEPS: • EXECUTE NEW PROJECTS (via native platform on-boarding) • FEEDBACK & CONTACT: mali@root-nyc.com
- 21. WHERE WE ARE AND NEXT STEPS WHERE ARE WE: • https://www.archimydes.com • EATING OUR OWN DOG FOOD • EXECUTING CLIENT PROJECTS ON NODE & JAVA (SPRING) NEXT STEPS: • EXECUTE NEW PROJECTS (via native platform on-boarding) • FEEDBACK & CONTACT: mali@root-nyc.com
Editor's Notes
- On the labs side what we do is generally driven by a pain point in client delivery Here the pain point had to do with feature development post-deployment of a product for a client
- Time and Materials Contract: TURNED OUT TO BE TOO EXPENSIVE AND NOT RESULTS DRIVEN Fixed Fee Arrangements: Were too risky, particularly because we didn’t know in advance what we’d be signing up for – some weeks we could be asked to develop no features, in other weeks we could be asked to develop 10 features Managed Service Option: We were not looking really looking to get into the production support business – it took us a bit too far away from the company focus Hence for different reasons none of these were great options for us
- Neither party feels obligated in any way The client only pays for the features he/she requires The client only pays if the features work as intended We get paid by feature – hence are not jipped by elastic demand
- Submission: Select stack and fork repo (if applicable) Enter project description Input user stories and acceptance criteria Review: Review forked code base Review user stories and acceptance criteria Update user stories and acceptance criteria Develop: Review user stories and acceptance criteria Develop code Unit test and check-in code Acceptance: Integration and regression test code Bug fix Acceptance and code merge
- Submission: Select stack and fork repo (if applicable) Enter project description Input user stories and acceptance criteria Review: Review forked code base Review user stories and acceptance criteria Update user stories and acceptance criteria Develop: Review user stories and acceptance criteria Develop code Unit test and check-in code Acceptance: Integration and regression test code Bug fix Acceptance and code merge
- <FOCUS ON SPECIFICITY>
- <FOCUS ON PROCESS AND CREDIT SYSTEM>
- If this is staring to look a bit like a assembly line process – which might be anathema around here – then well, it was meant to be so (not by accident) See the thing is we don’t think a lean startup approach makes sense for everything – in particular we think of product development in two different modes – a Search Mode & a Growth mode
- If this is staring to look a bit like a assembly line process – which might be anathema around here – then well, it was meant to be so (not by accident) See the thing is we don’t think a lean startup approach makes sense for everything – in particular we think of product development in two different modes – a Search Mode & a Growth mode