I was flicking through the Scrum Alliance site when I found an article entitled “The Accidental Scrum”. It was written by Royal Navy Logistics officer who was posted to a Ship that had to leave port sooner than expected. He had to have the ship ready to leave port in 5 days time when origionally he had been given a few weeks to prepare.
He describes the common sense approach that he took to prepare the ship for deployment. Coming from A software development background before being deployed to the Royal Navy, he knew nothing of Scrum and how it works. It was not until later that he would find that the method he took to get his ship ready was infact Scrum. He describes Scrum as a common sense approach, which when you think about it, scrum really is all about common sense. He describes in basic terms how he tackled getting the ship ready for deployment in a short time using Scrum.
“Without knowing Scrum at all, I had set a sprint goal (“We have to be shippable, quite literally, in five days.”), developed the product & sprint backlogs (our deployment requirements and daily priorities), and established a daily scrum. I knew intuitively at the time that we had to come together at least daily to monitor progress and that any issues affecting the sprint goal had to be resolved by me, so that the team could be left to deliver. Now I understand that what I was doing was setting up daily scrums and acting as ScrumMaster for the team.”
This is an interesting article for me, as up until recently I have only been focusing on Scrum in a Software Development sense. I think that when you look at Scrum as a bigger picture you begin to understand it more.