• Liked Arvi Krishnaswamy
    keyboard_arrow_down

    Lean Startup in Practice - Lessons Learnt from an MVP

    Arvi Krishnaswamy
    Arvi Krishnaswamy
    schedule 2 years ago
    Sold Out!
    45 mins
    Case Study
    Advanced

    Rovio tried 51 games before hitting upon Angry Birds. We tend to hear a lot more about the chart busting numbers of Angry Birds than the struggles of the previous 51 games. In my opinion, their success was the journey of the 52 experiments, and not just the final one.

    We at Levitum recently had learnings from an MVP that we put out, and experiments that we ran. In the spirit of openly sharing how I’ve tried to apply Lean Startup principles to a new venture, I’m going to outline how we went about things, and what I’ve learnt.

    More details on the experiments are available in my blog post http://arg0s.in/what-we-learnt-from-a-failed-mvp.html. My blog post made page one of HackerNews, has had over 20,000 visitors, and has been cited by various practitioners as an example of how to apply lean startup in practice.

  • Liked Tathagat Varma
    keyboard_arrow_down

    From Waterfall to Weekly Releases: A Case Study in using Evo and Kanban

    Tathagat Varma
    Tathagat Varma
    schedule 2 years ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    In 2003, we had a major problem to solve - our products had far too many open field defects, and the bug arrival rate was moe than the closure rate. We tried to fix using our process which involved shipping quarterly service packs, but that was not only elongating the lead time, it was also not very amenable to changes. The process for customer specials (specific features, etc.) was not any better, and invariably it led to exec-level escalations just to get some deal-blocking customer escalations into the service packs mid-way in the quarter.

    In 2004-05, we experimented with a pull system that limited the work in progress and created a more smoother flow of value. The result of this system was that we were able to significantly reduce the defect backlog, and were able to bring down cadence of features and bugs to a weekly cadence. The experiment was so successful that in about 6 quarters, we had fixed most of the field defects (brought down individual product's defect backlog to single digit) and we had to disband the team as there was no work left for them!

    We were inspired by Tom Gilb's "Evo" method and experimented with it to create a weekly cadence. However, we found that the nature of field defects and customer specials was stochastic in nature and didn't lend itself very well to a timeboxed framework like scrum. However, there were no off-the-shelf methods available back then that were a viable alternative. Hence, we experimented with various methods and blended-in elements form various methods to create out our very first kanban by limiting work in progress.

    In this talk, I will explain our first kanban experiment, and also compare and contrast with the later-day Lean Kanban by David Anderson.

  • Liked Niranjan N V
    keyboard_arrow_down

    Mr.Agile Leader - “ Develop People or Solutions”

    Niranjan N V
    Niranjan N V
    schedule 2 years ago
    Sold Out!
    20 mins
    Experience Report
    Intermediate

    Based on my experience of coaching/ training agile teams for 5 years, one of the important reasons for agile teams are impacted, is the personal leadership style of Agile Leaders(Scrum Master, Senior Managers etc) . I have summarized following, factors or impediments for creating effective agile teams

    • The agile teams effectiveness depends on personal leadership style of agile leaders(Scrum Masters, Senior Management etc)
    • Often Agile leaders focus more on “delivering solutions” than “developing people”.
    • Agile leader need not specify work requirements, all that team needs is - empowerment, autonomy to work.
    • The agile team needs more support through mentoring, coaching from agile leaders to exhibit the culture “Being Agile” than “Doing Agile”.
    • Agile leaders need not be an Expert to coach agile teams.
    • Agile teams needs to be taught on Identifying Problem, Problem solving skills and corrective actions and demonstrate steady, small and continuous improvement.

     

    My inspiration to write here, is derived from the book “ Managing Excellence” by David Bradford and Allan Cohen, and reading blogs, articles along with my own experience.

     

    The entire presentation will be done in “Pecha Kucha Style” with less words and more background pictures, in each slide. The most of the message is conveyed through pictures. The presenter will talk maximum 30 secs on each slide. The slides keep changing automatically after 30 secs, so that presenter continues the discussion in the next slide automatically

  • Sneha Kadam
    Sneha Kadam
    schedule 2 years ago
    Sold Out!
    60 mins
    Workshop
    Intermediate

    After revolutionizing the automobile industry, Lean principles have been successfully applied to different knowledge areas including software development. This workshop is intended to master Lean concepts like Waste, Push&Pull systems, systems thinking, Kaizen etc. & practicing cross-functional collaboration, self-organisation and safe-fail experimentation! In this interactive game, the participants will work in a small production lines, experiencing problems and applying Lean practices to overcome them.

  • Jeff Lopez-Stuit, CEC
    Jeff Lopez-Stuit, CEC
    schedule 2 years ago
    Sold Out!
    20 mins
    Pecha Kucha
    Beginner

    How can teams that have to deal with large, complex legacy systems get through planning and get to work? The title character of the classic American horror film, "The Exorcist" was a master at this..

    Pecha Kucha Talk Summary:

    • Introduction: Creating understanding through conversation can be very difficult for teams dealing with complex, legacy systems.

    • Introducing Regan McNeil: Poor Regan McNeil was starting go insane, but a team of doctors and specialists in close, face-to-face collaboration, couldn't solve her problem.

    • The Exorcist: The Exorcist knew how to have just enough conversation to get to work, so his team could deliver the value everyone had been working and praying for.

    • Summary: "In life, understanding is the booby prize". Sometimes the quest for understanding can be an impediment to delivering value. Having faith in self-organization, sometimes its best just to get to work.
  • Darren Davis
    Darren Davis
    schedule 2 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    Kanban is one of the fastest-growing development methodologies today.  Teams increasingly turn to Kanban to simplify and streamline their agile development, but few people know the inside story of how and why Kanban was created.  The Secret History of Kanban pulls back the curtain and gives you a first-hand account of how Kanban went from being a colossal failure to a startling success, presented by one of the original team leaders.  Learn how a team turned theory into practice, what it means for the future of Agile, and how you can apply those lessons in your own organization.

Sorry, no proposals found under this section.