Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I don’t know if this has been discussed.
Let’s say you are in a three developer team. How would you share:
Maybe someone says this has nothing to do with asp.net mvc but I think it affects somehow.
Do it by story. But by far the best way is have 2 developers work on the same story. Working together across the whole architecture. They can share the tasks as they are needed, creating the view or the model or the stored procs, and tables etc. There will be some stepping on toes but at those times they can pair program. Try to think of the ‘team’ doing a story. Rather than a single developer, and if they all work on the same story at the same time, the development should flow at a cracking pace. As Kieron says, you need a ten minute design meeting with the whole team, to decide how its going to hang together.