Timeline for Coding and testing in the same sprint
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 27, 2014 at 5:48 | comment | added | Móż | @MarkRichman for every hour they pay you to type nonsense into the codebase they're losing not just the hour they pay you for, but all the hours it takes to get the nonsense out of the codebase. | |
| Jun 26, 2014 at 18:48 | comment | added | Mark Richman | I actually think that much of this organization's (to which I am new) issue is that there is little time spent up front analyzing requirements and defining a solution that can be decomposed into small atomic units. With the project and team's current state, I think the current sprint should have been nothing more than an analysis sprint, where the deliverables are PBIs complete with tasks and test cases. However, they seem to focus on the money they pay me every hour, and for every hour I'm not "hands on keyboard coding" they are losing value. | |
| Jun 26, 2014 at 17:26 | history | answered | Arseni Mourzenko | CC BY-SA 3.0 |