Gearing Startups for Success through Product Engineering
•Download as PPTX, PDF•
2 likes•204 views
In the August edition of the #99XTWebinar Series, catch two of 99X Technology’s tech experts as they share some intuitive insights into product engineering for startups, and how they harnessed digital transformation to successfully launch a product.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Gearing Startups for Success through Product Engineering
Similar to Gearing Startups for Success through Product Engineering (20)
More from 99X Technology
More from 99X Technology (18)
Recently uploaded
Recently uploaded (20)
Gearing Startups for Success through Product Engineering
- 1. Gearing startups for success through Product Engineering Webinar Series
- 2. Suren Rodrigo Consultant Software Product Engineering Sajeetharan Sinnathurai Technical Lead
- 3. Characteristics of a successful startup • Disruptive • Solve a common problem • Rock solid foundation • A road map • Luck ( maybe)
- 4. Nature of a startup project • Level of ambiguity • Validating an Idea, pivoting idea based on feedback and adopting and doing changes rapidly • Not much to start with, expecting lot in future.
- 5. Preparing for a startup project (development perspective) • Make sure the scope of the MVP is well defined and agreed by all parities • Agree on a technology stack • Assembling the right team • Make sure all team members understand the project scope • Agree on a development process and follow from day 1
- 6. Architecture and Technology Selection • Architecture • Should be Flexible both at infrastructure and feature level so we can quickly change. • Should be able to differ decisions till the last responsible point • Should take into account the cost factors • Technology selection • Should be a proven technology • Should be a technology the team is familiar with (No time to experiment)
- 7. Essential Engineering practices for startup projects • Continuous Integration • Continuous Code Quality Analysis • Continuous Regression Testing • Continuous Vulnerability Testing • Continuous Deployment to Staging and other relevant environments such as UAT and Production • Test First Development (TDD) • Automated Testing • Unit Testing • Regression Testing • Peer review • Bug tracking and root cause analysis
- 8. Development process for startup projects • Agile process Backlog grooming Sprint planning Daily stand-up
- 9. Development Manual Testing Continuous Integration Automated/regression testing Steps involved in the process
- 10. Managing startup project • Micro management does not work • Alpine style of climbing
- 11. Perfect startup team • Hustler – Sell the product • Hacker – Build the product • Hipster – Pimp the product
- 12. What makes a perfect team? • Trust • Motivation • No hierarchy • Embraces different ideas and opinions • Not afraid to challenge • Respect one another • Knows other team members beyond professional level
- 13. Common Mistakes in a startup project • 90% of startup fails. • Trying to implement too many features • Having no specific users in mind • Slowness in launching • Failing to delegate • Delaying to implement essential engineering practices • Delaying to adhere to proper management process
- 14. References • http://theleanstartup.com/principles • http://startupsecrets.com/ • http://startupery.com/ • http://www.danpink.com/books/drive/
Editor's Notes
- Welcome all Introduction for the topic Sharing some insights on startup and what practices can make things effective
- Introduce speakers Tell story -babysitting Startup mentality is your own baby , 24/7 is what they are , ongoing thing ,little of pain sometimes lot of pain but infinite love.
- Distruptive – Redefine markets and deliver values in new ways – Everyone remembers apple iphones but we forgot the fact that it arise from music ipods Solves a common problem – Large scale solution Rock solid foundation – most successful startup always had solid foundation in terms of having good team which makes the journey fun, resources architecture etc A road map – opportunities,impacts and related kpis, dependencies and risks should answer the questions what are we doing and why are we doing? Luck - The harder you work, the luckier you get
- Level of ambiquity - When you are working in a startup that is dealing with a lot of different things all at the same time it’s really easy to lose sight of what’s important. Validating an idea – Everything starts with an idea, it’s the execution that matters. Ask family, professors, friends and people whom you trust about your idea and what they think about it. If the feedback is positive with a couple challenges identified, do a deeper level validation by asking potential customers or users of your product. create a Minimum Viable Product (MVP) . create a detailed business plan based on data and learnings from your MVP Limited resources , Start-ups should not take investments until the idea is validated and they get some traction. Once the idea is validated there is lot to do Well we have discussed the nature of a startup project. We already spoke about having a solid foundation? Suren what are the things that needs to be in place before start coding?
- Mention that these practices are common to normal projects as well. But in Startups it’s a must
- Mention that these practices are common to normal projects as well. But in Startups it’s a must
- Mention that these practices are common to normal projects as well. But in Startups it’s a must
- Agile method suits the best for startup projects. Usually two weeks sprint where we have the retrospective and feature demo on last day of sprint Backlog grooming - Continuously update and re-prioritize the backlog so it's up to date (on a daily basis) Sprint planning - plan and prioritize the work to be completed within the next 14 days Daily standup – Best approach to get the right feedback from customer iteratively and hence the right product market fit. Since Continuous integration is followed, so getting changes into staging can happen the same day. Most often we do a release at the end of a sprint.
- - A new branch is created for a corresponding story/bug - Running of code reviews before the code is passed to technical QA
- Micro management - It does not really work in a startup because you do not have time to, you should trust the professionals, if not you have hired the wrong people. Product owner – Responsible for what the product should do. when we talk about small teams like startup this is more like alpine style of climbing, should be able to adapt quickly changing conditions , require few resources, each engineer might have to have more skills , you have to be self sufficient and you have to go with what the conditions allow you to do, in startup no one knows all answers and the thing is you have to learn quickly
- work with marketing team to get the ideas work with the designers and this more collaboration creates more understanding can make engineers to make better decisions when it actually comes time to do the code. we make thousands of tiny decisions when we are implementing, product manager in a startup will not have thought of every single detail or edge case that can come up, if you make the engineers to understand what the goal is then it helps to make better decisions You should always communicate , if that does not happen, product just ends up getting delayed and delayed and no one knows why things are not getting shipped.
- Mention that these practices are common to normal projects as well. But in Startups it’s a must Trust : Everyone has a different role, but should act together. Everyone is dependent on each other. Great team is made up of team members completely trust another. Motivation : Second super power is motivation. It makes engineer productive and happier. After spending lot of time at work, not being motivated is really draining No hierarchy : Should be able to make decisions Not afraid to challenge : Key factor is ability to challenge Knows other team members beyond professional level : The best team is when all other team members come together to offer help in loosening that bottleneck when they realize assistance is needed there. As a team, to get things done and move things forward. That, is what we call teamwork.A well-bonded team is necessary for a successful startup. Succeed together as a team or fail together as a team.
- "Your start will never be an impressive one. You got to move on, learn from your own mistakes, failures - Focus on #Continuous Improvement - Sooner or later, you are gonna say, this is where I wanted to be"