I was fired from a job because of Agile... I'm a C developper, and one part of the server had Java development. Well, guess who had to take the post-it, because "that is the way things are done". So here I was doing Java, on a ticket that was supposed to take a day, I did it in 4. I had to take the ticket, because that is what Agile is about. During the scrum meetings, I said I had problems with it, but I couldn't ask for help, because I took the ticket, and "that is the way things are done". I was a 6-month trial period, so they sacked me with no warning, because I was crap at my job. Since then I've been working with multinationals, and the previous company has made one single iPhone App that has a rating of 1-star, their previous flagship application is now one-star too (and on the verge of a lawsuit because of a dodgy change of contract for the application). Since then, I've had real Agile training, and the trainer explained the way things were really done, and at least I know I wasn't in the wrong. Still, my first Agile experience cost me my job. That's what I remember.
I think if you had a problem developing or fixing that issue, you should mention them clearly in the scrum meeting which you have regularly that you are are a C developer haven't done much of java development so the issue which I am dealing right now may take a little longer, or I am not at a stage of setting the deadline right now. There is nothing wrong in asking for help if they want to get it done sooner or you could do it by learning but it would take a little longer, but its always good to inform.
Same thing happend to me, it was giving spacegen , outofmemory error all of a sudden and eclipse would crash....
I almost wasted 4hrs to find out the problem..
Slashdot Mirror
It is also obvious that men do less dumping then woman do...
I was fired from a job because of Agile... I'm a C developper, and one part of the server had Java development. Well, guess who had to take the post-it, because "that is the way things are done". So here I was doing Java, on a ticket that was supposed to take a day, I did it in 4. I had to take the ticket, because that is what Agile is about. During the scrum meetings, I said I had problems with it, but I couldn't ask for help, because I took the ticket, and "that is the way things are done". I was a 6-month trial period, so they sacked me with no warning, because I was crap at my job. Since then I've been working with multinationals, and the previous company has made one single iPhone App that has a rating of 1-star, their previous flagship application is now one-star too (and on the verge of a lawsuit because of a dodgy change of contract for the application). Since then, I've had real Agile training, and the trainer explained the way things were really done, and at least I know I wasn't in the wrong. Still, my first Agile experience cost me my job. That's what I remember.
I think if you had a problem developing or fixing that issue, you should mention them clearly in the scrum meeting which you have regularly that you are are a C developer haven't done much of java development so the issue which I am dealing right now may take a little longer, or I am not at a stage of setting the deadline right now. There is nothing wrong in asking for help if they want to get it done sooner or you could do it by learning but it would take a little longer, but its always good to inform.
Same thing happend to me, it was giving spacegen , outofmemory error all of a sudden and eclipse would crash.... I almost wasted 4hrs to find out the problem..