(What project management strategies did you use in your projects this module? What went well? What would you do differently next time?)
I think the most important project management strategy/agile practice that came up during our projects was "Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage." During the Game-Time project, Jack and I front-loaded the project because we knew that Jack would be gone over the weekend and not able to do any work. Because of this heavy front-loading, we made some choices that ultimately required us to make some big changes to code that was actually already working. It became important for us to realize that sometimes change is necessary. Sometimes if you allow for change, better results happen. During the rest of the module, our class also participated heavily in the principle of "The best architectures, requirements, and designs emerge from self-organizing teams." For the algorithms and complete-me projects, we worked as a team to accomplish all of our goals....and did an amazing job if I might say. By helping each other stay motivated and organized, we produced a product that was by far better than if we had all worked alone. That said, I think this is where we need improvement. During these group sessions, a few people had the driver seat and the rest laid back and took it all in. A better strategy might have been to talk about the concepts of a particular functionality as a whole class/group and then split into smaller groups where everyone might have had a better chance at trying their ideas or at least getting to speak a bit.