Bengaluru

Test Driven Development has been around for some time already. Writing unit tests is one essential step of TDD. Writing unit tests is also essential before we can make safe changes on legacy code. However, like codes, there are smelly tests around in this industry. In this session, we will go thru some interesting smelly test codes, and share stories behind these smelly test codes. Through these stories, we hope that not only participants can learn what kind of test code is smelly, but also acquiring the correct values and attitude to write good test code, as well as, understand certain organisational factors that would drive people writing smelly test codes.

Scrum and Lean are 2 different methodologies. Evolved at different times, different locations, under different circumstances to solve different problems. Yet they have quite some similarities in principles and are complimentary in processes. The presentation aims to explain how to blend them together to create a more powerful methodology for software development. Also talk about the challenges in the way and some tools to be used.

Introducing change within an organization has many challenges. One of the most critical one being able to support people going through this change with the right process, tools, techniques and environment. This session would aim to examine some of the challenges faced during this journey of change, specifically with regards the people aspects. It would talk about the various facets that an organization and team would need to address to be able to provide the right environment for their people to adopt the ‘New’.

I've delivered this talk at Agile 2010 Orlando this year, and my slides are in this proposal too. If you need it, I can share the feedback I received for the session, which was all mostly superlative stuff. Learning outcomes

• understand the importance of giving and receiving feedback on an Agile team
• understand who is responsible for generating feedback
• be aware of the different styles of giving and receiving feedback
• be able to use simple guidelines for delivering and receiving effective feedback

Introduction

User Stories are the primary development artifact in XP / Agile programming methodology. It serves as an alternative for the traditional, long and confusing Software Requirements Specification (SRS). User Stories are short and precise to a limited context. It focuses on Who, What and Why of a feature. In the session, I will be introducing User stories and effective ways to write them. I will also talk about various methods to gather User stories and the scenarios in which a particular method should be used. The session also includes a User Stories writing workshop where the participants will be writing User stories. See my article "Writing User Stories Effectively" for more information on the topic.

Abstract: Many organizations today are looking to adopt agile at an enterprise level. This presentation showcases an experience of how agile was made as one of the mainstream process at Wipro. Wipro is a leading IT Services firm which has executed Agile and Lean projects in several domains – telecom, healthcare, finance, insurance, embedded, media etc.

Typical IT service industry will have co-existence of all kind of projects starting from sustenance, to tech support, production support and product development. In such environment, always there is co-existence of different methodologies. There is a tendency to see Agile projects as alien projects, and many myths around agile projects make the team peculiar . This paper is to discuss about how to establish in the organization being with an Agile project and get considered for Organization leadership.

http://www.slideshare.net/ajaydanait/agile-developers-create-their-own-identity-4786316

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.