Starting a project the right way is essential for its success. We've collected a few principles, guidelines and ideas that help us both achieve the best outcome. Email Vince if you have any questions about any of these. Thanks in advance for agreeing!
1. Workflow
The workflow of this collaboration is designed to be as transparent as possible for optimal results.
1.1 Contact and Project Management
Yummygum expects one clearly designated contact person from your end who will be available weekly and provide constructive input. This person should gather internal feedback beforehand so that input from your team is communicated through a single channel. Within Yummygum, there is 1 project manager and contact person, ensuring the team works efficiently.
Yummygum prefers to collaborate with roles within your team that hold final responsibility and have decision-making authority.
1.2 Meetings, Quick Chats, and Task Management
Meetings will often be held remotely via Google Meet, or in person at Yummygum’s office, for example. Both parties will use Yummygum’s ClickUp platform for communication, planning, and project management tasks. Shared Slack channels can be created for quick, informal questions.
1.3 Feedback
Ideally we aim to receive feedback within 5 working days.
Design feedback is typically given asynchronously via ClickUp by a single designated person from your team and discussed further through video calls or in-person meetings. Final feedback will be entered into ClickUp as tasks to ensure a clear overview of the remaining tasks at all times. Generally speaking we include 2 rounds of feedback per deliverable, unless stated otherwise in the agreement.
Development feedback will primarily be provided asynchronously via ClickUp by one representative from your team and, if needed, in consultation through video calls or physical meetings. Your digital product should be reviewed in a test environment. Resulting feedback can be submitted via a “Bug Form” and will be processed as tasks in ClickUp, ensuring a clear overview of remaining tasks at all times. For Development, we account for one round of feedback on all deliverables; additional rounds can be conducted at an agreed upon hourly rate.
1.4 Post-delivery support from Development
Every project includes a 1-month warranty period applies on critical bugs.
2. Deliverables
A few additional notes on how Yummygum delivers.
2.1 Design Deliverables (Format)
Our design team works in Figma to deliver the mentioned deliverables. The delivery is as an image (JPG/PNG) and you can obtain the Figma files if this is mentioned in the agreement or agreed upon elsewhere.
2.2 Screen & Device Sizes
Designs will be delivered in two sizes, review your agreement if you get both:
Desktop (1440 width)
Mobile (393 width)
Development will deliver fully responsive screens, with these explicitily supported:
Desktops and laptops (resolution 1280 to 1920)
Mobile (resolution starting at 390 width and 500 height)
2.3 Icons, Graphics & Illustrations
Design will utilize professional existing icon sets and illustrations and will not custom design these from scratch, unless explicitily mentioned in the agreement.
2.4 Design System and UI Library
Design created components based on the Atomic Design Principle. Components required for the scope are created including type scales, color scales, states and variants and UI components. There is no additional documentation beyond the setup in Figma.
2.5 Development: Browser Support
By default our deliverables support the curent and 2 preceding versions of the following browsers:
Safari
Chrome (Chromium browsers)
Firefox
Edge
3. Risks
A successful collaboration also depends on mitigating certain risks.
3.1 Team Resources (Likelihood: Low)
Yummygum is a small team, and if 2 or more employees are unable to work (due to illness or other reasons), deadlines may be negatively impacted. In worst-case scenarios, we may need to extend our resources via skilled external parties, though this is not our preferred approach.
3.2 Communication Delays (Likelihood: Low)
All communication and exchange of input/information between parties must be efficient and timely to avoid delays in meeting deadlines.
3.4 Additional Iteration and Feedback Required (Likelihood: Medium)
If more feedback rounds are needed beyond what was agreed for a deliverable (such as a section or page), a new agreement must be made. Failure to reach a clear agreement in time could result in delays.
4. Technical Notes
If Development is part of your project, the following principles are relevant.
4.1 Performance
Additional performance optimization is not included, unless explicitily mentioned in the agreement.
4.2 SEO Best Practices
Basic SEO optimization is included as following:
Implementation of SEO-friendly URLs, meta tags, and alt tags
Adhere the SEO structure the current code base has.
4.3 Accessibility
Basic accessibility is included as following:
Semantic HTML to enhance accessibility
Meet minimum PageSpeed Insights web standards
4.4 Content Management
If content mangement is included, we setup the following:
Integration with Content Management System (CMS) mentioned in agreement
The Client are responsible for any costs arising from the CMS
4.5 Analytics and Tracking
Basic accessibility is included as following:
Integration of Google Analytics or similar script
No specific setup for event tracking
4.6 Hosting
Hosting will be facilitated by The Client
No support for server and hosting is included
4.7 Content
Development will only enter placeholder content into the CMS. Video content will be hosted on CMS or will be embedded via YouTube.