• Liked Nikhil Joshi
    keyboard_arrow_down

    Build - Measure - Learn : Without spending a fortune

    Nikhil Joshi
    Nikhil Joshi
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    At times we have great product ideas but the biggest barrier to entry lies in answering few questions such as:

    - How do I define and validate Problem hypothesis, Solution hypothesis and Underlying assumptions?

    - How do I quickly setup a platform for people to register their interest?

    - What will keep the potential customers engaged, excited until the first release (or beta) is out?

    - How do I get feedback from the early adopters?

    - And eventually when I have answers to some of these questions, how do I make a decision to persevere or pivot?

    If you've faced a challenge while answering any of these questions while building/validating your product idea, this session is for you. We'll look at tools and techniques to validate the product hypothesis early-on without spending months or fortunes. We'll also look at a case study to highlight how some of these tools, techniques helped us validate our product idea.

  • Liked Prasanna Vaste
    keyboard_arrow_down

    Should we stop using Story Points and Velocity?

    Prasanna Vaste
    Prasanna Vaste
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    On Agile projects we estimate user stories in order to allow team to

    1. 1. Track velocity
    2. 2. Decide scope for the Iteration
    3. 3. Help Prioritize stories
    4. 4. Help Release planning

    But most of the time we faced issues with estimation. It takes lot of time in estimating user stories, managers tend to relate estimate to number of days it will take to complete the story, in some teams estimate is equal to deadline. Most of the teams which use story points to estimate the work face these issues. This results in lack of confidence on development team when stories are taking more time to complete.

    Here I am going to talk about better alternative for both the suppliers of software products (financially and ethically) and their customers (internal and external). This alternative is being used in real companies delivering to real customers with great effect where team uses count of stories completed in an Iteration as measure of progress. Will talk about how this alternative can be used to track velocity, prioritize stories, planning Iteration and for release planning.

    I will share some exmples from my past projects where team did not use story points/velocty but used count of stories completed in Iteration to measure progress and also as best indicator of future performance.

  • Liked Archana Joshi
    keyboard_arrow_down

    Applying Agile Principles in Primary School Education: An experience

    Archana Joshi
    Archana Joshi
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Intermediate

    An important issue that has plagued the Indian sub-continent is that of education and more importantly primary education. Since past few months, my weekends are usually occupied in teaching English classes to underprivileged children from 5th grade at a government primary school. As an Agile coach and a practitioner I was drawn towards unifying the concepts of Agile to help increase the quality of education.

     

    As a teacher, I was given a set of high level goal by the school administrator that needs to be accomplished every quarter. My goals for the first quarter were :

    • > Kids should be able to identify basic words
    • > Form short sentences.
    • > Converse reasonably in English

     

    I started with the traditional chalk and blackboard style of teaching focusing on the spellings, grammar, sentences, reading and so on. In initial few sessions, I quickly realized that it took too long for the kids to understand and so was not yielding the desired results. Some of the problems were like

    • > Too much focus on semantics and grammar
    • > Kids not opening up in the class room
    • > Only able to read words but not talk or frame sentences

     

    This is where I had to reflect and consider course correction in my style of teaching and Agile came to my rescue. This is a talk which highlights how Agile techniques were applied in teaching kids effectively.

     

     

  • Liked Nikhil Joshi
    keyboard_arrow_down

    Build - Measure - Learn : Without spending a fortune

    Nikhil Joshi
    Nikhil Joshi
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    At times we have great product ideas but the biggest barrier to entry lies in answering few questions such as:

    - How do I define and validate Problem hypothesis, Solution hypothesis and Underlying assumptions?

    - How do I quickly setup a platform for people to register their interest?

    - What will keep the potential customers engaged, excited until the first release (or beta) is out?

    - How do I get feedback from the early adopters?

    - And eventually when I have answers to some of these questions, how do I make a decision to persevere or pivot?

    If you've faced a challenge while answering any of these questions while building/validating your product idea, this session is for you. We'll look at tools and techniques to validate the product hypothesis early-on without spending months or fortunes. We'll also look at a case study to highlight how some of these tools, techniques helped us validate our product idea.

  • Liked Prasanna Vaste
    keyboard_arrow_down

    Should we stop using Story Points and Velocity?

    Prasanna Vaste
    Prasanna Vaste
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    On Agile projects we estimate user stories in order to allow team to

    1. 1. Track velocity
    2. 2. Decide scope for the Iteration
    3. 3. Help Prioritize stories
    4. 4. Help Release planning

    But most of the time we faced issues with estimation. It takes lot of time in estimating user stories, managers tend to relate estimate to number of days it will take to complete the story, in some teams estimate is equal to deadline. Most of the teams which use story points to estimate the work face these issues. This results in lack of confidence on development team when stories are taking more time to complete.

    Here I am going to talk about better alternative for both the suppliers of software products (financially and ethically) and their customers (internal and external). This alternative is being used in real companies delivering to real customers with great effect where team uses count of stories completed in an Iteration as measure of progress. Will talk about how this alternative can be used to track velocity, prioritize stories, planning Iteration and for release planning.

    I will share some exmples from my past projects where team did not use story points/velocty but used count of stories completed in Iteration to measure progress and also as best indicator of future performance.

  • Liked Vibhu Srinivasan
    keyboard_arrow_down

    Working at a lean startup

    Vibhu Srinivasan
    Vibhu Srinivasan
    schedule 3 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    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

  • Liked Richard Kasperowski
    keyboard_arrow_down

    Agile for Massive Scale Art and a World Record Attempt

    Richard Kasperowski
    Richard Kasperowski
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Beginner

    Imagine quickly organizing 1500 people to work on a massive project together. Imagine creating an art piece that's 100,000 square feet. Imagine doing it in three days and attempting to set a world record.

    Chalkville was a massive scale art piece and world record attempt. This is the story of how we used Agile principles and practices to organize and execute our project over six months. Agile helped us form a team of inspired loving volunteers who would do anything for each other in pursuit of our goal. Does your team have that kind of vision and drive? Find out how we did it and what we learned.

  • Liked AOUADI
    keyboard_arrow_down

    Unleash the creativity of your team to innovate

    AOUADI
    AOUADI
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Advanced

    How the Lean approach can enhance the creativity of your team within software development area ?
    What is at stake for your company and your customers ? How Lean Manufacturing can speed up this creativity process ?
    During this session,
    BG2AA company will present his feedbacks about the implementation of this
    approach for the design of his multi-tenant Software As A Service (SAAS)
     business management platform built on cloud technologies.
    How can the user's experience capture process create the value and innovate
    
Through
     concrete examples, they will explain how visual management, five whys,
    kaizen, A3 report, PDCA ... are powerful quality catalists.

  • 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.

     

  • Liked Kalyanasis Banerjee
    keyboard_arrow_down

    Large agile transformation applying Kotter's change leadership strategy

    Kalyanasis Banerjee
    Kalyanasis Banerjee
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Beginner

    Link: http://wikireedia.net/wikireedia/index.php?title=Kotters_8_steps_for_implementing_strategy

    Kotter's change leadership framework was established almost 2 decades back. This paper highlights how the same steps helped a structured, waterfall company to start adopting agility to improve time to market. 

    That there is a need for a change was understood when we started. We formed a team that created the sense of urgency.

    We established a common vision ... a simple & easily understandable one.

    We created a framework which can help people understand what does agility means. The framework was created keeping the existing constraints & process (CMMi-5) in mind.

    We worked with an existing team to pilot, proved it works, made a case study and then showcased it to other teams to give an example. This answered the FAQ … does it work for me ? This helped other teams to overcome the fear of uncertainty.

    This created the bottom-up curiosity acres the organisation, in almost every team. They all had a different question now … how can I apply this ? This started the actual transformation.