Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

The Software Engineering process in Everyware Technologies


Published on

An overview of the software engineering process in our company

Published in: Software
  • Login to see the comments

  • Be the first to like this

The Software Engineering process in Everyware Technologies

  1. 1. Software Engineering on Everyware Carlos Rodríguez Domínguez Everyware Technologies S.L. Tomás Ruiz López /everywaretech @everywaretech {tomas, carlos}
  2. 2. 1. Let’s talk with the costumer
  3. 3. 1a. Our first meeting
  4. 4. 1b. We need to understand your work/ service/product
  5. 5. 1c. What’s our portfolio in your area
  6. 6. 1d. Is a mobile app suitable for you? Maybe not…
  7. 7. 2. What? When? How much?
  8. 8. 2a. Estimate when, taking into account what
  9. 9. 2b. How much = Days x People x 100 €
  10. 10. 2c. Don’t discuss the price, discuss what to do
  11. 11. 2d. Deliver a clear, but simple budget > 80% acceptance rate But is not enough for us… ;D
  12. 12. 3. The “face” of the code: Design + Storyboard
  13. 13. 3a. The graphical design needs to be clear
  14. 14. 3b. The storyboard is key for customer satisfaction
  15. 15. 3c. Do not impose, explain
  16. 16. 4. First prototype: Is the app already finished?
  17. 17. 4a. Your first prototype must include most of your storyboard But not all the functionalities, of course!
  18. 18. 4b. Iterate over the design again! But explain!
  19. 19. 5. Let’s code together
  20. 20. 5a. One person-One project = FAIL! But some times inevitable!
  21. 21. 5b. Coordination tools! Extra work=Less work Code + TODOs + Communication NOW LATER
  22. 22. 5c. Modeling team and Viewing team And exchange the people! And make them work together! Leaders? Yes, but carefully chosen and not always the same people!
  23. 23. 5d. Everyone is on the controller team! Strictly Model-View-Controller
  24. 24. 6. Daily-weekly- monthly prototypes
  25. 25. 6a. The customer is the most important member of the development team! A prototype is not a surprise! is programmed!
  26. 26. 6b. Provide a date for the next prototype - Why on that date? Explain! Explain! Explain! Explain!
  27. 27. 6c. TIC! TOC!
  28. 28. 7. Your app is ready! Let’s start the project…
  29. 29. 7a. We don’t provide products, we provide software Software Product = Software + Infrastructure + Marketing + Manuals + Economical model + CRM + …
  30. 30. 7b. …But we need to help! Our experience is a great value for the customer! Give your opinion and… explain!
  31. 31. 8. We are here!
  32. 32. 8a. A customer is always a customer The relationship should never end
  33. 33. 8b. Maintainability! Suggest it! New features? Technological changes? New knowledge? Detected bugs?
  34. 34. 8c. Comeback to the beginning if you need it If you failed: Accept it, take actions and continue
  35. 35. 8d. Train! Demo!
  36. 36. We need to learn and change a lot! ! Software Engineering is the new Never-ending Story! ! Questions? Feedback?