Build - Measure - Learn : Without spending a fortune

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.

 
 

Outline/structure of the Session

Outline:

- Introduction to lean startup thinking (5 Mins)

- Tools and techniques (5 Mins)

- Case study/Experience report walkthrough 5 Mins)

- Q&A (5 Mins)

Learning Outcome

The biggest learning from this session will be to overcome couple of myths:

- If I can't write code, I can't validate my product idea

- I need "X" amount of money/efforts to validate my product idea

Target Audience

Product enthusiasts

schedule Submitted 3 years ago

Comments Subscribe to Comments

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

    Nikhil,

     

    Do you think you can convert this to a 20 minute experience report? Focusing on the important topics

    • Nikhil Joshi
      By Nikhil Joshi  ~  3 years ago
      reply Reply

      Hi Pramod,


      Yes I can. In this case, I will cut short the concepts and focus only on the tools and experience report.


      Cheers,

      Nikhil

      • Naresh Jain
        By Naresh Jain  ~  3 years ago
        reply Reply

        Thanks Nikhil. Request you to please update the proposal accordingly.

  • gnuyoga
    By gnuyoga  ~  3 years ago
    reply Reply

    Am particularly curious  "How do I get feedback from the early adopters? and also about Validation" i think lot of product companies struggle to get this right. Questions like What to watch for, what are the common metrics to measure against, etc..  is something i keep getting when i interact with enterprenuers.  

    Will be great if you can share your video after Agile Goa. Will help understand your presepctives better. 

    All the best for your session @ AgileGoa. 

    • Nikhil Joshi
      By Nikhil Joshi  ~  3 years ago
      reply Reply

      Hello Review Team,

      Thanks for all the feedback and thought provoking questions/clarifications. Unfortunately, video recording wasn't available at Agile Goa conference. However, the session was received very well. There were couple of other Agile India core team members as well in the audience, I am sure we'll get feedback from them around the content, layout and presentation style. 

      Also, looking at majority of the audience at Agile Goa which was primarily academic, I had to focus more on the concepts along with the experience report. However, if the talk gets through at Agile India 2014, I'll need to tweak it more towards the practitioner aspects, skipping/focusing little on the basic concepts of lean startup. Hope this information helps, please let me know if the review team needs any additional info.


      Cheers,

      Nikhil

  • Tathagat Varma
    By Tathagat Varma  ~  3 years ago
    reply Reply

    Nikhil - Agile Goa is now just a week away and look forward to your session there. Meanwhile, can you share you presentation outline and any video of your past presentations (or make a quick video on your phone) so that review panel can make the final call?

    thanks, TV

    • gnuyoga
      By gnuyoga  ~  3 years ago
      reply Reply

      @Nikhil,

      Have you presented the same in other conferences ? What was the feedback ? If you could share the video link that will be awesome. 

      • Nikhil Joshi
        By Nikhil Joshi  ~  3 years ago
        reply Reply

        Hi,

        Thanks for your interest. Well, I haven't presented the exact topic anywhere else but this one will have snippets from my presentations in other conferences.

        • gnuyoga
          By gnuyoga  ~  3 years ago
          reply Reply

          @Nikhil,

          Will be great if you can share the same. Any other conference that you are preenting the coming week's/month where we can have your session recorded ? 

          • Nikhil Joshi
            By Nikhil Joshi  ~  3 years ago
            reply Reply

            The same talk has been shortlisted for "Agile Goa 2013" happening in September this year. I can share the video after the event if we can wait till then.

            Cheers,

            Nikhil

    • Prasad
      By Prasad  ~  3 years ago
      reply Reply

      Nikhil,

      I agree with most of the comments raised Ted, TV and Pradeep. Leanstartup 101 may not be exciting

    • pradeep panda
      By pradeep panda  ~  3 years ago
      reply Reply

      Hi Nikhil,

         I am sorry if i am missing the real essence, but not sure what are we stressing here to convey the message that, this topic falls under beyond agile ? Moreover, in short can you highlight how the approach is related to agile way of working.

      • Nikhil Joshi
        By Nikhil Joshi  ~  3 years ago
        reply Reply

        Hi Pradeep,


        Thanks for reaching out. The approach I'm proposing is not new, it's the "Lean startup thinking" but "In action". Meaning, we'll look at tools/techniques which really enable us to make most of Lean startup thinking while applying it to any startup/product idea. In my opinion, it goes very much in hand with the agile way of working as it enables us to validate the problem/solution hypothesis early on in the lifecycle. In short, the tools/techniques which we'll talk about in this session will enable us to do "Inspect and Adapt". As the tools/techniques are not just limited to "Agile lifecycle" or tailored for "Agile transformations/adoption" I thought "Beyond Agile" is the most appropriate umbrella for such topic. Hope this answers your query, feel free to reach out if you have more questions/feedback around the topic.

    • Ted Tencza
      By Ted Tencza  ~  3 years ago
      reply Reply

      Hi Nikhil

      Is this an intermediate level talk? It looks more like an beginner level introduction into the concepts of Lean Startup.

      Can you provide a bit more detail about the Case Study? Was it a success? It the company/product/idea still going? Were the tools and techniques of Lean Startup responsible for the success (if it was a successful project/product)?

      • Nikhil Joshi
        By Nikhil Joshi  ~  3 years ago
        reply Reply

        Hi Ted,

        The case study will basically talk about my own experience while validating a product concept for performing arts/theater industry in India. Although it's a big industry here, the opportunities for theater artists to get connected are quite limited. Like any other nascent product idea, everyone we approached felt there's a huge potential, we needed solid data pointers to validate the idea before spending too much time/energy on it. With the techniques that I'll share in this session, we were able to get this validation quite early on. Was it a success - depends on our definition of success but if it's validating the potential in any idea early on without a considerable "development" effort or "sizable monetary investment", we had a huge success.

        I am open to call it a "Beginner" level session if these tools/techniques are well known for any product enthusiast. In my experience they're not, we jump at implementation too early, spend months building something that you can get to the customer in hope of creating a "big" impact. Often this results in many invalidated "assumptions", the learning outcome from this session is exactly knowing right tools/techniques to identify and minimize these unknowns.

        Cheers,
        Nikhil

        • Tathagat Varma
          By Tathagat Varma  ~  3 years ago
          reply Reply

          Nikhil - we expect that most attendees already are aware of basic concepts (in a conference like this). What might make the session more engaging is if we have a story - there is a problem that needs to be solved and we apply conventional methods and don't quite get the level of success. And then we look at some other methods (or even 'discover' some of them in the process) and apply them. People are really interested in knowing how you applied some of these principles into solving a real-world problems and what did you accomplish, rather than going through the model itself, especially since this is an experience report session that you have proposed. Do you want to consider 'pivoting' your proposal to bring those nuances more sharper than only looking at them as a case study?

          -TV

          • Nikhil Joshi
            By Nikhil Joshi  ~  3 years ago
            reply Reply

            Thanks for your feedback TV! As I've shared in earlier reply, we'll take an example of a "real world" problem (A startup idea that I carried for nearly 3 months) with an objective of evaluating the potential in the product idea before focusing too much on the solutioning aspect. Obviously, we had quite a few learnings and found out few interesting opportnities while closely monitoring the usage/adoption using few of the tools we'll highlight during the session. Introduction to lean startup thinking is only going to be say a 5-10 min slot at the start of the session primarily for folks who're new to it. But I take your point to reduce it even further and focus more on our journey during those 3 months. I've updated the outline.


    • Ram Srinivasan
      Ram Srinivasan
      schedule 3 years ago
      Sold Out!
      90 mins
      Workshop
      Intermediate

      It is not a question of if a team is going to have a conflict; it is a question of when. Equipping them to deal with conflict is more than creating agreements or having a good facilitator. We look at a conflict model that focuses on dynamics of conflict by understanding- 1. Cognitive skills:self-awareness about triggers, hot spots, emotions,behaviors. 2. Emotional skills:reading emotions, body language, balancing emotions, using curiosity 3. Behavioral skills:understanding others’ perspectives and needs, avoiding 8 destructive behaviors, embracing 8 constructive behavior. In an organizational setting, it is important to understand the source (culture, interdependence, incompatibility, personality, power, etc.) and types of conflict (cognitive vs. affective). Creating awareness about conflict processes, retaliatory cycles and building a conflict profile can empower teams engage in constructive disagreements. 

    • Liked Mushtaq Ahmed
      keyboard_arrow_down

      Using a modern web framework for big enterprise agile project

      Mushtaq Ahmed
      Mushtaq Ahmed
      schedule 3 years ago
      Sold Out!
      20 mins
      Demonstration
      Advanced

      At ThoughtWorks, a 50-people team is building a marketing website backend for one of the largest consumer electronics brands in the world. We are Play-Scala as our web framework which allows us to design the application in a very different but powerful ways. This experience based talk will talk about these differences, emphasizing on two of them: "Dealing with concurrency without threads" and "Dependency resolution with constructor injection".

      Dealing with concurrency without threads
      - The backend is end to end non-blocking with highly concurrent architecture
      - Each page consists of 20+ reusable snippets, so each page request translates into 20+ outbound web service calls to get data for the snippet data in parallel
      - Posting data involves download/upload of large images from/to remote services, also done in parallel
      - We will show you how Scala Futures, Play and ReactiveMongo functional programming paradigm allows us to do all this without blocking any thread or managing thread-pools by hand

      Dependency resolution with constructor injection
      - Dependency injection is considered essential for designing applications that are easy to test. Usaully, dependencies are specified as constructors parameters
      - Scala traits allow us to get rid of constructors by wrapping classes and their factories inside components that in turn can depend on other components, this enables a compile time mechanism for dependency resolution which is very flexible
      - We will show examples of this pattern, its effects testing without external DI frameworks

      We will briefly talk on how functional programming style in general helps with testing and software delivery on agile projects. Finally, we will also cover the pain-points these approaches bring out, and argue if it is worth to pay that cost.

       

       

    • Bimlesh Gundurao
      Bimlesh Gundurao
      schedule 3 years ago
      Sold Out!
      45 mins
      Case Study
      Intermediate

      Transforming a Business to be Agile involves a lot of moving parts. Being Agile not only means delivering high quality software, but ability to respond to changing Customers Needs/Markets/Competitors/Stakeholders and more. Fundamental to this change is "People" within the organization. Keeping “People Over Process” at the center its important  to facilitate the People in the organization to be fully successful. So how do we ensure they are successful? How does goal setting change? How does measurement of these goals change? Focus on Organization adoption to Agile largely has been limited to Engineering function. But how has the HR process changed to facilitate this transformation to be truly successful?

      In this session will look to bring in some of the best practices that are followed in the organizations through a Mix of Case Study and Research across Product and IT Services Organizations.

    • Liked Karthik Kamal Balasubramaniam
      keyboard_arrow_down

      7 Deadly Sins of 'Agile- But' Teams

      Karthik Kamal Balasubramaniam
      Karthik Kamal Balasubramaniam
      schedule 3 years ago
      Sold Out!
      20 mins
      Experience Report
      Beginner

      This report is based on the analysis of the epidemic called ‘Agile-But-Teams’ in services organization. The presentation would cover the following 7 anti-patterns in such teams,

       #1 Fix ‘everything’ in your contract (definitely no breathing space) 

      Sign contracts with fixed scope and penalties. Ensure you include at least 30 metrics with fixed targets without accounting for team’s capability.

        #2 Don’t groom your requirements, make them look beardy and scruffy 

       Ensure your product backlog grooming is either not taken seriously or not done until the first day of the sprint.

       #3 Be a salary thief and never change a thing 

      Freeze your process steps in the beginning of the project and create checklists that would ensure compliance on a monthly basis. If possible, include mechanisms for tailoring and deviation, but never change the process.

       #4 Be loyal to the law of averages 

      Set organizational baselines for Agile teams and measure them periodically. Also, get RCA’s and reasons for missing the organisation targets.

       #5 Trust the pyramid and mummies 

      Adhere to the team pyramid structure and give the product responsibility to the identified leads.

       #6 Never Tell, Only Ask 

      Never change your product development/testing practices empirically instead implement industry ‘best’ practices based on case studies from other projects.

       #7 Make Self-fulfilling prophecies 

      Constantly discuss about, how Agile is not the right model for your project. Ensure your prophecies are fulfilled and there is no redemption whatsoever

       The presentation would also cover the possible antidotes for the scenarios and explain in detail about the behavioral sciences behind such patterns.

    • Liked Prabhakar Karve
      keyboard_arrow_down

      Inspect and Adapt – Powerful technique to increase productivity through continuous improvement

      Prabhakar Karve
      Prabhakar Karve
      schedule 3 years ago
      Sold Out!
      90 mins
      Workshop
      Intermediate

      Inspect & adapt is an important agile practice. Inspection helps us to see the reality beyond our filters. Better awareness of reality helps us to more effectively re-plan our work and modify our existing way-of-working.

      There are multiple benefits of this practice, but in this workshop we focus on how it can lead to continuous improvement in productivity.

      Inspect and adapt can be used while carrying out regular work activities across the entire agile life cycle. However our focus will be on the Scrum ceremonies and common artifacts.

      In this workshop, through discussions and exercises, we explore Innovative ways to expand our capability to carry out inspection & adaptation, without adding any extra overhead.

      During the session you also get a few simple yet powerful tips which can be practiced immediately once back from the conference.

    • Liked Naresh Jain
      keyboard_arrow_down

      Scaling XP Practices inside your organization using Train-the-Trainer Model

      Naresh Jain
      Naresh Jain
      schedule 3 years ago
      Sold Out!
      90 mins
      Workshop
      Advanced

      How do you effectively scale skill-based, quality training across your organization?

      Over the years, I've experimented with different ideas/models to scaling skill-based training across an organization. In the last 4 years, I've pretty much settled down on the following model. Its very useful when mentoring teams on skills like Test-Drive-Development (TDD), Behavior-Driven Development (BDD), Product Discovery, Writing User Stories, Evolutionary Design, Design Patterns, Problem Solving, etc. I've successfully implemented this model at some very prominent fortune 500 enterprises.

      The goal of this workshop is to explore what other successful models organized have used to scale skill-based training in their 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 Abhilash Chandran
      keyboard_arrow_down

      Agile Appraisal: Sprint Iterations for Appraisal reviews

      Abhilash Chandran
      Abhilash Chandran
      schedule 3 years ago
      Sold Out!
      45 mins
      Case Study
      Beginner

      Appraisal reviews are always hard. Traditionally it is done once a year. The manager and employee undergo a tough period of reviews, discussions and ratings. At the end no one is happy.

      • Manager
        • Manager is forced to provide a feedback of an entire year in few minutes.  
        • Because of time constraints and lack of useful data, a constrictive feedback is not given.
        • In most of cases this ceremony is reduced to mere salary negotiations.
      • Employee
        • Employee feels cheated because of lack of any concrete feedback
        • Employee is not able to proactively discuss his/her career objectives and create a proper plan to bridge the talent gap.

      In this talk I will discuss some of the approach we are trying to follow in our group to align appraisal feedback also along with agile sprints.  

      I will present the experience report of how we are converting the age old waterfall appraisal process to Agile. I will discuss the need for this change, the general idea and the challenges we are facing.

      In this new way of appraisal management the focus is on the individual. Just like we have a Scrum/Kanban board, each employee will have a talent and improvement board. Instead of developing a product, the focus is to develop an individual. Like the scrum there are Ceremonies

      • Release planning – Organizational agenda
        • Decide Group & team goals
      • Sprint planning
        • Work with each team members to identify some “traits”/action points to improve
      • Review
        • Review the outcome
      • Retrospective
        • Based on the outcome revisit the individual goal & do a re-planning
    • Sharad Julka
      Sharad Julka
      schedule 3 years ago
      Sold Out!
      45 mins
      Talk
      Intermediate

      -Open Source development depends a lot on community, their feedback,

      their suggestions, their reviews and their enthusiasm.

      -For an open source development project, the community itself is the first customer.

      -Product release for the community provides a good starting point to assess

      how the product will be accepted in the market.

      -This is very beneficial as it gives the software development team an edge over

      its competitors as it gets the pulse of the customer

      -In many ways the open source development has the culture similar to that of

      an Agile enterprise.

      -The principles guiding open source development are similar to Agile principles

      -The session presents views on above as well as how open source development projects employ agile for

      both the community development and for their own licensed version of the software.

    • Liked Venkatraman L
      keyboard_arrow_down

      Scaling from Project > Program > Portfolio - The Agile Transformation and Journey

      Venkatraman L
      Venkatraman L
      schedule 3 years ago
      Sold Out!
      45 mins
      Case Study
      Intermediate

      The case in point is a journey of Agile transformation when the organization was looking to manage releases through shorter iteration cycles. As the journey began, the organization had to leapfrog into 3x growth in terms of both people and business needs due to a round of substantial investor funding.

      The agile transformation started with just 6 teams in the organization and due to the nature of the team structure, the 3-member PMO team did not have the luxury for pilot projects and had to simultaniously roll out at one go across the 6+ component teams.

      In a span of 6 months, the number of teams grew to 12+ and the number of releases more than doubled. Also, 80% of the releases cut across more than 3 teams and the challenge was to keep the process pretty lean. PMO team worked closely with key stakeholders from Product, Engineering, Architecture and Operations to forumate and roll-out a simple 3 step process that aided the teams to deliver releases better than before. Here is when the organization leaped from project to portfolio of releases cutting across 10+ themes.

      Similar to what is quoted in the "Scaled Agile Framework" which the PMO tripped on much later in the process, there were organization wide prioritization done based on the product strategy, infrastructure and technology needs which eventually got translated into multiple programs within the organization, cutting across various teams. A concept of 3-in-a-box (PM, Architect and Engineering Owner) was formulated to bring in the required vigor in to the planning and execution process.The 3 in the box was further extended to Dev +QA + Ops who worked as a team to deliver the various stories across the contributing stacks.

      The challenges across value-driven prioritization from 100+ releases across the portfolio, release planning with engineering and product, the execution framework and scalability in engineering infrastructure commensurate with the agile processes, working with operations teams and all the way till adoption was seamlessly scaled using the initial framework that was set for just 15 releases.

      The presentation details how agile helped and is helping the product and technology teams in delivering better results than before. This would also detail the necessary Agile and operational metrics across the project teams, the program and the portfolio levels that aid the mid and senior management to take informed decisions. As always, this would not cover the IP and actual data of the organization but provide a clear framework to substantiate the process.

    • Liked Abhilash Chandran
      keyboard_arrow_down

      Workshop- Agile user story and Behavior Driven Development (BDD) using Gherkin

      Abhilash Chandran
      Abhilash Chandran
      schedule 3 years ago
      Sold Out!
      90 mins
      Workshop
      Beginner

      In this session I will introduce the audience to the concepts of Gherkin language. Gherkin is a popular language used to encapsulate the requirements in agile world.

      This was successfully implemented in our group across India & USA. I will go through this case study also.

       

    • Liked Pramod Sadalage
      keyboard_arrow_down

      Ten Patterns of Database Refactoring

      Pramod Sadalage
      Pramod Sadalage
      schedule 3 years ago
      Sold Out!
      45 mins
      Talk
      Beginner

      Over the life of an application as requirements change, application usage patterns alter, load and performance changes the need to change database and database architecture is inevitable. There are patterns of these changes such as

      1. 1. Encapsulate Table with View
      2. 2. Migrate method from database
      3. 3. Replace method with views
      4. 4. Introduce Read only table
      5. 5. Split table
      6. 6. Make column non-nullable
      7. 7. Drop column
      8. 8. Add foreign key constaint
      9. 9. Merge columns
      10. 10. Replace columns

      In this talk we will discuss the above database refactoring patterns and different implementation techniques to enable blue, green deployments, allow for legacy applications to work with fast changing database and enable the teams to effectively refactor the database to fulfill the changing needs of the organization.

    • Liked Naveen Indusekhar
      keyboard_arrow_down

      Enticement for Agile Team and Metamorphosis of Managers

      Naveen Indusekhar
      Naveen Indusekhar
      schedule 3 years ago
      Sold Out!
      45 mins
      Workshop
      Beginner

       

      What does productivity mean to the team? What does sponsor want from a team? What happens to Leads and Managers? A ROLE PLAY by JP and Naveen

      The topic assumes that the organization is medium or large sized (about 2K+ employees) and has recently migrated or is in the process of transitioning to Agile methodologies. Further, stakeholders are aligned to the idea and they are wholly in understanding of what and why they want to go (gone) Agile.

      Do you see a scenario in the corridor where a Manager is talking to another Manager – “What happens to us in future? Where do we go? Are we required in this organization? Agile is killing us.”

      Do you see Leads (by designation) saying to his Manager “Hey my career was set to take off – I was to become a Senior Lead, and a Manager in 4 years. Agile has made me an average team member and stalled my growth.”

      What about a team member to another saying “Man, there is no point in increasing the velocity – that becomes a bench mark for us and we need to sprint at that pace for the rest of our lives! I also had lot of time for myself in chunks when other functional group was slogging and I could read a book, attend a training, catch-up with my friends, blah, blah, blah. Let us add substantial buffer in estimates to have a comfortable life and commit on minimal ideal hours. Let us rock as a team!!!!”

      Or a Manager talking to HR “I’m unable to hit the bell curve as an entire team is involved in successful delivery of the project” and HR saying “Sorry, but you are violating global HR policy by not doing so – there ought to be a superior performer and a poor performer.”

      You may hear a team member saying “I was headed to becoming a super DBA and now you are asking me to pick testing tasks, web development task, etc. If I don’t spend 100% of my time in my domain, I will be termed as jack of all trades and master of none. This is not aligning with my career development plans.”

      A VP saying to another “Not sure if Agile has increased our productivity, how do I know it is productive? I understand teams are empowered and self-organizing, but are they self-productive? And what is this fuss about Managers’ not happy with “no-role”. Nothing should change for them.”

       

      A workshop where JP and Naveen play various characters to address these challenges in an Indian office context. Welcome to an enthralling way of presenting the core human challenges in Agile adoption and implementation.

    • Liked Gerry Kirk
      keyboard_arrow_down

      Create an Agile virus in your organization, empower your team, change your life

      Gerry Kirk
      Gerry Kirk
      schedule 3 years ago
      Sold Out!
      90 mins
      Tutorial
      Beginner

      Need buy in from a key manager or executive to adopt Agile? Desiring better team collaboration? Hungry for a saner life at home?
      Try Personal Kanbanwinner of the Shingo prize for Operational Excellence. It's the fastest, simplest way to taste test the goodness of the Lean Agile approach to managing knowledge work. Personal Kanban empowers small teams and individuals, at work and at home.Give that overwhelmed executive instant relief. Build your own system, and soon curious onlookers ask and then create their own. Look out, you've just released an Agile virus in your organization!
      You've also discovered a way for you and your team to get more out of your efforts, to improve communication, and find time for the things that matter most.In this session you'll learn how to create a Personal Kanban system through stories, examples and interactive exercises. Walk away understanding the psychology behind visualizing work and limiting work in progress, inspired and motivated to make a difference at work and home. 

    • Liked Ashish Mahajan
      keyboard_arrow_down

      Water the root , Enjoy the fruit

      Ashish Mahajan
      Ashish Mahajan
      schedule 3 years ago
      Sold Out!
      20 mins
      Talk
      Intermediate

      Yellow or dry leaves of a tree have more to do with its root, rather than its color, which is just an indication of need to water the roots. For a tree to flourish, to bear green leaves, with fruits, it’s the root that needs to be watered

      This is to say, put focus and care into your core every day and then the rest of the things will simply flourish and express itself.

      At times, we are too busy in discussing and analyzing things at a very high level, trying to improve the color of the yellow leaves of the trees, by applying patches, thereby ignoring watering its root.

      We are so obsessed with achieving better results every time, that ,metrics, processes and numbers become the focus of discussion in the organization. We keep on doing the same thing again and again, and expect different results, every time.

      Measure more, measure accurately, implement jazzy-flashy processes with new fashioned terminologies of promises of skyrocketing results, make everyone occupied, and reduce cost at any cost!

      And most of the times, you get the same results, or even worse.

       

      Here are some of the things,I believe, are watering the tree of Product Development that bear the fruits of success.

      • Focus on automated unit tests and refactoring the code every time you see an improvement opportunity, quality will take care of itself.
      • Focus on having open, honest and professional discussions with customers; trusted partnership will take care of itself.
      • Promote culture of failing fast and encourage making mistakes, time to market and innovation will take care of itself.
      • Implement the DNA of Value Flow into the organization, and cost will take care of itself.
      • Focus on respecting and improving skills of the people in your organization, the results will take care of itself
      • Destroy the cubicles , both physically and mentally,  and the waste will have a tough time to find a place.
      • Focus on building great teams; and great products will take care of itself.
    • Liked Cara Turner
      keyboard_arrow_down

      Building Creative Teams: Motivation, Engagement and Retrospectives

      Cara Turner
      Cara Turner
      schedule 3 years ago
      Sold Out!
      90 mins
      Talk
      Advanced

      How do software teams become creative? If you're not a start-up, does creativity even play a role in the business driven world of software development? Idea generation is the basis of all our work - no matter how challenging or mundane. With a scientific approach to implementing change, creativity is the basic tool we have for addressing the challenges of software development.

      This talk explores the elements of engagement and creativity along with the neuroscience of generating ideas. These give us specific insight into how employing different agile retrospective formats over the course of the product development process can extend our usual practices and develop a thinking mind-set comfortable with tackling daily work with a fresh and explorative approach.

    • Liked Johannes Brodwall
      keyboard_arrow_down

      Bare-Knuckle Web Development

      Johannes Brodwall
      Johannes Brodwall
      schedule 3 years ago
      Sold Out!
      45 mins
      Talk
      Intermediate

      Can you go faster with less weight?

      We have all learned the benefit of reusing application servers like JBoss, ORMs like NHibernate or dependency injection frameworks like Spring that "solve all the plumbing code for you", but how real are these benefits really? Most developers struggle using techniques like test-driven development and refactoring effectively in their day to day project. Many developers spend a majority of their day finding out which magic incantations will make your framework solve your requirement.

      Yes, frameworks probably will reduce the size of your code base. But will their reduce the time it takes to develop that code base? And perhaps even more pressingly: How certain are your estimates when you know that a the majority of your work is to find out exactly which few lines of code you need to change by debugging, reading documentation and searching for answers on stack overflow?

      When I was first learning math, my dad told me that I didn't to use a calculator before I could do the math without it. In the same tradition, this talk builds on the premise that you shouldn't use a framework that you can't do without: I will create, live, a realistic web application without generators, without frameworks and without bullshit. Instead, I will use test-driven development to ensure steady progress to a solution with no magic.

    • Johannes Brodwall
      Johannes Brodwall
      Niruka Ruhunage
      Niruka Ruhunage
      schedule 3 years ago
      Sold Out!
      45 mins
      Demonstration
      Beginner

      Can you maintain agile engineering practices with a distributed team?

      Johannes is the Oslo based Chief Scientist for the Sri Lanka based company Exilesoft. In order to promote agile engineering practices, he uses remote pair programming to connect with teams halfway across the world.

      In this talk, we will go through a practical approach for remote pair programming adopted for high-latency situations. We will demonstrate remote pair programming with a live example and we will discuss the advantages and usages of the approach. We will also cover the practical parts of remote pair programming, such as tools and setup.

      After seeing this talk, the audience should be able to remotely pair with members of their distributed team. They will also get a lot of tips on how to use pair programming effectively in both local and remote settings.

    • Liked Anna Obukhova
      keyboard_arrow_down

      The SCRUM and the willpower: how neuroscience can boost your productivity

      Anna Obukhova
      Anna Obukhova
      schedule 3 years ago
      Sold Out!
      45 mins
      Talk
      Intermediate

      Willpower is the force that is between the brain activity (I want to do this or I need to do this) and the action itself (start coding). If there is not enough willpower, people find it difficult to start any activity (especially that involves
      decision making).


      What is the standard approach when you feel tired and find it difficult to concentrate? Take some coffee (but latest research shows that coffee depletes the brain activity, even when body has more energy), take some sweets (but sugar ends quickly and gives even more exhaustion to the body)? These widely used strategies generally do not work, and in long-term even add harm to the body and brain.


      The willpower is not endless (so-called muscle theory of willpower), it can be saved, it can be trained, there are approaches how to keep the willpower level high. To keep the willpower (and thus, productivity) on the high level, people should know and use different approaches that lay in the field on the social and cognitive science.


      There are a lot of evidences that SCRUM improves the developer’s productivity in terms of speed of development, code quality, and accuracy of design. Unfortunately mainly all recommendations from SCRUM coaches look like “believe me, if you do this, you will have better velocity”. Yes, it works. But why does it work?


      Sometimes SCRUM does not give such great results even when main elements are in place. The question “Why” and “What makes the difference” is here again.


      I will describe the model of relationship between the willpower related brain metabolism on very low level (specific amino acid cycle) and the SCRUM practices. I can prove that SCRUM addresses the productivity of the people’s brain using 3 different flows simultaneously. There are several tips that make these productivity flows working or not. You can make Agile productive, you can have non-productive Agile. I will show you where the difference is.


      Overall there are 10 productivity tips that can be put into 3 flows.


      As the outcome of this session, Agile coaches, and all people who can change the process (in fact that is any team member) will review their SCRUM: does the way they have it improve the productivity or they are losing all the power? The changes are cheap, the outcome can be huge.

    • Liked Shrawan Gaur
      keyboard_arrow_down

      Learn from Mistakes, Retain Your Strong Holds: Sprint Retro: Do As WE Do at John Deere

      Shrawan Gaur
      Shrawan Gaur
      schedule 3 years ago
      Sold Out!
      45 mins
      Talk
      Beginner

      As the 12th Agile Principle states : "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.", it is quite easy to understand the importance of continuous evolvement which involves retaining learning and corrective actions.

      John Deere has started its Agile journey in year 2010 and since then has gone through various phases of transformation. Scrum teams has learnt alot and are continuously learning. Retrospection is one of very important scrum ceremony which paves path for team to advance in right direction.

      Here, I will demonstrate some retro techinques and its applications according to sprint work.