CLO 02: Post-Mortem

Our methodology process was basically the perfect description of a scrum-style Agile project plan. It’s commonly used in software development (Cohn, 2016), and although we followed a similar process as typical film making – concept art, storyboards, animatics, etc – we required a system we could change and adapt on the fly.

We adopted this for two main reasons; firstly we needed constant feedback from our client which required us to be flexible so we can make quick alterations without ruining the project flow. For example we got constant requests to change Stitches the bear but those changes were implemented without disrupting the workload of everyone else.

Secondly, since we also had other classes doing weekly meetings allowed us to stay on top of what was needed to be done and what had been completed, and if anyone needed to take up the slack. This was implemented because of tragic personal experience where not enough tabs were kept on some members which increased stress for everyone.

As the hallmark of the scrum method is constant meetings for the next sprint (Cohn, 2016), we had a weekly meeting before class where a dedicated leader – Rob and Cameron in this case – went over what objectives needed to be done. This was a great way to ensure that everyone was on the same page, knew who was working on what, work would be given to those with the best skills and could adapt to incoming problems. For example I was honest upfront about my limited ability to take on heavy workloads, so when the work was distributed I could be given work I knew I could do.

The second hallmark of a scrum method is constant communication (Bonnie, 2014), which we did over Slack, Skype, emails and the Google drive. This way if anyone needed help they could get it immediately instead of falling behind everyone else.

This level of planning and supervision I think was the key to keeping the project on track and delivered on time with minimal stress on everyone involved. This group was the best one I have ever worked with during my entire education and I was happy to be a part of it.

References:

Bonnie, E. (2014). Fundamentals of the Scrum Methodology. Wrike Blog. Retrieved 2 September 2016, from https://www.wrike.com/blog/fundamentals-of-the-scrum-methodology/

Cohn, M. (2016). Scrum Methodology and Project Management. Mountain Goat Software. Retrieved 2 September 2016, from https://www.mountaingoatsoftware.com/agile/scrum

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s