So the following day, I was by myself and began to take section by section. After a couple of sprints, i took a closer look at what was left. I had taken down more than half of the frame. I noticed that if I kept going down the path that I took, the front end would topple over in the other direction because of the weight. I needed to make another plan to get to the result. After some review, I felt that if I took out a couple of the studs, tie a rope to the frame, take off the bracing, and tie a line to the frame, I would be able to pull the structure down, almost like taking a leg away from a table. It would fall in that direction. The weight factor was not there anymore, and the most substantial part of the base a non-factor. As you see in the picture to the right, it fell as planned, and there was no damage done. After a few more sprints of removal, it was time to get ready for the new shed. One sprint to prep the base was structurally sound; it was time to get the new shed up. The following day was building day. With some extra help, it went up without issue. Every couple of hours looking at the directions, and distributing the work, the final product was up and tested (sprayed it with a hose to make sure it wouldn’t leak). See below.
Organizations are starting to see that the agile mindset, initially developed for software development, can be used in a lot of other functions. My demolition project could have had some catastrophic situations if we continued on our initial plan. Being agile is not about being fast, that is a welcomed output; it is about finding value and dealing with risks sooner. It would have been just as easy to knock things over and go from there. Without us attacking it in components, the surprise would have made things too much to handle. I was still able to achieve the value I wanted and was able to finish it faster than planned.