Agile India 2005 (Mumbai)

Keynote: Reducing Business Risk through Agile Development
This presentation describes what Agile & Iterative methods are and the impact they have on reducing the Risks associated with software development. This is presented in contrast to the traditional approach of a single pass through the development cycle and using extensive documentation to reduce risk.

Iterative approaches are not in themselves new - what is new is that they have been formalised into several rigorous methodologies. According to the Standish groups CHAOS report Agile methods are also gaining ground in the industry; it is my belief that in 5 to 10 years time everyone will be developing software this way.

Fred Tingey

Keynote: An Introduction to distributed Agile
Software development is a complex process. Global organizations consider geographically distributed development as an effective way to develop and deliver software, reaping benefits of cost savings, round-the-clock development, scalability etc. Agile methods like XP, SCRUM etc help development teams to deliver business value to the customer in an efficient way by introducing light weight processes. Early projects that followed agile methods were small, with relatively smaller teams. Many of the early adopters believed that agile works effectively with only projects with collocated small teams. This assumption was challenged by success of few projects in the last couple of years, successfully scaling agile to large teams. ìDistributed Agile Developmentî is the new kid on the block. In this presentation, letís try to understand the nature, process and challenges of distributed agile development.

Bapiraju Nandury

Agile - Distributed: Connecting the agile mass
eXtreme Programming exploits the benefits of tight collaboration in an environment where all stakeholders sit within talking distance of one another, and work in pairs. But in real industry scenario it is difficult to get every stakeholder around the proverbial round table each day. Core concepts of extreme programming such as planning games and pair programming are generally hard to achieve over a distributed environment where the stakeholders are distributed over the globe or at least are not in physical proximity. This talk deals with Distributed XP planning games and our experiences while building collaborative tools for Distributed XP.

Bhaskar Mitra and Annapurna PS
Agile Development with Ruby
Ruby is a powerful, pure OO programming language. It's like a mix of the best things from Perl and Python. A lot of the features of the language facilitate agile development. This talk will focus on some of those aspects -- like testability, unit testing, etc. -- that facilitate such development..

Premshree Pillai
Lightweight record and play web testing tool - Sahi
Sahi is a simple, easy to use tool for record and playback of web based applications.
Apart from being a QA tool, Sahi allows developers to actively participate in functional testing. It helps in reproduction of bugs and in automating repetitive web sequences.

The presentation aims to showcase the capabilities of Sahi and the role that Sahi can play in a project life cycle.
Sahi was developed due to a need felt for easy reproduction of bugs. It developed into a full fledged web testing tool with feedback from QAs.

V Narayan Raman
Hands-on testing with domain-language acceptance tests
Acceptance testing: what it's all about, some better practices, why it will bring joy to your (and your client's) life , and also a demo or two using FIT.

Conan Dalton and Dhaval Dalal
Migration to Agile
A "how to" session on going agile. This session will also discuss different approaches, the necessary organizational and customer issues involved.

Anand Joglekar

Overview of Agile and Managing Iterations in XP
A gentle introduction to Agile. An overview of different activities that take place during an Iteration. The objective of the talk is to introduce the core values and principles of Agile. We will also discuss how some of these values map to practices in XP.

Naresh Jain

Agile Product Development
Product developers face an increasingly turbulent world. Market requirements change constantly and available technologies evolve rapidly. If a company lacks agility in its product development, it cannot respond to a changing environment, nor get the right products to market fast. Agility is the ability to change direction without losing momentum.
  • It requires quick decision making during development, adapting plans to emerging information, and obtaining fast feedback from customers
  • Product architectures must be robust enough to absorb change
  • Development processes cannot carry excess baggage
This presentation uses 2 case studies to demonstrate how this can be achieved by leveraging key features/tools from methodologies like, DSDM and RUP.

Taruni Tamhane

Sausage Machine: Agile tuned for offshore co-development
Overview of Sausage Machine, an agile methodology tuned for large offshore co-development projects. Objective is to present a case study, elaborating how a domain centric project like Securities Services for BNP Paribas benefited from the agile offshore based co-development model. Also to provide an executive summery on "Why Agile and for Who".

Satish Ranade and Jitendra Joshi

TDD Workshop
Test Driven Development Hands on Session. We'll be using Java and Eclipse to run the workshop.
Prerequisite: The participants need to have a good exposure to object oriented programming with Java

Naresh Jain and Anand Joglekar

Developer Testing - An introduction
XP popularized developer testing through the concept of Test driven development. This topic covers basic tenets of TDD and Associated Tools and Techniques. It will also cover the tester's role in an XP Project and "Incremental Testing - an insight in to the process followed by Subex development teams."

