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

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.


Outline/Structure of the Talk

Introduction - 5 min

How do we develop software usually? - 3 min

Activity 1 - 15 min

Can we redefine the term 'Developer' to do better? - 5 min

Activity 2 - 15 min

What are the benefits to Developers? - 2 min

What are the benefits to QA Engineers? - 2 min

What are the benefits to the organization? - 2 min

Pre-requisites to trying Developer 2.0 - 3 min

Questions & Answers - 8 min

Learning Outcome

Audience will leave the session with an understanding that 

  1. Great powers come from small changes
  2. What is collective ownership?
  3. Some new development process to try at their own organization

Target Audience

Scrum Master, Developers, Team Leads

schedule Submitted 5 years ago

  • Jeganathan Swaminathan

    Jeganathan Swaminathan - TDD - the good, bad and ugly part

    45 Mins

    Being an Agile Coach & TDD Consultant, I have helped many product companies during their Agile transformation journey. I have observed many interesting good, bad and ugly practices followed in industry in the name of TDD. I would like to share my experience with the audience and guide them towards the correct direction and help them extract the true benefit of TDD.

    To give a simple example, using code-coverage as a metrics to measure the effectiveness of the Unit Test Cases is one of the common mistakes committed by many companies. 

    In my presentation, I would like to demonstrate hands-on and discuss, how to effectively follow TDD and what to watch out and avoid bad practices in TDD.