Due to us having only one story to do for our day and the testing being done for other components (Yay for taking on more stories at the end of the sprint), we tried out the fabled quad-programming, where one person codes, other person observes and two others are just distractions.
This was pretty much our day up until 1 hour before the demo when we experienced our first server downtime.
Did our deployment still work? It did not. So we needed to redeploy. We went over the changes we had made since the last deployment and speed-tested it. Now or nothing we used the luck we had and deployed our newest publication.
The time for the demo was here and the Java team went first. Having complained for the whole day, that they had nothing to present to the client to due multiple blocking stories, they sure did have a lot completed. They had chewed through most of their harder tasks and those not implemented were just tiny features on the good foundation that they had. The demo was a screaming success.
Same goes for the .net team, but with less drama and simpler demo.
The Sprint retro was highly positive and everyone found more good points to put on the board. This concluded the sprint for us and we were free to go home.
Yay for an early day