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.

1. @Vivek_Ganesan
Developer 2.0
Redefine the role of Developer to achieve success for all
Vivek Ganesan
Scrum Master
Gainsight

2. @Vivek_Ganesan
A Glimpse of
Traditional Software
Development Team

3. @Vivek_Ganesan
Coder
QA Engineer

4. @Vivek_Ganesan
Coder
QA Engineer
Product Owner

5. @Vivek_Ganesan
Coder(s)
QA Engineer
Product Owner
Scrum Master

6. @Vivek_Ganesan
Why not try something
different?

7. @Vivek_Ganesan
Coder
Devil’s
Advocate
Reviewer
Developer 2.0

8. @Vivek_Ganesan
Developer 1 Developer 2 Developer 3
Story 1
Story 2
Story 3
Coder
Devil’s Advocate
Reviewer

9. @Vivek_Ganesan
Test Case
Authoring

10. @Vivek_Ganesan
Test Case
Authoring
Test Case
Review

11. @Vivek_Ganesan
Test Case
Authoring
Test Case
Review
Solution
Development

12. @Vivek_Ganesan
Test Case
Authoring
Test Case
Review
Solution
Development
Solution
Review

13. @Vivek_Ganesan
Test Case
Authoring
Test Case
Review
Solution
Development
Solution
Review
Happy Product
Owner

14. @Vivek_Ganesan
Test Case
Authoring
Test Case
Review
Solution
Development
Solution
Review
Happy Product
Owner
Happy
Customer

15. @Vivek_Ganesan
Test Case
Authoring
Test Case
Review
Solution
Development
Solution
Review
Happy Product
Owner
Happy
Customer

16. @Vivek_Ganesan
Why is this good for
Coders
?

17. @Vivek_Ganesan
Why is this good for
Coders
QA Engineers
?

18. @Vivek_Ganesan
Why is this good for
Coders
QA Engineers
Organization ?

19. @Vivek_Ganesan
How is this possible?
What is needed to get there?

20. @Vivek_Ganesan
Key Learnings from
Implementation

21. @Vivek_Ganesan
Any Questions?