Timeline for In an agile project is it ok to change the requirements of the sprint in the middle of the sprint?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 30, 2018 at 6:59 | comment | added | Dan | Another aspect is that today the front end of websites can be build extremely quickly and to a high standard. But that really depends on the overall planning of the project. The reason for this is the modern component architecture of javascript frameworks. If a developer has like a perfect idea of what he/she will do over the next few weeks, they can leverage the power of these frameworks and deliver great products built with great code. If there is disorganisation, I would say the length of time can increase several times due to the difficulty of reusing code and maintaining good structure. | |
| Apr 29, 2018 at 18:02 | comment | added | Dan | I think that is well said ... I will also just add. While I understand agile, and I think it is superior to waterfall no issues there. I think this philosophy can be abused, and it really comes down on front end developers hard. Because basically as a project leader it can be a license to not have a plan and whimisically order stuff. And as mentioned the front end developer is the last point in product development, so it hits them hard when deadlines have to be reached. It can be really unfair for them. | |
| Apr 29, 2018 at 15:08 | history | edited | Mike Hofer | CC BY-SA 3.0 |
added 905 characters in body
|
| Apr 29, 2018 at 14:54 | history | answered | Mike Hofer | CC BY-SA 3.0 |