Scratch 1.1.7
"crazy ball game"
Partners: Mitchell Stepp, Brandon Roeling
Final Product
Abstract |
Rubric and sketches
|
Our team created a geometry wars game. We used the Scrum framework to develop our game. A Decision Matrix was created to help analyze our ideas and narrow the choices. Once our game was selected we created a Product Backlog consisting of five user stories. From the product backlog, we created our first sprint. In our first sprint, my task as a Scrum Development Team Member was to create an object that can jump on top of or over obstacles.
|
|
Reflection
This project proved to be more challenging than we thought. In order to get anything to work, we had to have everything working at the same time. This forced us to do two almost entirely separate things at once. The consequence of this was that our code was not compatible with each other but it had the framework for an entirely different game. We had very little time left so we had to change our end product in order to meat deadlines; for there was no time to start over. This turned out okay. we ended up getting a working product in time despite the obstacles in our way.
Problem 1.2.6 Designing an App
"Get Cookin'"
Partners: Dakota West, Michelle Huerta, Mitchell Stepp
Final Product |
Abstract |
Artifacts: Rubric, Product Backlog, Decision Matrix |
Our team created a cookbook app. It contains various recipes including a variety of ingredients and are practical. The app opens to the main menu where you can select which recipe you are going to use. Once you click the recipe it will show you a picture of it and tell you step by step how to make it.
Artifacts: Sketches, Code
|
Reflection
We used the scrum framework to develop our app. We began our project working on a different idea. It was a Stepper named "Stepp Up" based my last name. We worked for this for many days and came up with something that didn't work correctly. We had to change our idea to something that we could complete. That is where we came up with the idea of "Get Cookin". This was something that we knew we could complete and we could use even out of the app because all of us liked to cook. We were able to get through this quickly and easily. The only thing i wish we could have done more on is the GUI. It doesn't look very nice and there are no pictures of our recipes.
Problem 1.5.4 Design a Python GUI
"Chicken"
Partners: Mitchell Stepp, Efran Padilla, Michelle Huerta
Final Product |
AbstractMy team created a game about feeding a chicken and keeping it alive. The app would open to the chicken where you could see it running around and interact with it. You could feed it, water it, and play with the chicken. We also included options to change the color of the chicken, what food it eats, and what the background is.
|
Artifacts: Rubric, Product Backlog, Decision Matrix |
Artifacts: Sketches, Code |
Reflection
This product was more difficult than we anticipated, making the chicken become hungry, and getting it to move across the screen on the press of a button wasn't easy. However, we were able to accomplish some of these tasks. we got the chicken to move across the screen and had the basic GUI. We were never able to get the hunger bar to work and couldn't get the chicken to do many different animations, but there were some things still functional. Our main issue, which was also the issue of our classmates, was a virus that came through and wiped out all progress. We were only able to bring together the gui and some buttons in time .