• Liked Vivek Ganesan
    keyboard_arrow_down

    Developer 2.0 - Redefine the Role of Developer to achieve Success for All

    Vivek Ganesan
    Vivek Ganesan
    schedule 1 year ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    Gone are the days where developer was responsible for just writing clean code. Traditional definition of developer affects the individual developers more than it affects the organization. The developer tends to concentrate on getting better at just the area of coding and ends up not learning the nuances of building a successful product. As a Developer 2.0, the developer performs all of the following roles. 

    1. Coder 

    2. Devil's advocate 

    3. Code Reviewer 

    A developer can work in multiple stories but cannot do more than one of the above tasks for the same story. For example, the same person cannot be both the coder and Devil's advocate. A team at Gainsight worked with this improved definition of developers and saw higher product velocity, better awareness about product and increased responsiveness to issues. This session will take the audience through the improved definition of the role of developer and present some thought-provoking questions to the audience to make them realize that the traditional definition of role of developer is just not enough.

  • Liked Vijay Bandaru
    keyboard_arrow_down

    Scrum Master - The Team Spirit Guardian

    Vijay Bandaru
    Vijay Bandaru
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Lord Krishna was our first Scrum Master who helped "Pandavas" to win the "Kurukshetra" war without using a single weapon. On top of it, he was the almighty with so many invisible powers, but he still guided the "Pandavas" through his servant Leadership.

    Inspired by this concept, I have created a session to highlight the role of a "Scrum Master" and how can we make a Scrum Master a true "Servant Leader" without so much depending on authority or tools rather concentrating on simple things that can make his contribution to the team a true differentiating factor.

    In this task, I am going to cover the following topics:

    - Understanding the team formation stages

    - 5 dysfunctions of teams

    - Gauge the team members' behaviours

    - How a Scrum Master can make his team GREAT

    - Soft skills for Scrum Master

    - How a Scrum Master help his team in various situations

    - Importance of learning for a Scrum Master

    - Scrum Master's backlog for his team's improvements

    - Scrum Masters checklist

    I will also cover anti-patterns of Scrum Master in this session along with suitable remedies.

Sorry, no proposals found under this section.