OOGASalad Team Meeting

In your project teams, complete the following activities today:

1. Discuss each person's team experiences and expectations
   • share good and bad past team experiences and what you learned from them
   • share preferences and styles regarding expectations, communication, and debating/conflict
   • share technical preferences regarding internal project deadlines, general design goals, and a GIT workflow
   • choose a time for the next team meeting
2. Discuss your project goals, ideas, and roles to come to consensus as a start to your planning:
• what are your goals for the project?
• what parts of the project do you want to spend more or less effort on (game complexity or variety, viewer, engine, etc.)?
• what extensions to the project would be most interesting/useful?
• what would mark good progress for each Sprint/week?
• summarize the discussion in the file doc/PLANNING.md using Gitlab's Markdown format
• choose a fun/interesting name for your team (this is an excellent team build exercise because, along with agreeing on the genre, it can sometimes be the hardest part of the project :)
3. Complete this exercise to think about describing the design of a very flexible game without actually writing any code
• summarize the discussion in the file DESIGN_EXERCISE.md using Gitlab's Markdown format
4. Create a Team Contract
   • discuss the questions in this worksheet to get started
   • complete this example contract template using Gitlab's Markdown format
   • individually submit this form as your personal agreement to its content
5. Clone the shared team repository to each person's machine and Open the project in IntelliJ to submit your work
6. Team exercises with DUI!

Any time left over can be spent discussing anything useful to get the team started on the project's Design Plan.

Submission

At the end of lab, push your group's markdown files, DESIGN_EXERCISE.md and PLANNING.md, to the doc folder of the master branch of your team's provided oogasalad_teamNN Gitlab repository using the commit message "lab_fluxx_design - everyone's NetIDs".

Discussion

Work together on this smaller exercise that asks you to try to think about the design of a very flexible game without worrying about exactly how it will be implemented. In other words, without writing any actual implementation code, try to explore trade-offs between several designs and describe the best one in enough detail that you can get a handle on how the different rules and goals could be defined using data files.

Team Contract

Now that you have some experience with teams in this course, create your own Team Contract for this project. This document serves as an agreement between all team mates about how the team will operate and has been adopted by many Open Source coding projects.

It should be created collaboratively by thinking about good or bad aspects of team project experiences you have already had, your goals for the course, how the team should communicate, the quality of work everyone wishes to achieve, and the level of group participation and individual accountability everyone feels comfortable with. The process of generating a team contract usually helps jump start a group's efforts to become a team by immediately focusing everyone on a definite task that requires communication and negotiation. Discussing the questions in this worksheet will help you get started.

As a reminder, here is the minimal contract used for previous projects and the individual expectations for course team projects.

Planning

Like most complex software, this very large can be broken down into a set of somewhat self-contained components that are potentially usable on their own but need to work together flexibly to solve the total problem. Keep in mind when your team creates a schedule for the work to be done on various components that some components are more fundamental than others and some can simply be placeholders or have simplified implementations until they need to be fleshed out. Some components will represent the Model, while others will represent the View and/or Controller.

Within each Sprint, you may choose to start some components, make progress on others, and/or finalize the implementation of yet other components. No matter how you choose to distribute the work to be done among the sprints, there should always be something demonstrably improved over the last sprint, and the code at the end of the sprint should always run (i.e., without crashing). In industry, Sprints often end with a demo to stakeholders, and progress is measured by how many features (i.e., things a customer would see as a reason for buying your product) were completed in the Sprint, rather than how much of the data structure was set up.

Try to spend some time now clarifying the order in which the project's features will be completed and who will be taking the lead on each feature.

• There is much flexibility in the specifications and goals for this project so start by listing all features your team wants to complete (called the project's Backlog) and then begin to break those down into one or more tasks (issues) for each Use Case you feel confident could get down during a single Sprint.
• Then take responsibility to complete specific tasks during each Sprint during the rest of the semester. Based on the scope of the project and your design goals, you should be able to prioritize the order of specific tasks so your team has a working app to demo at the end of each Sprint. These tasks should include both a user interface component as well as backend support for each feature and be small enough to verify they can get done during a Sprint. Tasks may also be non-programming oriented, but it should be clear from looking at the distribution of tasks that everyone on the team is accepting responsibility for their fair share.

Discuss your plan by prioritizing the components each team member plans to take primary and secondary responsibility for and a high-level plan of how the team will spend its time to complete the program. Specifically, each person should take responsibility for specific features and use cases they intend to work on during each Sprint. This requires the team to agree on the feature priorities and set a goals for each week's work.