How Scrum Master can help the team in quitting 'SMOKING'

We all know ‘Smoking is injurious to health’ but in this session we are going to discuss about ‘How SMOKING is injurious to teams’ health’ and how Scrum Master can help the team in quitting 'SMOKING'.

  • Are you satisfied with mediocre or above par performance? No?
  • Do you need the best out of everyone? Yes?
  • Have you ever realized about the bad practices that crept in. Yes or No?

We have brainstormed with more than 30 Scrum teams and collated the SMOKING patterns. So, in this session we are going to discuss in detail about tried and tested recommendations to trash those SMOKING patterns with which we can increase efficiency and also break the monotony in Scrum events.

 
 

Outline/Structure of the Talk

1) Overview of SMOKING patterns (Brainstormed with 30+ Scrum teams)

2) Mapping patterns to target areas

3) Recommendations to thrash out each pattern (tried and tested)

4) Conclusion

Learning Outcome

1) SMOKING patterns & target area mapping

2) Tried and tested recommendations to increase team's efficiency

3) Breaking monotony in Scrum events

4) Theme based reviews and fun filled team bonding activities

5) Retrospectives techniques and themes

Target Audience

Scrum Masters, Leadership, everyone involved in agile transformation or want to know more about it.

Prerequisites for Attendees

Basic knowledge of Scrum framework

schedule Submitted 4 months ago

Public Feedback

comment Suggest improvements to the Speaker

  • Liked Satya Jyoti Yellapantula
    keyboard_arrow_down

    Satya Jyoti Yellapantula - Product Backlog Refinement - The UnSung "Hero"

    Satya Jyoti Yellapantula
    Satya Jyoti Yellapantula
    Scrum Master
    Pegasystems
    schedule 5 months ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    When we speak of Scrum framework, the 3-3-5 structure is imbibed in our memories. The 3 roles, 3 Artifacts and 5 events are known to all. When we talk of processes, learnings, improvements, most of the teams confine themselves within the limits of 3-3-5. How many of us realize Product Backlog Refinement lays the foundation of the Release/Sprint planning. Do teams really give the right importance to PBR, or do they feel it distracts them from the their current sprint work? How can PBR be more effective and help teams plan better, be more predictable, help in being more productive, and encourage the teams to take calculated risks when needed - these are few of the things we would discuss during the session.

    We conducted with more than 40+ Scrum Masters across the globe in one of the organizations I was associated with, to collect the challenges w.r.t PBR. During this session, we will discuss those practical challenges, and tried and tested recommendations.