Trivs i Lisebergs södra

Case 1: Make function const vs. non-const const Track& ScoreTableElement::getTrackLeft() const {     return left_; } vs. const Track& ScoreTableElement::getTrackLeft() {     return left_; } The difference is, if the function is not marked const, then we can not call this function on a const variable or const reference variable, because this function could change the content of the object, so the const variable/reference will not allow the calling of this function. Example: sf::of::ScoreTableElement element(track_left, track_right, 4.5F); scoretable.push_back(element); const sf::of::ScoreTableElement element_out = scoretable.back(); // or const sf::of::ScoreTableElement & element_out = scoretable.back(); element_out.getTrackLeft(); // compiler error getTrackLeft() is not const function Case 2: Assign return const reference to const vs. non-const reference const Track& ScoreTableElement::getTrackLeft() const {   ...

Problem description: When a sprint finishes, some unfinished user stories have a status in which some of the work, or sometimes even most of the work is claimed to be finished already. The remaining work to be done will naturally be rolled over to the next sprint and get its size re-estimated. However, the question remains when it comes to how to handle the credits that lies partially in these user stories. Should the story points be extracted and summed up as finished story points in the previous sprint?  There is some discussion on stackoverflow The solution could be this one: Do not take partial credit for semi-finished user stories, based on splitting the big user stories into smaller ones as mush as possible. Here is a good article that explains this: https://www.mountaingoatsoftware.com/blog/dont-take-partial-credit-for-semi-finished-stories