Proposal Main Page

Table of Content:

Project Management

@Mateusz Stopczański

To effectively develop a game with multiple complex systems (Rasmusson J., 2010), it is essential to establish a robust roadmap that is shared among all organisation members. It is essential to prioritize mutual understanding and communication within the organization, as this can directly impact the quality of the final product. One approach that can be taken is adopting agile methodology and the spiral software development model. Development occurs in short cycles, and prototype features are prepared for testing at the end of each cycle (Boehm B.,1986). This allows for frequent iteration and the ability to reassess elements that do not fit into the overall design. This approach is also commonly seen in software architecture, where a shift towards microservices, independent systems that communicate with each other to create an experience for the user, has replaced the traditionally siloed architecture. (Nadareishvili I., 2019))

Project Schedule

@Mateusz Stopczański

The strategy of using agile methodology and the spiral model has been implemented in the development of Coven of Cards from the early stages. It will continue to create a meaningful and engaging experience for players while meeting the product's artistic, technical, and design requirements.

As an example, the initial design phase, which took place from week 0 to week 10, included the following steps:

  1. During the first three weeks, ideas for original mechanics were developed, considering the thematic context and deriving symbolism.
  2. Physical prototypes were produced for early playtesting and balance from week three onwards.
  3. After establishing the core mechanics (Sabbat, Snowball Morality, Crafting, and Automatization), the product architecture was established to outline the communication scheme between the systems representing features from week 4 to week 7.
  4. An internal GDD was drafted to summarize the efforts and establish a pattern language that could be shared with founding members of the organization and collaborating entities such as 3D artists or sound designers from week 7 to week 10.
  5. Throughout this stage, multiple meetings took place to discuss the product's features and ensure mutual understanding of each element.
  6. Extensive documentation was also produced to represent the product's architecture, which aims to improve the ability to collaborate with entities outside the organization and enhance internal understanding of the technical and economic aspects of the game.

During weeks 11 to 14, the team deconstructed the initial idea to create a conceptual model for each feature. This process involved mapping the intersystem correlations and determining the data required, modified, and produced by each system. The team also developed a plan for future development to ensure that all team members clearly and consistently understood the project and its objectives. This planning process helped the team to understand the key dates and milestones and to work more efficiently by considering the overall project context.

In the future, the development process will continue as follows: