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.

[QE 2017] Michał Stryjak - Startupowy chleb powszedni

180 views

Published on

Prezentacja z VI edycji Quality Excites. Jak startup może przekonać do siebie klienta? Michał zaproponował zastosowanie argumentu, który w Dolinie Krzemowej nazywa się „overwhelming advantage”. Jest to rozwiązanie, które daje tak ogromne możliwości, że odbiorca nie może sobie pozwolić aby go nie kupić.
Podczas wystąpienia Michał opowiedział jak technologiczne startupy szukają swojej przewagi. Użył przykładów ze swojego zespołu aby opisać, jak można poradzić sobie z bezlitosnym rynkiem, z częstymi zmianami wymagań oraz z ciągłym ciśnieniem, aby dostarczać jeszcze szybciej.

Published in: Software
  • Be the first to comment

  • Be the first to like this

[QE 2017] Michał Stryjak - Startupowy chleb powszedni

  1. 1. Startup’s Bread & Butter
  2. 2. Hello!I am Michal Head of Development at PiLab, Testing enthusiast, Gamer You can catch me at: michal.stryjak@gmail.com
  3. 3. AGENDA × What’s a startup? × Path From Idea to product × Overwhelming advantage × Challenges × How To find balance
  4. 4. 1. What’s a startup? IRON man Mark 1 A startup is a human institution designed to deliver a new product or service under conditions of extreme uncertainty Eric Ries “The Lean Startup”
  5. 5. How Do Startups work? Build Measure Learn IDEA Product Data
  6. 6. 2. Path from idea to product × Idea is easy, but we need to sell × No peaceful work × Requirements Come and go × Constant pressure
  7. 7. 3. Overwhelming advantage
  8. 8. 4. Challenges
  9. 9. … in search of overwhelming advantage!
  10. 10. … In need of Reliable solution!
  11. 11. Can both goals be pursued at the same time?
  12. 12. 5. How To find balance × We tried many Tools (Epics, US, DOD, …) × We tried many dev approaches (Scrum, Kanban, B-GA-G, Fast-Track on a different branch…) × It took us 2 years to learn the right path (For us)
  13. 13. Life of a feature Feature idea Prototype Validation Stabilization DROP
  14. 14. Stable Team’s goals - Build a solid foundation for further development - Improve performance, reliability, scalability - Help the support team - regular releases
  15. 15. Alpha teamS’ goals - Deliver as fast as possible - Implement new features - Explore new ideas - Lead on demo/POC/conference prep - Help the delivery team - Stabilize validated features
  16. 16. governance - Analyses the purpose of the feature (why we want it) - Suggests the implementation quality level (Risk areas) - Decides what is moved from alpha to a stable line - Resolves disputes
  17. 17. Development approach summary - One branch but Clear line between stable and Prototype (Feature Toggle) - New features are always developed as prototypes - Only selected (validated) features are moved to stable - People who developed a feature move it to stable (fix or rewrite it) - Possibility to deploy stable or Alpha

×