Skip to main content
12 events
when toggle format what by license comment
Jan 29, 2019 at 23:07 vote accept ENDK
Jan 24, 2019 at 21:00 history tweeted twitter.com/StackSoftEng/status/1088542102093471744
Jan 24, 2019 at 20:19 answer added Martin Maat timeline score: 0
Jan 24, 2019 at 14:13 answer added Bart van Ingen Schenau timeline score: 3
Jan 24, 2019 at 7:37 answer added Ewan timeline score: 0
Jan 23, 2019 at 21:18 comment added ENDK @RikD Usually they are questions that the PO or the Analyst asks to the development team, for the work that will come for new sprints, in fact the example of the spikes, is just that, work that will be done in the next iterations of the sprint but require some feedback of the development team, that's why it takes a little time to answer it, since sometimes there is a need to analyze what you have to answer
Jan 23, 2019 at 21:12 comment added Rik D What's in these emails that it takes hours per day reading and replying? If this work is really part of the software development process, it should probably be added to the board. It's more likely that these are actually management or support related tasks, not relevant to the current sprint or maybe even the current project, in which case the work shouldn't be added.
Jan 23, 2019 at 17:27 history edited ENDK CC BY-SA 4.0
added 704 characters in body
Jan 23, 2019 at 17:21 comment added ENDK We have user stories that are selected to enter the sprint and we break them into different tasks, the example I give of the email is an example of something that is not within the sprint but requires a response from the development team.
Jan 23, 2019 at 17:11 comment added nvoigt Most examples you gave to me are red flags regardless of representation on a board. How is your backlog structured? Do you have user stories? Do you break them down into tasks? What do you put onto the board normally?
Jan 23, 2019 at 16:50 review First posts
Jan 23, 2019 at 17:02
Jan 23, 2019 at 16:48 history asked ENDK CC BY-SA 4.0