Timeline for Who should be responsible for writing/updating design specifications in an agile team
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 30, 2020 at 19:38 | history | edited | Thomas Owens♦ | CC BY-SA 4.0 | deleted 27 characters in body |
| Jul 10, 2017 at 21:48 | comment | added | Andy | I find it helpful to own a car, but I'm not going to build one by myself. | |
| Oct 10, 2011 at 3:09 | vote | accept | DXM | ||
| Oct 6, 2011 at 19:45 | comment | added | Thomas Owens♦ | @DXM Find out why they don't want to do those things, especially if they find the existance of the documents helpful. One of the things that the agile methods are really good at is continuous improvements through your retrospectives after each iteration. Having people who are fighting the process and artifacts is only going to be a hinderance to the rest of the team, so try to figure out what the problem is and deal with it appropriately. | |
| Oct 6, 2011 at 19:18 | comment | added | DXM | Thomas, I completely agree that putting responsibility in the hands one developer is dangerous and anti-agile. What if you have more than one developer, but taking out of the hands of "certain" ones. So the question is if different people have different skills/strengths/competencies, should they still be given completely equal responsibilities in the team? And don't get me wrong, I encourage and help anyone that wants to take on more things, but it seems certain people just don't want to do those things in the first place. | |
| Oct 6, 2011 at 18:39 | history | answered | Thomas Owens♦ | CC BY-SA 3.0 |