Skip to main content
15 events
when toggle format what by license comment
Jul 22, 2013 at 6:34 audit Close votes
Jul 22, 2013 at 12:07
Jul 15, 2013 at 12:36 vote accept Szili
Jul 10, 2013 at 6:11 audit Close votes
Jul 10, 2013 at 6:12
Jul 9, 2013 at 4:00 answer added Michael timeline score: 5
Jul 4, 2013 at 5:49 comment added jwenting slice the topics vertical, then slice the resulting stories into horizontal tasks.
Jul 4, 2013 at 3:13 answer added Erik Reppen timeline score: 1
Jul 4, 2013 at 2:20 comment added Erik Reppen My fantasy solution involves occasional slapping of all parties. slap Stop whining. slap Stop ignoring the critically important role that data and business logic contributes to the success of the business that pays our rent. slap Stop eating other people's lunches. It's not your mom's refrigerator.
Jul 3, 2013 at 17:08 history tweeted twitter.com/#!/StackProgrammer/status/352474062901100546
Jul 3, 2013 at 11:35 vote accept Szili
Jul 15, 2013 at 12:36
Jul 3, 2013 at 9:31 answer added sleske timeline score: 11
Jul 3, 2013 at 9:21 answer added Sklivvz timeline score: 4
Jul 3, 2013 at 8:41 comment added Bart van Ingen Schenau Making separate back-end stories implies that the back-end work can be prioritized separately from the front-end. This has the risk that the priorities get assigned such that the back-end work gets relegated to the bottom of the backlog until it gets re-incorporated in the front-end stories. For the problem with the lack of appreciation from management, I recommend you ask about that over at Workplace.SE.
Jul 3, 2013 at 8:27 review First posts
Jul 3, 2013 at 9:07
Jul 3, 2013 at 8:21 comment added margabit I wouln't have the backend stories, they make no sense.. However, I wouldn't like to have that kind of managers.. I thought the backend devs were the rockstars some time ago
Jul 3, 2013 at 8:07 history asked Szili CC BY-SA 3.0