Andrew Michael Miller's Thought Backlog
Writer and working Agile professional. Author of Pancho's Fall.
Sprint Review is an informal meeting held at the end of the Sprint where the increment is presented to promote the collaboration and obtain the customer's feedback on the developed product. It is mainly conducted to 'Inspect' the Increment and 'Adapt' the Product Backlog if required. The Sprint Review is not the time to nitpick the team's processes; that is supposed to happen at the Sprint Retrospective meeting later on.
So you were asked to be the Best Man at an upcoming wedding. First off, congratulations! By being chosen as the Best Man, you have agreed that you are, indeed, the best man for the job. Hopefully you are aware, however, that it’s a job that requires you to prove to everyone why you were chosen. The biggest, most important task of the Best Man during the wedding reception, of course, is the speech you have to give to all of the people there. And you better knock ‘em dead because all eyes are on you. But don’t fret, I’ve got you covered.
In the still of the night, as the crickets’ chorus crescendoed and slowed to a scarcely recognizable tune, the cold air crept onto the property of Charles Douglas. The peaceful silence, which had always been the best salve for his tired and restless body, came upon him as it had most nights. At 87 years old, Charles appreciated every ounce of sleep his mind would allow. After all, Charles had seen more shit in his lifetime than anyone else he knew, and that made him an angry old man, unloved by everyone with whom he came into contact in the few times a week he would venture to show his face in public. But that was the way he preferred it; if he didn’t make any new friends, he would never have to lose them in one tragedy or another.
All sprints come to an end. After a set period of time, the sprint will come to a close and the team will review the work done in the sprint, and then reflect on the things that went right and the things that went wrong in the sprint. A new sprint begins as soon as the current sprint ends. Every sprint should be able to produce something immediately usable.