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.
When working on an agile development project, how do you incorporate into the estimation of time for user stories/use cases/etc. the time it takes to train new developers on unfamiliar technology being used by the project?? How do other managers handle this?
Of course, my question assumes that one has deemed the technology in question necessary to complete the project successfully … or perhaps it could be considered paying down a bit of technical debt!
If we face something which is new to the whole team (or most team members), then we have performed sort of an investgation sprint, where we allow ourselves some time (timeboxed) to investigate/learn.
For smaller things, we add a timeboxed activity to the sprint backlog to allow training/investigation/experimentation.
In both cases, we simply subtract the time used so far from the estimated remaining time at the end of each day.