Agilicious - Part 3

At the end of the last Sprint, everyone brought together the work they did over the last week, and we realized just how poorly each piece fit together. What really brought this to light was our playtest of the current material. As we worked through our boardgame and tried integrating each person's work, we found that we were having to cut out huge chunks to make the game playable.

Despite this, forcing all of the pieces together and playing with them gave us direction. We could see the weak points in the game, what features were boring, and so on. By delivering a "working" product early, we could find out what parts of it didn't fit the overall vision of the game, and which parts we wanted to cling to and develop further.

Our retrospective allowed everyone to discover the source of our frustration and difficulties - not know exactly what the hell we were supposed to be doing! We planned out our next Sprint with much greater detail, and gave what we felt were proper estimates for the time require to develop each piece. We mapped out each piece of the game into a web, allowing us to see how they all connected into each other. It also uncovered parts of the game that still had to be developed.

Overall, this meeting was very refreshing. The team was pretty satisfied, and pumped up to get to work!

Featured Picture: A web connecting each feature of the game

Comments

Post a Comment

Popular posts from this blog

Native, Web, and Hybrid apps

I'll be discussing the strengths and weaknesses of Native, Web, and Hybrid application development. Strengths And Weaknesses of Native The Native Development Kit (NDK) is a set of tools that allow the developer to write in C and C++, and is integrated with the Android Software Development Kit (SDK). Apps written in Java (the official programming language of Android) have to run in the Java Virtual Machine, whereas the code written in C/C++ can be compiled and run by the CPU itself. Native is best when there is a need for optimized performance, faster response time, and improved battery life. These are big perks for the NDK. This is ideal in video games and physics simulations, among other things. Because of Java's extra steps, this can lead to a slower app, which if you're wanting to run on older and cheaper hardware, can lead to a bad user experience and can tarnish your app rating. Using NDK has some tradeoffs compared to Java. Java is well known for its Garbag...
Read more

What is a mobile application?

What is a mobile application? There are several definitions on the web. Wikipedia says it is a computer program designed to run on a mobile device such as a phone, tablet or watch. While it might be a regular program, a person's first reaction is that there has to be a difference between a mobile app and a desktop app. At their core, a mobile app and desktop app are both just code, running on a device. Going a level up, they can be measured in limitations and capabilities. For example, a mobile device's resources are nothing compared to a desktop. Therefore, the code must be written with limited resources in mind. Imaging trying to open an Excel file such as this on a mobile device, in an app that was not optimized for a mobile device. You'd probably wind up having to pull the battery! Both mobile apps and desktop apps are created with different coding languages. Swift is a language created by Apple for iOS, macOS, and other operating systems. Java is a language known for ...
Read more

Agilicious - Part 15

Image
With everything closer to finalized, it was time for our ultimate challenge - playing our game with the teacher. It's one things to play on our own, since we put in all the work to create the game. Bringing in a somewhat outsider to go through the madness is something else. Even though our product was a bit weak, our team's glowing personalities made the experience pretty enjoyable. We had a lot of laughs, since our game encouraged dark humor. Feature Picture: The logo of the game
Read more