Create Collab 7hr to MVP Hackathon (Mobile App ft. Flutter)

Meetup is restricting it to 10 attendees but space can support up to 25 + any number of online participants. If you'd like to sign up please join the Discord and introduce yourself. https://discord.gg/cAhtP4qzWG

Learning software development but want more experience collaborating with other professionals?

Join us through the ideation, design, and build process as a manager, designer, or programmer. Gain real-world skills, connect with the tech community, and explore your technical creativity in a non-competitive risk free environment.

All skill levels welcome. Free to all!

Want to participate? Have any questions? Want to join live Flutter learning sessions to prepare? JOIN THE DISCORD!

https://discord.gg/cAhtP4qzWG

EVENT INFORMATION

### Make Sure the Following Technology Works for You:

• GitHub: Ensure repositories are set up, and access permissions are granted.
• IDE (VS Code/Cursor recommended): Verify extensions and plugins (e.g., Prettier, ESLint, etc.) are properly configured.
• Simulator: Set up mobile/desktop simulators for testing (e.g., iOS Simulator, Android Studio, or browser dev tools).
• Discord: Join the event server and ensure roles and channels are configured for teams and announcements.
• Figma: Create an account and verify access to shared design files.

***

### Levels:

Lead:

• Makes final decisions and reviews all work from lower levels.
• Facilitates communication across team roles (design, engineering, product).
• Provides mentorship and ensures adherence to the project’s goals and deadlines.

Mid-Level:

• Can work independently but still needs guidance from managers and leads.
• Responsible for implementing key features, resolving moderately complex issues, and ensuring code quality.
• Acts as a bridge between junior members and leads by assisting with troubleshooting.

Junior:

• Requires more assistance and direct instruction.
• Assigned low-point tickets or tasks (e.g., simple bug fixes, small enhancements).
• Learns through hands-on experience and mentorship from leads and mid-level team members.

***

### Roles:

Project Manager:

• Defines user stories.
• Creates tickets, organizes the project backlog, and maintains documentation.
• Facilitates sprint planning, retrospectives, and standups.
• Ensures alignment between team objectives and the project’s goals.

Design Team:

• Sketches initial low-fidelity wireframes for the product.
• Establishes a reusable design system.
• Develops high-fidelity designs based on wireframes.

Front-End Engineers:

• Builds responsive and accessible interfaces based on designs.
• Ensures UI consistency with the design system.
• Integrates with APIs and implements client-side logic.
• Conducts device testing.

Back-End Engineers:

• Designs and implements APIs and database schemas.
• Develops server-side logic, authentication, and authorization.
• Optimizes for performance and scalability.

DevOps:

• Sets up CI/CD pipelines and ensures deployments are stable.
• Configures and manages development, staging, and production environments.
• Implements automated testing, monitoring, and alert systems.
• Ensures system security and scalability.

***

### Event Schedule:

Introductions and Pitches (10:00 AM - 10:30 AM):

• Get situated, introductions, and role assignments.
• Share ground rules for fostering a supportive and inclusive environment.
• Open-source approach (Apache 2.0 License).
• Collaborative teamwork focus.
• Brief overview of the Kanban system for tasks.
• Pitch 3-minute ideas and vote.

Planning and Design (10:30 AM - 11:30 AM):

• Project Manager: Leads discussion, creates the first user stories, and initializes tickets. Provides a product roadmap and sprint goals.
• Designers: Propose initial UX wireframes and user flows.
• Developers: Diagram the data model and decide on the stack.

Agile Sprint 1 (11:30 AM - 1:30 PM):

• Teams split into roles:
• Project Managers: Create more tickets, facilitate communication, answer questions, and prepare to lead the retro.
• Designers: Define the design system and create component mockups, passing them to managers for ticket creation.
• Developers: Start coding, creating components and boilerplate code.

Lunch Retro (1:30 PM - 2:00 PM):

• Eat and discuss progress.
• Managers reassign tickets as needed.

Agile Sprint 2 (2:00 PM - 5:00 PM):

• Managers and designers continue tasks from Sprint 1.
• Lead Developers: Focus on full-stack connections and integrating components. Conduct testing if time permits.

Final Retro and Cleanup (5:00 PM - 5:30 PM):

• Run the app and demonstrate functionality.
• Document contributions and key takeaways.
• Gather feedback and ensure cleanup of shared spaces and repositories.

We can eat in the library meeting room. Eat breakfast and get coffee before you arrive. Bring your own lunch. There’s also a coffee shop next door that has some lunch food. Snacks will be provided.