• Português
  • 简体中文
  • 繁體中文
  • Deutsch
  • English
  • Español
  • Français
  • 日本語
  • Latviešu
  • Lietuvių
  • Русский

Submitted Conference Content

Full name

Yashasree Barve

Job Senior Consultant
email yashasree [dot] barve [at] gmail [dot] com
Phone number 9820-469-460
Company Tata Consultancy Services
City (Country) Mumbai
Time 45'
Type of Conference Conference > 100 attendees
Level Everybody

Nothing Official umm... Functional about it - An Agile Developer's View of the Product Backlog


Yashasree Barve has been working as a technologist in Tata Consultancy Services since last 14 years. She has an extensive experience in delivering solutions for Enterprises. She has executed and worked on several projects in the role of a developer, designer and architect across multiple domains such as Insurance, Retail, and Hi Tech using various technologies such as Java, Java 2 Platform Enterprise Edition (J2EE), Ruby on Rails and such. She is also a core member of the Agile community in TCS evangelizing Agile within TCS by bringing the community together and organizing internal conferences. She has also spoken on Engineering Practices in Agile Tour 2010 Pune, Agile Architect in Agile Tour 2011 Pune, and also in Agile India 2012 in 2 separate sessions on Agile Architect, and DevOps.


Ever since big up-front architecture and design died its own death in the agile world, non-functional requirements have been orphaned. The product backlog shaped up by the sponsors and product owners focuses on what the product should do. The agile team gets busy churning out the functional stories. In such a scenario, the 'alities' i.e. the qualities that describe the 'how' part of the features often get missed out, ignored or de-prioritized. These are not official or functional requirements, but those still are a very important view of the product, and in turn the backlog. I, an Agile Developer and Architect would like to take a dig at the various non-functional requirements and discuss where they belong. I would like to discuss and debate the new home for such requirements, whether it is the done list, acceptance criteria or a separate technical story in itself! I would also like to elaborate how and when to discover these requirements that are not explicitly expressed by the sponsors. Finally I would like to leave this thought with the audience to think through the non-functional requirements hand in hand with the features to deliver a complete quality product.


None to be specific; Knowledge of Agile methodology, basics of scrum, product backlog would be helpful.

Benefits for the attendees

1) Learn to appreciate the importance of non-functional requirements for a product 2) Understand how to incorporate non-functional requirements while a product backlog is shaped.

Go to the submission page!