Agilicious - Part 5
After creating my set of buff cards from the previous post, the team had gathered to review what was created. Again, suffering from the same ambiguity mentioned in my second blog post of the series, we found that many folks' work just couldn't fit together. As I worked on buff cards, another team mate worked on them as well. With two people working on the same task, you can get one of two results - you're both on the same wavelength, or you put out completely different results. What separates the two? Communication!
My team member and I shared our documents with one another, sure. But when we went to review our results, well... you can tell that we didn't communicate. Where my buff cards were generic-use types, his were more tuned to each individual class in the game. Even though we both created two different types of cards, it didn't mean we had to toss out one person's work though! After review, my team member really liked the format of my buffs, with phases, and number of turns. I like how each of his buff cards had a special effect when used by a certain class. We decided to merge both of our work into one united feature.
Featured Picture: Some of our collaborative buffs
My team member and I shared our documents with one another, sure. But when we went to review our results, well... you can tell that we didn't communicate. Where my buff cards were generic-use types, his were more tuned to each individual class in the game. Even though we both created two different types of cards, it didn't mean we had to toss out one person's work though! After review, my team member really liked the format of my buffs, with phases, and number of turns. I like how each of his buff cards had a special effect when used by a certain class. We decided to merge both of our work into one united feature.
Featured Picture: Some of our collaborative buffs
Comments
Post a Comment