How to choose appropriate technology for product development
Download as PPTX, PDF0 likes92 views
The document provides guidance on choosing the appropriate technology for product development, emphasizing the importance of understanding the product lifecycle and the required technology stack. It outlines crucial components to consider, common mistakes made by young teams, and suggestions for success, such as being honest about capabilities and leveraging existing solutions. Key considerations include the product's features, scalability, and aligning technology choices with market demands and internal processes.
![What components you need to think about
The main categories you must review:
Design [Interactive Mockups, Graphic Design]
Support, Sales, and Marketing [Email Marketing, Marketing Automation, Help Desk, Engagement/Lifecycle Marketing, Self-Hosted Blogging/ CMS]
Analytics [Analytics Integrator, Funnel Analysis Analytics, Heatmap Analytics, General Analytics]
Build, Test, Deploy [Code Collaboration & Version Control, Server Configuration and Automation, Code Review, Browser Testing, ContinuousIntegration,
Version Control System, Source Code Management Desktop Apps, Infrastructure Build Tools, JavaScript Testing Framework, Containers as a Service,
Text Editor, Virtual Machine Platforms & Containers, Virtualization Platform, Virtual Machine Management, JS Build Tools / JS Task Runners,
Front End Package Manager, Java Build Tools, Load Balancer / Reverse Proxy, Integrated Development Environment, Container Tools]
Collaboration [Wireframing, Group Chat & Notifications, Project Management, Issue Tracking, Web and Video Conferencing, Agile Project Management,
Password Management, ChatOps]](https://image.slidesharecdn.com/howtochooseappropriatetechnologyforproductdevelopment-200122134840/85/How-to-choose-appropriate-technology-for-product-development-9-320.jpg)
![What components you need to think about
The main categories you must review:
Payments [Payment Services]
Communications [Transactional Email, Voice and SMS, Mobile Push Messaging]
Monitoring [Performance Monitoring, Exception Monitoring, Website Monitoring, Log Management, Monitoring Tools]
Application Hosting [Web Servers, Cloud Hosting, Serverless / Task Processing, Realtime Backend / API, Platform as a Service]
Languages & Frameworks [Front-End Frameworks, Operating Systems, Cross-Platform Mobile Development, Cross-Platform Desktop Development,
Microframeworks (Backend), Templating Languages & Extensions, Languages, CSS Pre-processors / Extensions, Frameworks (Full Stack),
Javascript MVC Frameworks]
Back Office [Enterprise Resource Planning (ERP), Payroll & Benefits, Accounting, Expense Management]](https://image.slidesharecdn.com/howtochooseappropriatetechnologyforproductdevelopment-200122134840/85/How-to-choose-appropriate-technology-for-product-development-10-320.jpg)
![What components you need to think about
The main categories you must review:
Mobile [Mobile UI Frameworks, Mobile Test Automation, Cross-Platform Mobile Tools]
Application Utilities [Documentation as a Service & Tools, DNS Management, Search as a Service, User Management and Authentication,
Static Web Hosting, Mapping APIs, API Tools, Static Site Generators, Machine Learning Tools]
Libraries [Javascript Utilities & Libraries, Charting Libraries, Javascript UI Libraries]
Data Stores [Cloud Storage, Message Queue, Databases]
Assets and Media [File Storage, Content Delivery Network, Image Processing and Management]](https://image.slidesharecdn.com/howtochooseappropriatetechnologyforproductdevelopment-200122134840/85/How-to-choose-appropriate-technology-for-product-development-11-320.jpg)
How to choose appropriate technology for product development
- 1. How to Choose Appropriate Technology for Product Development By Amin Mesbahi @mesbahi | amin@mesbahi.net Jan-2020
- 2. Agenda • An overview on product lifecycle • Where is technology stack on the product lifecycle • What components you need to think about • Find out the correct requirements • Common mistakes among young teams • Some suggestions
- 3. An overview on product lifecycle 02 03 04 05 01 vNext Now, we need more from the product to gain more from the market, It’s time to review the up to date requirements v1.0+ The market asks us to add features and improvements so that we will continue our development v1.0 Now, we a real product, and we know we want to continue developing it. Sometimes it's very similar to the MVP version. MVP The area overlapped by possible products, and the market is an MVP. It’s working and expandable… From Idea to Start Everything starts with an idea, and then we need to plan and start to develop something to prove our mindset…
- 4. An overview on product lifecycle Be careful about technology because: Some tools/technologies are appropriate choices for prototyping only We do not need to buy a scientific calculator for our babies Product and Technology are two sides of the same coin Swapping engine on a moving vehicle is difficult, I swear
- 5. Where is technology stack on the product lifecycle What technologies required for implementing your idea? Can you find and hire the required professionals? What is the cost of your choice? IDEA Can you continue with acceptable velocity to v.1.0? Is it really an MVP? Did you check your internal processes? MVP V.1.0 V.NEXT Quality, Development Speed and Growing is the main priority. Are you ready? Do you have insight on Data, Market, Customer, Product? How many changes you need to be ready for the future of the market and requirements? Are you ready for new concerns?
- 6. Where is technology stack on the product lifecycle Database Back-end Development Front-end Development Product-Specific Features Product Side:
- 7. Where is technology stack on the product lifecycle Task Management Test Management Continuous Integration/Delivery Documentation Collaboration Issue Tracker Configuration Management Development Side:
- 8. What components you need to think about The main categories you have to review:
- 9. What components you need to think about The main categories you must review: Design [Interactive Mockups, Graphic Design] Support, Sales, and Marketing [Email Marketing, Marketing Automation, Help Desk, Engagement/Lifecycle Marketing, Self-Hosted Blogging/ CMS] Analytics [Analytics Integrator, Funnel Analysis Analytics, Heatmap Analytics, General Analytics] Build, Test, Deploy [Code Collaboration & Version Control, Server Configuration and Automation, Code Review, Browser Testing, ContinuousIntegration, Version Control System, Source Code Management Desktop Apps, Infrastructure Build Tools, JavaScript Testing Framework, Containers as a Service, Text Editor, Virtual Machine Platforms & Containers, Virtualization Platform, Virtual Machine Management, JS Build Tools / JS Task Runners, Front End Package Manager, Java Build Tools, Load Balancer / Reverse Proxy, Integrated Development Environment, Container Tools] Collaboration [Wireframing, Group Chat & Notifications, Project Management, Issue Tracking, Web and Video Conferencing, Agile Project Management, Password Management, ChatOps]
- 10. What components you need to think about The main categories you must review: Payments [Payment Services] Communications [Transactional Email, Voice and SMS, Mobile Push Messaging] Monitoring [Performance Monitoring, Exception Monitoring, Website Monitoring, Log Management, Monitoring Tools] Application Hosting [Web Servers, Cloud Hosting, Serverless / Task Processing, Realtime Backend / API, Platform as a Service] Languages & Frameworks [Front-End Frameworks, Operating Systems, Cross-Platform Mobile Development, Cross-Platform Desktop Development, Microframeworks (Backend), Templating Languages & Extensions, Languages, CSS Pre-processors / Extensions, Frameworks (Full Stack), Javascript MVC Frameworks] Back Office [Enterprise Resource Planning (ERP), Payroll & Benefits, Accounting, Expense Management]
- 11. What components you need to think about The main categories you must review: Mobile [Mobile UI Frameworks, Mobile Test Automation, Cross-Platform Mobile Tools] Application Utilities [Documentation as a Service & Tools, DNS Management, Search as a Service, User Management and Authentication, Static Web Hosting, Mapping APIs, API Tools, Static Site Generators, Machine Learning Tools] Libraries [Javascript Utilities & Libraries, Charting Libraries, Javascript UI Libraries] Data Stores [Cloud Storage, Message Queue, Databases] Assets and Media [File Storage, Content Delivery Network, Image Processing and Management]
- 12. Find out the correct requirements Human Resource Today, finding experts fit your needs, team culture is expensive and difficult. Features The features are coming from your ideas, market, product complexityand competitors. Scale It’s important to design your product, and its infrastructure as its size. Future is Coming… Do not try to invent everything from scratch. Existing Solutions Follow-up trends and upcoming requirements…
- 13. Find out the correct requirements Proof of Concept (PoC) Feasibility of idea Basic Idea Prototype working simulation product MVP Fully working version of product Ready to be launched MMP, MAP, etc. Time is Important Change is Expensive Market is Waiting Competitor is Watching Technology is Changing Problems will solve easier Product doesn’t mean Wish
- 14. Find out the correct requirements Be honest with yourself, your team, your advisors, this will help you with estimation and resource allocations. Check your limitations, budget & time before making decisions. Trim decisions by your requirements not by your wishes. All common and well-known technology stacks have success stories, you may be the next. Prevent copy your Eldorado
- 15. Common mistakes among young teams Spending time on personal adventures, not product adventures. These are great technologies but not for all teams:
- 16. Common mistakes among young teams re-Experiencing failures or trying to create weird solutions… resolution: asking!
- 17. Common mistakes among young teams Being a donkey who imagines himself a unicorn, or lighter dragon…
- 18. Common mistakes among young teams Internal processes and technologies are as important as your product techs.
- 19. Some suggestions Be careful about your technical interviews Get consultant before making a decision Rely on facts and numbers, rather than excitements Check benchmarks taken in your similar position Start with small but scalable solutions
- 20. Some suggestions
- 21. Thanks for your TIME As your most valuable property continues Q&A