2 added 5 characters in body
source | link

I think this question related not only to agile but to teamwork in general. When

When we are working in a team and each member areis working a user story to complete how to avoid creation of duplicate classes and conflict. i?

I mean if my user story require the creation of class A and also my team member need the same class and created the same  (he may create it with slightly different name)., how would we plan so that we move smoothly.?

I think this question related not only to agile but to teamwork in general. When we are working in a team and each member are working a user story to complete how to avoid creation of duplicate classes and conflict. i mean if my user story require the creation of class A and also my team member need the same class and created the same(he may create it with slightly different name). how would we plan so that we move smoothly.

I think this question related not only to agile but to teamwork in general.

When we are working in a team and each member is working a user story to complete how to avoid creation of duplicate classes and conflict?

I mean if my user story require the creation of class A and also my team member need the same class and created the same  (he may create it with slightly different name), how would we plan so that we move smoothly?

    Post Migrated Here from stackoverflow.com
1
source | link

Team work and agile development

I think this question related not only to agile but to teamwork in general. When we are working in a team and each member are working a user story to complete how to avoid creation of duplicate classes and conflict. i mean if my user story require the creation of class A and also my team member need the same class and created the same(he may create it with slightly different name). how would we plan so that we move smoothly.