• Liked Vishal Prasad
    keyboard_arrow_down

    Learning from Anemic Reviews - The Monger Project

    Vishal Prasad
    Vishal Prasad
    schedule 1 year ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    Consider an agile utopia executing scrum for software development. How would you feel if your biggest strength of receiving early feedback from your end-users turns out to be your Achilles heel? Recently I faced this dilemma where my end-users unfortunately were a group of introvert individuals. This led to Monger project’s MVP almost declared as a failure since it did not fulfill the end-user’s requirements. 

    Many a times, projects transform their delivery mechanism from traditional models to agile with a myth that agile is a recipe for success. In reality many projects fail since agile is not well understood by the teams. A few times (like in this case) the agile process falters not due to incorrect implementation but due to incorrect participants responsible to execute a part of the process.

    Experience with me what happens when your end-users falter your feedback loop just because of the nature of individuals. If you’ve ever been a part of a group (or may be in the future) where your end-users are introverts, learn from this experience report how we overcame this problem on the Monger project by strengthening our anemic reviews. At the same time, if you as a participant have been there and done that, I would love to hear about it. 

  • Liked Ashish Pathak
    keyboard_arrow_down

    Why Businesses should not ignore Technical Debt - A Case Study

    Ashish Pathak
    Ashish Pathak
    schedule 1 year ago
    Sold Out!
    45 mins
    Case Study
    Advanced

    Cases like the Toyota’s Unintended Acceleration case of 2007 highlight the impact of bad engineering practices on the quality of the product. This eventually impacts the business and the organization’s reputation as well. There have been several such instances in recent history, yet business stakeholders get tempted to compromise on the sound engineering practices for having quick gains. This approach, most of the times, is due to lack of understanding of these practices and under-estimating their negative impact in the long run. The aim of this paper is to highlight this impact and present a strong case for paying enough focus on concept like technical debt to reduce and control it in software development context.

  • Liked Sridharan Vembu
    keyboard_arrow_down

    Over-selling the "Enterprise Agile Frameworks and Certifications"

    Sridharan Vembu
    Sridharan Vembu
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Intermediate
    Agile is only for smaller projects and/or startup organisations - Not Anymore. Taking my own and my organisation's experience, Agile is a proven methodology that is well suited for delivering complex, distributed, multi-year enterprise programs, for many years now.
     
    While this is really a great thing for agile enthusiasts and practitioners, it’s a bit of worrying sign for me the increased recognition and popularity the ‘Agile Certifications’ and ‘Agile Frameworks’ are receiving among individuals and organisations who would like to adopt Agile to stay relevant in current world.
     
    I would like to share my views on the adoption of these frameworks and certifications, why I feel they are not-so-agile and how am I and my organisation are solving similar problems without the need for any of these frameworks and certifications.
     
    I am planning to walk through the complete life cycle of the most recent program that I’m part of (from Inception to Initiation to on-going Execution to Post-Production Support) and bring out the relevant agile principles that we adopted, context based customizations we did and the best practices that we have come up with.
    • For instance, one should know the clear difference between hygienic practices vs context based practices - the first ones are not to be compromised at any cost, whereas the latter ones are to be applied based on the need, not because some framework prescribes it.
    The typical life cycle stages that we follow in any program / project delivery is normally: Discovery - Inception - Initiation - Execution - Transition, whereas the actual set of practices within any of these stages and how they are being implemented could be very different from project to project, team to team. 
    • For example, in the Execution Phase, doing pair programming and following TDD are hygienic practices for us. Having said that, it’s perfectly okay for a pair to split and work on a specific task on a case-to-case basis (we call this Pragmatic Programming) and the pair decides when and how long they would split and when to re-join.
    To give an idea on the complexity, enterprise and distributed nature of the program, some key data points:
    • Started almost 3 years ago, on-going
    • 10 quarterly planning workshops done so far
    • 10+ teams, 7 timezones
    • peak program size: 250+
    • peak team size from my org.: 50+
    • total no of systems: 10+
    • geographical spread: plan: 100 countries, 132 locales launched so far: 53 countries, 56 locales
    • 140 page-views / sec
    • Av. response time: 1.3s
    • Handling 100+K products in the catalog, 15+ K pages , 300+ K responsive images
    • Blue-Green production deployment (zero downtime over 1.5 years)
    • 3 weeks cycle of production releases
  • Liked Uday Kumar KV
    keyboard_arrow_down

    DevOps Primer

    Uday Kumar KV
    Uday Kumar KV
    schedule 1 year ago
    Sold Out!
    60 mins
    Others
    Intermediate

    Agile Principles are more Software Development focused. There is need for Organizations to look for Software Development Agility nothing but DevOps. In order to achieve Organization operational efficiency the complete Organization needs to be DevOps complaint.

    Take away for orgnizations on What is that they need to do?

    At present, DevOps has got several buzz words associated with it. Standards in terminology by bringing in concepts such that everybody speaks same language.

  • Liked AnkitTandon
    keyboard_arrow_down

    Visualization – The unsung hero of your Agile journey

    AnkitTandon
    AnkitTandon
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Beginner

    In our Agile journey, while it is great we focus on mastering various Agile practices, understanding Agile principles and internalizing Agile values at times small yet an  important aspect like Visualization does not get the required attention.   

    My presentation will be about various Visualization examples for teams to improve collaboration and communication.  It is going to be an interactive session stuffed with a lot of discussions around the various practical Visualization techniques an Agile coach / Scrum Master / Agile team member should have in his toolbox.

    These techniques enable communication and aid knowledge sharing by making information visible to the team members. There is no prescription but the suggestions that one can experiment, evaluate and evolve as per team's need.

     

Sorry, no proposals found under this section.