↳
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. Less
↳
It’s about demonstrating it to them and comparing the efficacy compare to other frameworks via dissecting a story vertically to the smallest size possible. Less
↳
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. Less
↳
I gave a summary of my extra skills and projects I have completed
↳
I start with my field. My years of experience and the various industries I have worked, the positions occupied and responsibilities in the various companies . Less
↳
I start with my field. My years of experience and the various industries I have worked, the positions occupied and responsibilities in the various companies . Less
↳
I expect the salary to be competitive.
↳
I was uncomfortable with the question and had to dodge it twice.
↳
I told them I did my research and asked for what was on here as starting salaries. I was told he was impressed by the fact that I researched them and was given an offer as expected. Less
↳
Team velocity is tracked, using the number of estimated story points, over the actual completed story points. This can be measured on the burndown chart. You can guesstimate your team velocity overtime, from the previous sprints. Less
↳
Velocity is the total story point the team complete in a sprint. It can be tracked in the burndown chart in Jira for instance. Can be determined for an existing team by adding up velocities of 3 sprints and dividing it by 3 to get teams velocity. Less
↳
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. Less
↳
Let’s get it together and I’m ready
↳
As politely as possible, I replied that unless there is a real emergency, I will not work late or weekends. I went on to explain that most people working overtime so much are poor planners and are unable to manage time efficiently. I have always been able to plan, track and work in such a way that I never have had to work late. Less
↳
Why would anyone so no? My ambitious response for the entertainment industry at Fillmore is a strong big YES! Kindest Regards Less
↳
After asking several qualifying questions and not getting clear/good answers I was able to walk the interviewer through 3 different scenarios. As more details were revealed, the time to cross grew. Less
↳
a minimum of 11 #2 and # 4 goes, then #3, then #1
↳
Project Quality control and promotion of the team numbers
↳
roles and responsibilities of project team members
↳
Are you serious? Please, disclose a few details. that is a worst thing could ever happen to a candidate. Less
↳
I'm not naming names or divisions because that doesn't really help me any. The rejection motivated me to go back and get a Masters in CS at a Top 5 school. Amazon has an incredibly competitive culture and what manager wants to hire someone that might be able to pass them? There's two sides to every story, maybe I misread it but I'm trying to be as honest as I can. Less
↳
Cowculator...
↳
I answered that I will check goverment census and get the inputs from them, then interviewee asked if they donot have that information, then I mention I will check which are the areas more diary products are selling I will get the counts, then I said I will check from feed store where more cow feeds are selling I will get the counts from those area Less