Project premise

The project premise is a crucial document that concisely provides the most significant information about the project. It aims not only to present the project's goals, challenges, and technologies but also to aid in its evaluation by supervisors and inspire others to track its progress. The following are the guidelines for the structure of the premise and the specific details that should be included.

Remember: It's your responsibility to ensure that your form is filled out correctly. Only properly completed fields with accessible elements will have an impact. If you make a mistake, everyone will notice :)

1. Project Title
   The title should be short and suggestive, clearly reflecting the main topic or goal of the project. Example: “ZPI Day – Platform for Engineering Project Presentations”

2. Acronym
   Prepare a concise abbreviation that you will use in internal and external communication. E.g., “ZPI Day”.

3. Team Members List
   Provide the full names of all team members to clearly indicate who is participating in the project.

In the form, you must also provide the album numbers of each person.

4. Team Supervisor
   Enter the name of the person supervising the project.

   Do not include academic titles or degrees in the form.

5. Project Logo Prepare a graphic containing the project logo. It should be a square graphic with a minimum size of 150x150 px. Ideally, it should be a vector or raster file with a resolution of at least 150 DPI.

   In the form, provide a direct link to the graphic. You can use tools like Google Drive for this.

   If you lack inspiration, we suggest using free tools such as

   • Canva,
   • Hatchful by Shopify,
   • Looka,
   • FreeLogoDesign,
   • or LogoMakr.

In this section, provide answers to key questions:

• What do you intend to achieve?

An example could be improving the way engineering projects are presented, creating a platform for knowledge exchange and networking.

• What problem does your project solve?

ZPI Day addresses the need for a space for professional presentations of student projects, increasing their visibility and helping establish industry collaborations.

• What are the main business goals?

The goal is to promote innovative solutions, develop students’ presentation skills, and strengthen university-industry collaboration.

• What added value will the project bring?

The added value will be improved presentation efficiency, time savings in the recruitment process, and the promotion of student creativity.

Optionally, you can also include elements such as:

• Key Risks Example: Possible delays in task completion or difficulties in synchronizing team work. We plan to monitor progress and hold regular status meetings to minimize risk.

• Assumptions and Constraints

Example: The project will be completed within eight weeks, assuming the use of open technologies and tools.

The limit is 1500 characters, but you can use simple formatting according to Markdown.

In this section, list the planned technologies and tools to show that the technological process is well thought out. Example technologies:

• HTML/CSS i JavaScript – To create the interactive ZPI Day website.
• Python – To support task automation and data analysis.
• Git – For code version management and team collaboration.
• Canva – For designing promotional materials.

The form will require selecting technologies from a list of nearly 450 items.

Full list of supported technologies:

Present the work plan in the form of a simple list of key stages and milestones. Example:

1. Week 1-2: Preparation of the project premise.
2. Week 3-4: Development of the website design.
3. Week 5-6: Testing and validation of functionalities.
4. Week 7-8: Presentation and evaluation of the project at ZPI Day.

When creating a project roadmap, it's essential to start by clearly defining its goal and outlining the problems it aims to address. Understanding the target audience is crucial for effective planning. Next, the project should be divided into key stages, including research, design, development, testing, and implementation. It's important to set realistic deadlines for each stage while allowing for flexibility to accommodate unforeseen circumstances. While project management tools like Gantt charts can be helpful for visualizing the schedule, they are not specifically designed for creating roadmaps.

A well-prepared roadmap is a visual aid that plays a critical role in organizing work. Its clarity and comprehensibility are vital for the project's success. Remaining flexible and open to adjustments as work progresses is of utmost importance. A thoughtfully crafted roadmap can significantly enhance the efficiency and success of the project.

If you want to learn more about creating a project roadmap, we recommend reading articles on sites such as:

• Smartsheet,
• Productboard,
• Wrike,
• Productplan,
• Savio.

In the form, you must submit a link to an image of the roadmap in 18:7 proportions. Ideally, it should be a vector or raster file with a resolution of at least 150 DPI.

For better visualization, we provide an example project premise. This will help you see how to correctly fill out each section and how to present the project concisely and professionally.

It's essential to craft a strong project premise for the successful execution of ZPI Day. This document serves not only as a technical blueprint but also as a means of communication, enabling stakeholders to understand the team's strategy and pinpoint potential areas for enhancement. Thoroughly preparing this document will not only streamline project implementation but also ensure its effective presentation to a broader audience at the culminating event.