Incorta story with product
•Als PPTX, PDF herunterladen•
0 gefällt mir•202 views
Who is Incorta? How can the product team be better partners with Incorta in this journey? Prepared and Presented by: Hichem Sellami Incorta's CoFounder.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Incorta story with product
Ähnlich wie Incorta story with product (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Incorta story with product
- 3. e)
- 4. Easy to Deploy No database required ETL and Reporting tool included Totally Web based solution Supports large volumes of data Great Performance Security integration with Source systems Incorta Advantage
- 6. Technology E-Commerce Retail Healthcare Industrial Financial Services Other
- 11. Product Focus – Next 12 months
- 12. Breaking down themes into key features for Release Planning
- 13. Challenges in Release Planning • Our backlog is really large compared to what we can deliver in a given release • This product pipeline funnel is indicative of the challenge ahead of us • But, this is not because we are not delivering enough in a release…..
- 14. 10 Customer Commits 35 Customer Bugs Look at what we are delivering! Release 4.6 in Numbers 112 Feature Stories 31 Dev Improvements 12 Technical Debt We are delivering several enhancements in an extremely tight window, right after another major 4.5 release. But, this will still not make a dent in our backlog! ~8 Weeks
- 15. So, how can we plan and execute better? • Prioritization • Managing customer expectations • Laser focus on prioritizing key themes • Break up big features into smaller chunks • Well defined business requirements by persona • Writing good user stories and acceptance criterion • Introduce more features via Incorta Labs • Agile, cross functional teams • Patching framework for customer bugs • Relentless focus on quality • Own the experience, not just the feature • Empathy for the customer journey • Knowledge sharing and education • Pluggable frameworks like connector SDK • Help identify the low hanging fruits!
- 16. How can the product team be better partners with you in this journey?
Hinweis der Redaktion
- Osama: BI Publisher, Reliable solution, PixelPerfect reports, Great performance OBIEE : Complex BI reports, bad performance
- Broadcom: Build simple schema, and load relatively large tables Stanford: Replace a heavy plsql procedure running on EBS Apple: Replace heavy plsql procedures, and download 400K table to csv
- We have a small team but big plans…
- Incorta can compete with the likes of Snowflake and Databricks. It can reshape the BI field, but for this we need to stay true to our roots of a simple solution, but become more…
- Our solution has to be a reliable solution that companies run their business on 100% of the time.
- We need to double our efforts, and each one of us should feel responsible for the solution. Each each engineer needs to double as a UI designer (don’t release anything you wouldn’t put in your facebook page), a QA engineer (take the time to think how this can break, run some unit tests before shipping it to QA), and a support engineer (how is the customer going to use this? What happens if this fails, would the customer know what to do next)? QA engineers should work with Dev team by understanding how the solution works from inside, this will help in debugging