DaKiRy_PMWeekend2016_Андрій Рифяк "Product development for Enterprises: Short Survival guidelines"
•
2 likes•137 views
This document provides guidance on product development for enterprises. It discusses business models for product development versus outsourcing. It also outlines key considerations for the product itself including features, architecture, and development process. Additional topics covered include product support, documentation, versioning, marketing, budgeting, integration with other systems, security, and lessons learned. The overall message is that product development requires planning across many areas to balance expectations with reality.
More Related Content
Viewers also liked
Viewers also liked (20)
Similar to DaKiRy_PMWeekend2016_Андрій Рифяк "Product development for Enterprises: Short Survival guidelines"
Similar to DaKiRy_PMWeekend2016_Андрій Рифяк "Product development for Enterprises: Short Survival guidelines" (20)
More from Dakiry
More from Dakiry (20)
Recently uploaded
Recently uploaded (20)
DaKiRy_PMWeekend2016_Андрій Рифяк "Product development for Enterprises: Short Survival guidelines"
- 1. Product development for Enterprises SHORT SURVIVAL GUIDELINES
- 2. Who am I? Head of Department @SoftServe BS. 80+ employee dpt. 9 years in IT 9 years in Hell Project Management, 5 years in Product Developent No technical education. International Relations. IEDC MBA alumni since 2015 Heavy language damage due to professional activities Last project managed of 30 000 Mh. Lucky to have really good teachers
- 3. Who are u? PMPC BARM Sales Marketing DevQC Designers CEOGM Not sure Not raised a hand yet
- 7. Product BM vs. Outsource BM PRODUCT High start-up costs and initial investments Full cycle experience needed High rump-up costs Market analysis Done once, sold 1000 Push than pull, highly differentiated High Risk OUTSOURCE Rather quick cash Limited experience needed to start Multiple sell options: T&M, Dedicated team, Fix-bid Push, hard to differentiate Medium risk
- 8. The product
- 9. To make story short Winning recipe 1. Reach and useful feature list 2. Well built UIUX experience 3. Solid state architecture layer Translation 1. It has to do something. 2. Look sexy 3. Do not crash every 5 min.
- 10. Religion – what development process to use? Waterfall Agile
- 11. Product Scalability assessment 1 layer app 10 users 1 layer app 100 000 users 3 layers app 1 000 000 users Stress testing IT Landscape planning 1-3 years. Affects the budget!
- 12. Product Implementation Knowledge base, internal communication channels SLA, timings Scalability effect Time zones
- 13. Product support Knowledge base, internal communication channels Qualification Regional allocation Scalability based on Product features or Customers expansion Complexity leveling ITIL, 1st line, 2nd line
- 14. The box and docs Selling texts Technical writers Styleguides Userguides How to’s
- 15. Versioning
- 16. Move to market Channel Target audience Market share Competitors Pricing strategy
- 17. “My baby” syndrome NO! NO! NO! Well.. maybe ^-^) it’s so cute..
- 18. The customer
- 19. Business need behind the enterprise Money Stakeholders Interests and ambitions
- 20. Budget planning Every fall for 1-4 months CAPEXOPEX Every year need to cut costs Hard negotiations
- 21. IT Landscape Check the system environment Requirements for the software f.e. Allowed versions of the browsers/screen size Phone app – version of android. Next plans for device updates.
- 22. Security Informational Security requirements NDA Allowed softwarehardwareconfiguration
- 23. Integration with other systems What is your product surrounding? Test integration early Master data management Synthetic data if needed Secure channels and schedules VPN tunnel
- 24. Takeaway lessons Product development is fun and extremely hard Keep your eyes open and always check your assumptions The world is changing and the world is changed by us It’s always about expectations vs. reality
- 25. The end! Got more questions? Andy Ryfiak aryfiak@softserveinc.com