The statement that popped out to me in the video you assigned us to watch is that better planning means less wasted effort. Looking back at my prior entries, I noticed a trend. That trend was that I often mentioned that I should have done something earlier.
This statement can pretty much be applied to anything, but regardless, it is an important concept to keep in mind, especially in code world. The second statement that popped out to me is that it’s important to have a shared definition of done. As DJ’s post says, you’re never really done with your site/project. When referring to agile practices, it’s most important that everyone is on the same page and understands the point in which they are trying to reach. I have kept this in mind when thinking about/referring to my site. There are so many improvements that can and should be made to my site, but all of those changes will not necessarily be made by Sunday. I learned that it is important for me to set a goal of what it is that I want, and just get there. Everything else that may come to mind later on that I want to add can be added at a later time as well.
What I learned most through the reading/video is that the teachings are close to identical to what you’ve taught us from the beginning of this class. We were asked to pick the functionalities of our sites (keeping them realistic) and we were given a deadline. We were encouraged to test them before deadline to ensure all of the bugs were worked out. As we critiqued one another’s sites, we played the user role.