Working at a lean startup

I have had the oppurtunity to build and be part of a few successful and failed startups. One such succesful startup was my association with a startup called Evri.com. I have also consulted as a developer and coach for a gaming company called BigFishGames which went to become a largely succesful gaming company making one game a day today. 

In this session I would like to tell the story of what happened at Evri and Big Fishgames that made them succesful. 

This is a lessons learned, observatiosn shared being part of this startup as a developer. This session also looks at what makes a good product. Is product creation a pure idea of a bunch of geeks working together or something more than that. 

 

Come see and learn

 
2 favorite thumb_down thumb_up 7 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

This is a casestudy of the what I learnt at Evri and BigFishGames and another startup called VendorNetworks. This session is without slides and uses story telling and experience of what made two of these startups go well and one to fail.

 

Learning Outcome

- Things to plan for when creating a product

- Innovation Ideas

- Working with the market to create a product.

- Concepts from a Lean Startup.

- Mistakes and pitfalls to avoid in a startup

Target Audience

Startup founders, developers , testers

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • gnuyoga
    By gnuyoga  ~  3 years ago
    reply Reply

    Hi Vibhu,

    Will be great to see you past recording of your session.  Plus i was looking for your presentation unfortuntely i could not find the same, will be great if you can paste the URL of the same. 

    If your approach more generic which can be applied to any startups / product development ? 

    -S

     

  • Nitin Ramrakhyani
    By Nitin Ramrakhyani  ~  3 years ago
    reply Reply

    Hi Vibhu,

    Thanks for your submission. I have heard you previously, so no doubt that it would be a very interesting talk. A quick check, don't you think this would fit better in 'Beyond Agile' theme where most of the Lean/ Kanban talks are being submitted or do you have any specific focus in mind to submit it in the Agile lifecyle part ?

    Thanks,

    Nitin

    • Vibhu Srinivasan
      By Vibhu Srinivasan  ~  3 years ago
      reply Reply

      Hello Nitn, Thanks for your kind words. Based on your tips i moved it to beyong agile. The reason I was struggling is we never thought at this start up ever if what we did was agile or scrum. There was no time to think about such things and I think that is what made us succeed in the end

      I have moved the theme.

  • Joel Tosi
    By Joel Tosi  ~  3 years ago
    reply Reply

    I agree with Nitin on this.  It sounds like an interesting experience, I wonder about the fit.  If the fit is right, I would still like to see a little more information.  Since there isn't slides, what are some of the innovation ideas you would be covering along with some of the pitfalls for example?

     

    Thanks much,

    Joel

    • Vibhu Srinivasan
      By Vibhu Srinivasan  ~  3 years ago
      reply Reply

      @Joel Thanks foryour feeback. I have updated some of my thoughts on Nitins comment above.

      Some of the stories i want to share are

      1) Working on the first release

      2) Forming teams

      3) Building complex systems when you do not know your customer

      4) How things changed drastically when  the first customer was singed

      5) How having customes increases clarity and removes waste in startups

      6) To what extent a self organizing team can go to keep the servers running

      7) How using all macbooks helped us?

      There are many more simple stories like this

      I am still working the details.

  • Sachin goel
    By Sachin goel  ~  3 years ago
    reply Reply

    I would like to see how session will be conducted, as in what is the agenda. Also the theme at this stage seems little out of sync with Agile Lifecycyle.

    thanks

    Sachin

    • Vibhu Srinivasan
      By Vibhu Srinivasan  ~  3 years ago
      reply Reply

      @Sachin Thansk for your feedback . Apologies for a bit of delayed response. I have moved this to beyond agile. the problem is at this startup we never thought of this as Agile. We worked in a certain high energy way with customers in mind. Since this is a experience report I will be sharing this through story telling with pictures and hand drawn art so that participants cna visualize. I am hoping to tell the story so that any one in the audienec who are currently doing a startup can related to that.

      I also will be talking about tecnology challenges we had and not just process  Evri was a symantic web start up at that time and people had to write complex algorithms in short amount of time.

      Story telling is a poweful way of communicating ideas and that i what I plan to use

      I will be happy to answer any more queries.


  • Liked Naresh Jain
    keyboard_arrow_down

    SAMPLE PROPOSAL - Product Discovery Workshop

    Naresh Jain
    Naresh Jain
    schedule 3 years ago
    Sold Out!
    90 mins
    Tutorial
    Beginner

    Many product companies struggle with a big challenge: how to identify a Minimal Viable Product that will let them quickly validate their product hypothesis?

    Teams that share the product vision and agree on priorities for features are able to move faster and more effectively.

    During this workshop, we’ll take a hypothetical product and coach you on how to effectively come up with an evolutionary roadmap for your product.

    This 90 mins workshop teaches you how to collaborate on the vision of the product and create a Product Backlog, a User Story map and a pragmatic Release Plan.

    This is a sample proposal to demonstrate how your proposal can look on this submission system.

  • Liked Bhuwan Lodha
    keyboard_arrow_down

    Building a Team Backlog: The Power of Retrospectives

    Bhuwan Lodha
    Bhuwan Lodha
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    “Inspect and adapt” is one of the basic tenets of continuous improvement, and agility in general. Holding retrospectives is one of the core processes that allows teams to look back and reflect on their progress. However, over time, teams may focus only on the product work and lose interest in their own improvement as a team. Kanchan Khera and Bhuwan Lodha believe that one approach to solving this problem is to bring the rigor, structure, and discipline we use for maintaining healthy product backlogs to team improvement by creating a “team backlog”—items the team needs to do to improve itself. The team backlog introduces three keys to successful and sustainable team improvement—a structured framework, visibility of its impact, and creative ways for building the backlog. Just as a healthy backlog is the basis for a great product, so a healthy team backlog helps create great teams.

  • Liked Prerna Kale
    keyboard_arrow_down

    Cent Cent Business Value! A Sneak Peek at sprints from evolving design/UI, getting right priorities to delivering $$

    Prerna Kale
    Prerna Kale
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

     

    We want to share experience of working on a complex project, with deadlines set upfront and all players distributed. Perhaps argued as a complex combination to have but yet we were right there, on time enabling the new tool there. Reporting systems often have evaluation cycle that have imperative timelines to start and freeze, hence working for a huge system was not easy. Right agilist mindset with right agile practices helped us meet this. As a Product owner I jostled with eight experts using one system with some variation for their own service lines. We want to show how we leveraged the benefits of distributed teams balanced the challenges, kept the UI flexible enough to accommodate 8 expert reviews, and how our evolving architecture designed a system that had the most used and important features for the users to try hands on..

    Introspecting and sharing how we ensured Cent Cent business Value:

    - Kick off the project with eight stakeholders that got the ball rolling
    - Identifying the 30 % that was core to the business
    - Inspecting, and adapting to constant changes with modular designs
    - Getting stakeholder agree on priorities
    - Release Backlog with stories and design with validated acceptance criteria
    - Managing challenges and ensuring meeting needs seamlessly with truly distributed teams (Distributed PO/Designer/Architect/ Team/ Stakeholders)

    How important is it to dig the core 20-30% in projects with deadline upfront and ways to do that.. Prioritization techniques that enabled mutual agreement on the needs. Backlog with designs that reduced the development time. How work effectively with distributed teams, by building trust, keeping motivation and sharing the definition of done- yes we lived it and did it! We want the audience to explore it all with us and be open to take up and successfully meet the projects with distributed agile teams and tight deadlines yet agile :)

  • Liked Ted Tencza
    keyboard_arrow_down

    Creating a Great Engineering Culture in an Agile workplace.

    Ted Tencza
    Ted Tencza
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Company culture, or its DNA, is one of the most important factors to determing if a company succeeds.  Many companies claim to have great company culture.  But what does this mean, how can you know if your company has a great culture, and how can you go about improving the culture?  This talk will explore what great companies have in common, and share experiences I have had in helping to develop engineering culture during my career.    

    Will also explore how Agile principles help to foster creating the best possible culture for your organization.

  • Liked Vibhu Srinivasan
    keyboard_arrow_down

    Coding with Geeks- De Code the secrets behind TDD, BDD and ATDD

    Vibhu Srinivasan
    Vibhu Srinivasan
    schedule 3 years ago
    Sold Out!
    90 mins
    Tutorial
    Intermediate

    This session is a coding sessiont that takes a problem and shows clearly what is the difference between TDD, ATDD and BDD. Ths session uses code for the server layer as well as UI layer.

    This session is not for you if you do not code. If you do code, please bring your laptop as we delve into the details of all these styles of programming techniques.

    We will rotate between ATTD, TDD and BDD periodically and show it at use in different layers. This session will be using Java , Rails, Scala and C# together so that you can see how you can benefit do these techniques even when coding in different languages.

    We look at common pitfalls and wrong beliefs that programmers have when it comes to these concepts

    This session is purely keyboard and you will have to bring a laptop.

  • Liked Kanchan
    keyboard_arrow_down

    Come! Take a plunge with us into the world of Self Organization!

    Kanchan
    Kanchan
    schedule 3 years ago
    Sold Out!
    90 mins
    Workshop
    Intermediate

    In agile teams there is a belief that the teams self organize. But do we really understand what this really means? The scrum guide simply says three things autonomous, self transcendent, cross functional.

    In this interative workshop we will experience what self organization is all about via a fun filled game. You will go back with key learnings through your own experience. 

    This session will be a combination of audience participation in activities, discussions combined with presentations and loads of fun!

    This interactive game session is for anyone who wants to learn more about  being self organized and what makes the self organized teams tick.

  • Liked Lalatendu Das
    keyboard_arrow_down

    Setting agile teams for success – Use of Operations Research to improve agility

    Lalatendu Das
    Lalatendu Das
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    While there is a good amount of literature on how an existing agile team can self-organize to deliver higher business value, very little has been said about how to use learning from one team on another or how to set new agile teams for long term success.

    In our organization, a typical engagement lasts for 6-8 weeks, leaving very little time for team ramp-up. Setting teams for success was not aspirational but a core ingredient to our service delivery. We explored the field of Operations Research (OR) and applied some of the techniques to software engineering. In this experience report, we are going to share how we leveraged OR concepts such as “Queueing Models” and “Network Optimization” techniques to identify

    - What should be the ideal size of a story to deliver optimal value

    - What should be the optimal team staffing for a given scope of work

    - How to get more predictability on release plans of agile projects

    While our research in this field has been tailored to a very specific type of work we do, the concepts and learning can have wider application.