Retrospective is the heart of scrum and agile world. We need to ensure this heart is well connected to other parts and functioning well. Getting the right amount of inputs and making sure with the right outcomes. This workshop will be an eye opener to understand anti patterns of retrospective. It will be more of a hands-on exercise for all the attendees based on our experiments which we have conducted got benefited. Will help to practice an effective retrospective which enables the team to seize opportunities to improve. Retrospectives can become monotonous and boring over time and so they become ineffective. We need to bring something new, fun, or exciting to the retrospective to make it lively.

This workshop will lead a way as a food for thought for scrum practitioners. Why it is important to ensure that each team member is comfortable participating and sharing thoughts and ideas requires that the Retrospective be conducted with an atmosphere of respect, honesty and positivity. Retro facilitator who contributes structure and process to a Retrospective to help the Scrum Team identify and bring about an outcome that is consistent with the Team’s objectives.

Will also cover the aspect as how a Retrospective lacking a Facilitator will suffer problems similar to a team-based sporting event lacking a referee. Retrospective should be facilitated in a healthy and fun way, team level engagement should be taken on priority. Retro outcome apart from the action items team should look forward to participate and leave a mark.

Successful retrospection responsibility who ensure, is it team or scrum master or both? Together teams need to think outside the box when approaching Sprint Retrospectives and appreciate that these short gatherings need not to be done only by using the usual techniques or methods. Instead they can bring their own ingenuity, knowledge, and experiences to the table to create games or to start meaningful discussions that the team drives.

Behaviour Driven Development is a collaboration practice exists under agile umberalla for a while. It is a way of writing requirements which can be automatically turned into a code. Originated from Domain Driven Design [Business & Software speaks same language]. BDD that uses conversations around concrete examples and requirements, expressed in an executable form, to deliver higher value software more effectively. It is an extension of popular TDD but using simpler methods While every BDD team is different, and mature teams adapt and refine their process to suit their specific needs and context, the steps outlined here give an idea of the general approach followed by many of these teams. Matured way of eliminating waste by minimizing handshakes. Behavior-Driven Development is a great way to get your team working well on many levels, not just the obvious in terms of backlog refinement but also in pushing it to communicate regularly.

A typical mature BDD process is made up of a cycle five key activities:

Discover

Define

Formalise

Automate

Deliver