Pune

Agile Software Development and the breed of Agile Methodologies (XP, SCRUM, DSDM, etc.) have gained popularity since 2001. Primarily founded as methodologies for software projects executed at a single location, Agile Methodologies have started showing promising results in multi-site projects too with many adopters and practitioners across the globe. For more than two decades, offshore delivery models have been successful in case of application maintenance and enhancement projects. In case of development projects iterative lifecycle approaches have gained familiarity and acceptability compared to the classical waterfall approach in delivering results and ensuring customer satisfaction. Agile Software Development focuses on early delivery of working software to measure the progress of projects and hence to mitigate risks. It creates an environment that responds to changes by means of being flexible and nimble.

Agile Methodology brings in high level of customer delight, and associate delight. It is adaptive, focused on delivering in very small sprints, and welcoming change. When the development team needs to responds to change in small sprints, traditional approaches of development, testing, deployment need a make-over. We, a part of High Performing Agile Team have been practicing Agile development methodology (specifically Scrum) for over four years now. I would be very happy to share with you the engineering practices that we focused on to boost and sustain this methodology.

Drawing primarily from the experience of a large in-house software development project, this presentation will illustrate how to incrementally evolve architecture and design for a system across iterations. One of the principles we adhered to was: use before reuse. Some of the key practices and activities in architecture and design evolution that this presentation will highlight are: * identification of desired architecture qualities of a system, cross-cutting requirements * no upfront architecture * implementing one story, sowing the seeds of architecture through this story * implementing more stories and refactoring existing ones to create an application framework * verifying the framework by implementing a couple of more stories through framework extension * gradually introducing more architectural features and patterns in the system through progressive refactoring.

This session endeavors to answer soem of the tough question faced by Agile teams while dealing with testing issues

Through "Panchayat Raj" , Mahatma Gandhi introduced the concept of empowerment of the people. This conference discusses the issue in detail to discover its relevance to Agile methodologies. It will further explain to embrace the "Truth is God" doctrine of the Mahatma.

What do your agile teams do for estimating and planning their work? Does it work for you? As a manager have you come across bloated estimates? As a team did you run into a stressful sprint because of bad planning? Estimation and Planning is one of the important facet of an Agile project. And thus the need to do it correctly increases. This talk would focus on nuances of Agile estimation and planning.

"Our project failed. Agile process and practices to be blamed". Agile is not a magic stick to save a failing project and bring immediate results. It lets you uncover better ways of developing software by doing it and helping others do it. As with all development methods, the skill and experience of users determine the degree of success and/or abuse of such activity. Sometimes, we obtain the agility by making up our own variation of this methodology. In this case, failure of this project should largely be incumbent upon us for deciding to sacrifice the practices we choose to ignore and the new ones we add. Some are Agile just cherry picking a couple of practices here and there and picking the principles they like. This talk would help you uncover some Agile "bad smells", if you have any.

This session would talk about the challenges that HR and OD associates face when dealing with organization transitioning to Agile

As organizations grow in Agile, it is important for them to identify risks at right time and prepare a risk plan. This session intends to investigate what kind of risk management works with Agile Projects.