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

Can we bring phenomenal changes by doing small changes in the mindset of developers in the organization?

Gone are the days where the developer was responsible for just writing clean code. The 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.

The audience will work through some activities for two sprints and see the difference for themselves.

 
 

Outline/Structure of the Tutorial

  1. Introduction - 5 min
  2. How do we develop software usually? - 5 min
  3. Sprint 1- 20 min (Work in teams using traditional definition of the term 'Developer')
  4. Can we redefine the term 'Developer' to do better? - 10 min
  5. Sprint 2 - 20 min (Work in teams using improved definition of the term 'Developer')
  6. What are the benefits to
    1. Developers? - 3 min
    2. QA Engineers? - 3 min
    3. The organization? - 3 min
  7. Pre-requisites to try Developer 2.0 in your organization - 5 min
  8. Perceived roadblocks to adoption of Developer 2.0 - 3 min
  9. Tips to address roadblocks to adoption of Developer 2.0 - 4 min
  10. Some Interesting Observations during implementation - 4 min
  11. Questions & Answers - 5 min

Learning Outcome

Audience will leave the session with

  1. An understanding that "Great powers come from small changes"
  2. What is collective ownership?
  3. Some new development process to try at their own organization
  4. Hands-on experience of the philosophy of Developer 2.0

Target Audience

Scrum Master, Developers, Team Leads, Organization Leaders, Managers

schedule Submitted 4 years ago

Public Feedback