Timeline for Dealing with failed sprints and deadlines
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 29, 2016 at 23:06 | comment | added | Joshua K | ok, i upvoted this for the immediate rejection of blame as a concept. I agree that blame is an unproductive component that's a distraction from success. Let's change the question. Maybe we could make it "how could we have handled this"? "how can we turn this into a success for us?" "what changes from every party could have resulted in a positive outcome?" i might be ok with changing "blame" to "responsible", but as every project with a vendor and a customer is a team interaction, isn't the entire global scoped 'team' responsible anyway? the question of who is to blame then becomes rhetorical. | |
| Feb 26, 2016 at 11:19 | comment | added | Cronax | @Iker The one does not preclude the other, but the point of being truly agile in the development process is that "It's done when it's done" mentality for both the customer and the team. Sure, there are always some risks you can predict, but you can never successfully predict all possible risks and exactly what impact they will have on your progress. Unless you can see the future somehow. That's why Agile work requires specific contracting, where you agree that "we'll continue working until the money runs out, or either party is no longer willing or able to, or all the customers needs are met" | |
| Feb 25, 2016 at 10:20 | comment | added | Iker | @Euphoric I cannot entirely agree. Yes, the point of Agile is that many risks cannot be predicted, and that's what the buffer is for, I'll grant you that. However, that doesn't mean that all risks are unpredictable, nor does it mean that you should go into a project blind, without considering the risks that you can predict. | |
| Feb 25, 2016 at 9:20 | comment | added | Euphoric | -1 The point of agile is that many of the risks simply cannot be predicted. For example, they added 1 week buffer in case things slip up. You can always triple time needed, but then you loose against competition that doesn't do that. Agile should adopt "Its done when it is done" mentality. Which is simply incompatible with contracts and deadlines as described. | |
| Feb 25, 2016 at 9:08 | history | answered | Iker | CC BY-SA 3.0 |