Version 54 (modified by dersek, 2 years ago)

--

Notes for the Week

Notes for the Jan 19 Meeting

Notes for the Jan 22 Meeting

Notes for the Jan 23 Meeting


Previous Week:

Ticket # Owner(s) Task Check-in / Intermediate Deadline
#1 All Preparation (intermediate deadline) for Competitive Analysis N/A
#2 All Preparation (intermediate deadline) for Pre-Elicitation N/A
#3 Kevin and Buike High Concept Writeup 1/23
#4 Meredith Competitive Analysis Compilation 1/23
#5 Kevin and Buike Pre-Elicitation Slides 1/23
#6 Meredith Pre-Elicitation Questions and Reqs Compilation 1/23
#7 David Management Update 1/23

  • Assessment:
    • Wiki Setup: Wiki Setup is going smoothly - Getting to know the wiki format and create all the necessary pages has taken roughly 1.5 hours
    • Comparative Analysis Prework: Setting up a Google Doc was useful to allow everyone to contribute. The job of compilation is much easier than writing everything from scratch. The process of looking up/ playing/remembering a game and then evaluating it took roughly .5 hours
    • Elicitation Prework: Again, setting up a Google Doc was helpful for balancing the work load between all of us. ~ .25 hours
    • High Concept Brainstorming: We did this during our meeting. Meeting as a group allowed us to effectively discuss ideas and address questions and concerns from other members. ~ 1 hour

  • Time Estimates: Time tasks/goals took to achieve was reasonably close to expectations. As this is the first week, we don't know if the estimates are getting better.

  • Missed deadlines: None as of yet.
  • Project progress: The 4 documents due for the project are progressing well and a check-in meeting was scheduled on Monday in order to ensure the quality of each document. Only the Competitive Analysis was evaluated at this meeting, but all members report their specific tasks going well and have any questions necessary before additional work have been answered.
  • Team progress: Again, the team has only been together for a short amount of time. However, we have discussed the roles of the Game Designer - mentioning that the role includes setting the team agenda for meetings and facilitating the meetings. All meetings have seemed productive thus far. For these meetings, however, it may have been better to plan out the work for next week as a group. Part of this came from a misunderstanding of the meeting schedule - thinking that the meeting before Tuesday is meant for the current week, rather than planning out the next week. While it is important to prioritize based on our goal stack (stuff this week is due first), it is equally important to be prepared for the next week.

Current Week:

New Goals

As mentioned in the weekly plan, all goals currently line up with the deliverables.

  • Verify our design objectives/requirements with the customer (Customer elicitation)
  • Fill in the parts of the game that are not yet clear (Use cases)
  • Come up with a reasonable approach to creating the game and prototype (Tech assessment)
  • Make sure our game is interesting to students (Game treatment)

These goals come from our top three current design objectives (summarized and simplified):

  • Teach the material
  • Make the game robust
  • Provide motivation for children to continue playing

New Deliverables

  • Customer requirements elicitation report ~ 1 hour (individual)

The Elicitation report is a document designed to ensure that the team is clear on the customer's requirements and needs. The risk of not getting this document done on time is that the product we start to create Use cases for, get feedback on, and decide the feasibility for will be a product that does not satisfy the customer's needs.

  • Use cases ~ .3 hours (group), ~ 1 hour (individual)

Use cases give snapshots of how the program will work. It allows us to figure out issues we will run into ahead of time, allowing us to prepare for them. It also allows us to get a sense of the major components that will be implemented in the code, which will be useful for the Technology assessment. The risk of not completing this document are that, without the program's uses being well defined, time will be wasted as we encounter errors later on after coding has been done and have to spend more time to fix them. In addition, it is more difficult to fully assess the feasibility of our project without knowing what that project will look like. Thus the technology assessment depends partially on the Use cases.

  • Technology Assessment ~ .3 hours (group), ~ 1 hour (individual)

The Technology Assessment is a document that assesses the tools and technologies at our disposal that will help us successfully implement the game. It will help us determine the approach for a given project that is most likely to be successful and be completed in time. Once we have a close idea of the game we will be designing, this document will help us ensure we are making the right choices in terms of our tools. The risk of not completing this document is that without a clear idea of what tech approach we will be using, we may arbitrarily choose an approach that will take more time or effort compared to another approach, resulting in us loosing time that could be used for improving the game, catching bugs, etc. In the worst case, we may have to change tech approaches mid-project (such as using a different language), which will be very time consuming.

  • Game treatment ~ 2 hours (individual)

The game treatment is very helpful for making sure the students would want to play the game we are creating. As this is our 3rd design goal, it is not as important as teaching the necessary content, but still very important. This information will allow us to see if our current plans for a scoring system and a plot are interesting enough for the students. The risk of not finishing this document on time is that we will not get early feedback from the end users and may have to change some of our designs as we are implementing the game. This is not as much of an issue as the other items as we will be adjusting the game anyways as the product develops and the customer desires changes in requirements and functionality. However, it is helpful to figure as much as we can before we begin implementing the game.

  • Management Report (same as last week) ~ 2 hours (individual)

Risk Mitigation Plans

  • Elicitation report
    • Prioritize this deliverable as most important
    • Have Elicitation notes available early-on for the person creating this
    • Consider this assignment to have an earlier due date as other deliverables depend on it
    • Assign a check-in date to ensure that the document is progressing according to the requirements
  • Use cases
    • Create a Google doc for people to create use cases (everyone adding input will increase the amount of work we can accomplish in a small amount of time). Multiple inputs will also ensure that we see a range of different use cases
    • Assign someone to oversee the deliverable and eventually compile all of the Google doc information into the finished 'Use Cases' document
    • Consider this assignment to have an earlier due date as the Game treatment deliverable may benefit from this.
  • Tech assessment
    • Spend time in our next meeting discussing any approaches we are familiar with and any relevant work done that we know of
    • Assign someone to work finish the document
    • Schedule a check-in date to make sure the team is comfortable with the chosen Tech approach
  • Game treatment
    • Assign one person to assemble this document
    • Schedule a check-in date to make sure the person creating this has the information they need to finish the document

Plan for the Week

Remaining deliverables for this phase include game treatment, use cases, tech assessment, prototype, and proposal. Currently, we intend to have all but the prototype and proposal complete this week (as is required). Our goals currently line up with the deliverables, as we will not be creating any longer-term goals until after the customer elicitation. This week's tasks are not inter-dependent, though the elicitation report and use cases will be of use in composing the rest of the deliverables. The remaining tickets will be issued after we divvy up work later today. In our next pre-Tuesday meeting, we will create the detailed work plan and divvy up the work for the following week.


  • Contact with Customer: First Meeting Scheduled for 1/24

Back to Main