- Setup the git
- John prepared the initial documentation to help us get organized
- We decided on building upon an existing Greenfoot Application
- We split up the XP Core values among the five of us (I have been assigned to "Simplicity")
- Decide on a specific Greenfoot application to build upon
- Found games that we could work with
- We decided on working on the P-Type Greenfoot game
- This game is a simple skeleton that we will be able to build upon more easily than the more developed games that have been published.
- The skeleton gives us room to decide on what features and patterns can be applied to the source code.
- We listed out some features that we could work with
- So far, the list of features is simple enough. Nothing is too complex.
- However, some of them may not be necessary. I will discuss this next time.
- Turn the features into user stories / use cases / tasks
- John compiled some detailed notes on the features we may implement.
- We went over John's notes and discussed them further.
- I had to make sure that our plans are not too complicated.
- I noted that we should focus on stories/features that would allow the implementation of patterns.
- The tasks that are later drawn out should be reasonable and be completed within our limited time frame.
- We compliled a draft list of user stories
- From the user stories we compiled a draft list of features that are derived from the stories
- Turn the features into tasks
- Delegate the tasks and label their priority levels
- Start working? (ASAP, since we are running out of time)
- Reviewed the extracted features and tasks
- Assigning priority levels
- Delegated tasks for each member
- I tried simplifying the requirements so that the tasks are achievable within reasonable time
- Perhaps my direction is wrong, but I wanted to prioritize tasks that allowed for the implementation of a pattern
- Although, some base features may need to be implemented before a pattern can be applied
- Start working on the assigned tasks for the week
- The 5 starting items from the backlog have been moved to the TO-DO list.
- I will be implementing the display of player lives and adding a score feature
- John created the base for the boss level.
- Sid set up a base for the Settings page
- I have created a display for player lives using the observer pattern.
- Sid continues to work on the Settings page by incorporating the buttons for volume
- The game/intro volume are separate from the sound effects.
- Having one being adjustable is a good start.
- We can leave sound effects as a separate, lower priority task.
- John continues to work on the Boss level.
- I suggested that the boss level can just be a static level with just one boss enemy, just to simplify the task.
- The level design will be left to his discretion.
- Progress from Faizali is unknown at this point.
- Hashmitha has no access to the repo.
- I will clean up anything from the Life display code
- I need to start working on implementing player score and displaying it.
- John added a Debugger display on the screen
- Sid has successfully implemented buttons for volume adjustment
- I made code adjustments to the life display and fixed some bugs.
- We are discussing what will need to be done next.
- I asked John about specifics in implementing the score. He helped in reminding me to keep things simple.
- Faizali says he has something in the works for the Leaderboard.
- I briefly discussed with him again on possible pattern implementations for the leaderboard.
- It really depends on how Sid's finish screen will work and how it will cooperate with the leaderboard aspects.
- Hashmitha has not started any work yet.
- Not sure if she has asked the professor about repo access.
- Sid will start working on the Finish screen.
- John will continue to make progress with the Boss level.
- I will start on the implementation of player score and displaying it.
- John has made more progress on the boss level. A Mega UFO is on the screen.
- I have implemented the player score and display.
- Sid has made progress on the finish screen, but it introduces new bugs.
- John is finishing up the boss level. We are thinking about what pattern he could implement.
- Sid is fixing the bugs with the finish screen.
- Faiz is implementing basic leaderboard components.
- No communication from Hashmitha.
- Sid and Faiz will need to integrate their parts together.
- I need to work on the wireframes as well as fix any minor bugs.
- John will implement a pattern into the boss level.
- John has made further progress with the boss level.
- John also took over Hashmitha's assignment in updating the main screen.
- I made simple sketches of the wireframes.
- Faiz has put together an iterator for the leaderboard component.
- Faiz and Sid are still working together.
- John and I are looking for any new bugs to squash.
- We need to put together the README components.
- We need to consolidate the source code to be working.
- We need to record the 1-min pitch video.
- I updated parts of the burndown chart.
- John is continuously updating our Readme.
- He put together several diagrams.
- We are putting together a draft of our presentation.
- We are working on and discussing what to include in the Readme.
- We need to continue with putting the presentation together.
- We need to see what Sid has put together.
- John was able to add a toggle to the Debug display.
- I updated the observer patterns to be more correct.
- I am working on the pitch video.
- Sid is fixing bugs on the finish and leaderboard screens.
- I think it is best, at this point, to focus on major bugs and not worry about the minor ones.
- Sid will continue to complete his parts.
- I will continue to work on the video.
- Sid has pushed his code up.
- I have completed the pitch video.
- We are going over Sid's work.
- It is almost ready to go. We need to resolve some conflicts in the code.
- We are still figuring out what to do with the presentation.
- We need to prepare the video.
- Sid is finished with his coding tasks.
- We are resolving code conflicts together.
- The source code should be ready at this point.
- We can do a whole end-to-end run that presents all the features.
- We are still discussing what to do for our video.
- We have decided to record individual parts for our slides, and we will put them together in one video.