• Liked Cara Turner
    keyboard_arrow_down

    Building Creative Teams: Motivation, Engagement and Retrospectives

    Cara Turner
    Cara Turner
    schedule 3 years ago
    Sold Out!
    90 mins
    Talk
    Advanced

    How do software teams become creative? If you're not a start-up, does creativity even play a role in the business driven world of software development? Idea generation is the basis of all our work - no matter how challenging or mundane. With a scientific approach to implementing change, creativity is the basic tool we have for addressing the challenges of software development.

    This talk explores the elements of engagement and creativity along with the neuroscience of generating ideas. These give us specific insight into how employing different agile retrospective formats over the course of the product development process can extend our usual practices and develop a thinking mind-set comfortable with tackling daily work with a fresh and explorative approach.

  • Liked Prashant Kutade
    keyboard_arrow_down

    How should be a Sprint Retrospective ?

    Prashant Kutade
    Prashant Kutade
    schedule 3 years ago
    Sold Out!
    45 mins
    Experience Report
    Beginner

    Sprint Retrospective

    Sprint Retrospective is a meeting that happens at the end of each Sprint that usually occurs after the Sprint Review. This practice involves the Scrum Master and the team members to discuss what went right and what went wrong in the practices adopted during the Sprint. Thus, it allows modify some practices to maximize the positive and avoid negative points. This meeting provides a moment for greater interaction among the members and allows the team to self evaluate and propose the necessary changes, thereby strengthening the sense of teamwork.

    Like the other meetings in Agile, the Sprint Retrospective requires many adjustments. In the experience reported in one of the Sprint Retrospective in John Deere TCI(Pune, 2013), someproblems that were faced related with the presence of all members at the meeting and related with the tool support. The first trouble was to find a time when everyone could attend, since this meeting was initially scheduled one day after the Sprint Review. The solution was to hold the meeting after the Sprint Review and limit the maximum duration for two hours, so this is not tiring. The second difficulty is the need for multiple tools for holding the meeting, the techniques to be followed to drive the meeting and raise the positive and negative suggestions, as well as project management tool like Rally for presenting data from the project’s progress, such as the Product Burndown.

    Despite the importance of the presence of all team members in the Scrum meetings, in some situations, for example, a project with many distributed teams, a remote meeting with all members becomes impractical which should be avoided. Thus, for those situations, this proposed approach suggested to do a Sprint Retrospective by team, and saving the information collected at each meeting. This information collected should be shared to all members, allowing them to analyze the improvements suggested by other teams.

    One last modification is to hold a meeting among each Scrum Master, similar with Scrum of Scrums, to discuss the Sprint Retrospective done by each team, and with that, it is possible to align the dependency among them. This meeting may occur the day after the Sprint Retrospective of the teams, and it is crucial that each Scrum Master considers the points raised by other teams before the meeting between them, in order to optimize its duration.

  • Liked Cara Turner
    keyboard_arrow_down

    Building Creative Teams: Motivation, Engagement and Retrospectives

    Cara Turner
    Cara Turner
    schedule 3 years ago
    Sold Out!
    90 mins
    Talk
    Advanced

    How do software teams become creative? If you're not a start-up, does creativity even play a role in the business driven world of software development? Idea generation is the basis of all our work - no matter how challenging or mundane. With a scientific approach to implementing change, creativity is the basic tool we have for addressing the challenges of software development.

    This talk explores the elements of engagement and creativity along with the neuroscience of generating ideas. These give us specific insight into how employing different agile retrospective formats over the course of the product development process can extend our usual practices and develop a thinking mind-set comfortable with tackling daily work with a fresh and explorative approach.

  • Liked Naveen Nanjundappa
    keyboard_arrow_down

    4 Quadrant: Focus Area based Team Retrospective.

    Naveen Nanjundappa
    Naveen Nanjundappa
    schedule 3 years ago
    Sold Out!
    45 mins
    Tutorial
    Intermediate

    The Regular and most popular retrospectives end with action items on the specific person in the team. 

    while the retrospective's primary goal is to enable the team to reflect onto themself and tune their behaviour for becoming more effective. In order to provide such a platform I practiced and coached 4 quadrant, focus area based retrospectives.

    In which the team focus on the over all improvement and not just an action item. this is truely the team's behavioural change and their actions to become more effective. 

    Based on many successful coaching experience, i would like to present this activity based session.

    Summary:

    The team identify the focus areas for improvements, then identifies the small delta improvement in that focus area that is measurable. then they decide on if they need external coaching or internally the team can achieve the goal.

     

    Focus areas | Coaching/Training

    _________________________

    Measurement | Self / team 

  • Prajakta Thakur
    Prajakta Thakur
    schedule 3 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

     Prioritization, Accountability, Inspect-and-adapt, Rhythm, Feedback, Collaboration, Self-Organization, Focus form the key principles of Scrum Methodology. And it is the Scrum Ceremonies which help ensure that this essence of Scrum remains intact through following of the above principles. Scrum Ceremonies give project teams a wholistic framework to ensure smooth Scrum implementation and effective project delivery.

    The key Scrum Ceremonies are as listed below

    • Release Planning & Sprint Planning ( consisting of Backlog creations and grooming and Estimation )
    • Daily Scrum
    • Sprint Review
    • Sprint Retrospective

    The scope of this presentation is to share:

    • Deeper understanding of objectives behind each ceremony
    • Benefits of each ceremony
    • Challenges and Common Mistakes related to each ceremony
    • Effective techniques of conducting the ceremony to get best advantage out of it