This is a workshop to build product while practicing impact mapping, feature writing, specification by examples and applying test first approach. Workshop will practices that will help in translating product vision to product increment and living documents. Facilitator will demonstrate how to convert specifications in code by using test first approach.​​ Facilitator will help in crafting product vision, coming up with product features, how to write examples for features and use examples to write production code. Session will demonstrate how to convert specification into product increment, living documents and build test automation.

We often see team create tasks for product backlog items during sprint planning but those tasks are skill-based task like coding, testing, documentations etc. Is it a right way to do? What all can go wrong if we keep creating tasks like this?

• Team may not focus on delivering end-to-end feature and every members are just concern about their respective tasks but what about whole feature?
• Team members may not be interested in hearing other’s work so Daily Scrum may become boring for team and team may not be interested in each other work.
• Sprint planning may get completed quickly without going in details. This may lead to poor planning for iteration.
• Team may not discuss about design and architecture during planning and that will lead to duplicate code to avoid dependencies on each other during execution.

I will share my learning on how to plan sprint to avoid above issues. 

Behavior Driven Development (BDD) is a agile practice that helps in overcoming collaboration challenges between Product Management Team and Software Develop Team. Unfortunately team usages BDD tools more for test automation than addressing collaboration challenges. This talk with demo is to understand what is BDD and how to practice to bring more transparency in software development.

Talk will also help to understand how to build a infra to bring visibility about what feature team is building on day to day basis with help of CI tools.

Well BDD is a collaboration practice but can it be useful technique to split product feature?
Usual to address spitting complex product feature to ensure continuous delivery of working software?
How splitting product feature can be a fun if scrum team collaborate often?
How bring transparency while spitting product feature through BDD practice?

Large-Scale Scrum (LeSS) is a framework for scaling agile development to multiple teams. LeSS builds on top of the Scrum principles such as empiricism, cross-functional self-managing teams and provides a framework for applying that at scale. It provides simple basic rules and guidelines on how to adopt Scrum in large product development.

In this tutorial, we focus on LeSS framework and see how you can scale Agile development to big organizations. We will start by looking at basic assumptions behind scaling and what different approaches there. Then we learn how LeSS deals with scaling in big groups and finally how LeSS can be adopted for existing organizations and what changes it bring in.

Will share LeSS (Large-Scale Scrum) implementation journey and challenges encountered during transformation from component team to customer-centric feature team. Journey that covers defining product, building feature team through changing organization design and descaling organization through lean thinking. Talks will cover challenges in adoption and difficulties in retaining agile values beyond single team. Will also talk about key engineering practices that helped in resolving integration challenges and roles of management after adoption.