Ajmal Y

XP in Product Support Environments: An experience report
This will provide an insight in to how Subex supports its installations after deploymnent. It would cover the aspects of how the product/ Features are developed in Roadmap team, Delivered by the Customer Delivery team with customizations as needed and finally supported by the Support team. The guiding factor will be how XP's processes and Principles helped.

Prashant Shah

Agile way of Implementing CMMI
CMMI has a set of Specific and Generic Practices that leads to achieving some GOAL. Agile is a methodology, that can be useful in implementing the CMMI Specific Practices(SP- to a moderate extent) and Generic Practices(GP- to a high extent).
My Presentation shall focus on the efficiency and effectiveness impact of using the Agile for implementing cmmi. Specifically the GPs can be implemented in a much more faster with lesser operational overheads saving adequate time for the project teams.

Hitesh Sanghavi

Introduction to Mock Objects
We will present the basic ideas behind testing with mock objects; attendees will then have an opportunity to put these ideas into practice.

Madhusudhan Rao and Conan Dalton

Lean Software Development - Balancing Discipline and Agility
Software development is a critical industry in the world we live in today. The production system for software is governed by the discipline of software engineering. Software engineering has gone through the growing pains infancy, adolescence and is now begining to show signs of maturity that comes with an established discipline.

The evolution of software engineering can be categorized into three major paradigms:
craft production,
mass production and
lean production.

The first two decades of software development fall primarily in the craft production paradigm, in which the software developed was a unique product that was created by specialist developers, who in most cases were also the end users of the produced software. The learning associated with the development process resided primarily in the developer, and was shared within a small community of skilled artisans.

The subsequent three decades saw dramatic reductions in computation costs, and the resultant commoditization of software led to the adoption of the mass production paradigm. This period saw the emergence of compilers, integrated development environments, fourth generation programming languages, and most importantly discplined software development approaches. The extant process models and maturity assessment approaches have more often than not resulted in heavyweight approaches that are characterized by rigid processes and document centricity.

The lean production paradigm provides a means of getting the best of both the mass and the craft production approaches. Lean production has its roots in Japanese automotive manufacturing, and is often credited for the current dominance of the Japanses automotive industry. Lean as an operating philosophy is beginning to permeate mainstream software development; however, successful institutionalization of these principles and practices requires both a purpose driving the adoption of these principles and practices, as well as a significant change in the culture of the organization.

This talk addresses lean software development from the mission-critical embedded systems perspective through the use of case studies drawn from extant literature and ongoing research studies at the Lean Aerospace Initiative. An overarching framework for lean software development is presented, and two case studies covering different phases of the software development lifecycle are use to illustrate aspects of the framework. The framework is based on four key pillars: value based project management, eliminating waste through model-based system development, achieving perfection through integrated verification and validation, and continuous improvement through knowledge management. Each of the foundational concepts is discussed in depth, and the principles and practices associated with them are presented. Case A focuses on the requirements generation phase in the development of an embedded radar system. The project was staffed with a small co-located team that had several members working on multiple projects at the same time. The original project plan had a large amount of requirement reuse planned into it, however that vision was not actualized, and the plan was revised significantly at different points in the project lifecycle. The case highlights the challenges associated with requirements reuse, as well as the limitations of the earned value approach to project management. Case B is drawn from the literature, and focuses on the code generation and verification phases of an embedded control system. The project involved globally distributed teams that were developing a product for use in multiple geographic locations. The impact of external stakeholders on project success is discussed both from the value and the knowledge management perspectives. The ability to reuse software architectures and thereby minimize waste was one of key reasons for the successful completion of the project. While the project serves to highlight a lot of the successful aspects of using lean software development, the gaps in the adoption of lean provide interesting points of learning.

Jayakanth Srinivasan

Lean Thinking Workshop
This would be a workshop for 15-20 ppl max for maybe around 3 hours. Plan to talk abt the various Lean Principles & try and arrive at some concensual practices. Highly interactive & would want ppl of cross cutting concerns.

Mujiruddin Shaikh

XP Planning Game
The XP Planning Game is a playful way to familiarize the players with some of the more difficult concepts of the planning in XP, like velocity, story estimation, yesterdayís weather and the cycle of life. Anyone can participate. The goal is to make development and business people work together, they both play both roles. Itís especially useful when a company starts adopting XP.

A few ThoughtWorkers
  Sardar patel College of Engg [SPCE],

2005-2017 Copyright © Agile Software Community of India
Website designed and hosted by Agile FAQs