I said I would talk to them about t-shirt sizing and try several ways to help them understand that story estimation has little to nothing to do with time, rather effort. I also explained that this was a challenging topic for a new team.
Story points should be explained to a team that's new to agile, that it's an agreed upon estimate. Explaining to teams that it's the amount of
Time vs effort.. teams get hung up on time based estimates. And not about the amount of effort it's going to take to accomplish a task/user story.
I said that I had a little bit, as we still had a bit of a challenge on my last team comprehending the burndown chart and how to improve estimates. How to determine it would be based on the Sprints. I kind of fumbled through this one as I really hadn't ever had much velocity tracking training, I just winged it at that time.
I spoke of setting up private meetings with the counter-parties in question. The substance of the question I found troubling. So much so, I must forward to you the suggestion that you pick another potential employer in the stead of Omgeo, Inc.
- Code is fully tested with each sprint (little or no technical debt built up) - Emphasis on interaction over documentation allows for live feedback on ideas rather than producing documentation that is not needed. - Give Scrum Team the ability to control schedule, sprint by sprint - Many others.