Week #2 #
Detailed Requirements Elaboration #
As a Team Seeker, I want to see only high-quality and vetted projects, so I can avoid wasting time on low-effort posts. Acceptance Criteria: Content moderation, rating system, reporting feature.
As an Idea Founder, I want a space to discuss and refine my idea with potential team members, so I can better evaluate whether to collaborate with them. Acceptance Criteria: Built-in chat or forum for idea discussion.
As a Developer, I want a search tool with advanced filters (e.g., tech stack), so I can find projects efficiently. Acceptance Criteria: Customizable filters, saved search preferences.
As a Recruiter for my project, I want to filter applicants by skills, so I can ensure qualified team members join. Acceptance Criteria: Skill-based filtering.
As someone unsure how to start my idea, I want templates or guides for pitching my idea or recruiting a team, so I can reduce uncertainty. Acceptance Criteria: Step-by-step onboarding, example project pitches, clear and simple instructions for beginners.
As a founder, I want to create a public roadmap with milestones (e.g., MVP by Q3), so potential collaborators see progress. Acceptance Criteria: Timeline editor, Option to mark milestones as “completed.”
As a reader, I want to filter graveyard posts by industry/failure reason (e.g., “ran out of funding,” “poor marketing”), so I find relevant cases. Acceptance Criteria: Filter by tags like “failure reason” or “year.”
As a founder, I want to create a structured project post with required fields (title, description, tech stack, roles needed), so my idea is clear and appealing. Acceptance Criteria: Form includes mandatory fields (title, description, skills needed), preview option before posting.
Idea collaboration survey #
How often do you look for new projects or ideas to work on? #
Where do you typically search for projects or teams to join? #
What’s the biggest pain point when searching for projects/teams? #
Have you ever had an idea you wanted to execute but lacked a team? #
What matters most when recruiting a team for your idea? #
What discourages you from joining startups? #
Which features would be most valuable in finding projects to join? #
Prioritized backlog #
Project specific progress #
Frontend #
New components #
Implemented several new components in the frontend, which are essential for the user interface. These components include:
- Button component
- Input component
- Card component
- Label component
- Skeleton component
- Avatar component
New pages #
Implemented following pages in the frontend:
- Sign Up page
- Sign In page
- Demo main page with skeleton projects
Routing #
Implemented routing in the frontend using Svelte Router. This allows users to navigate between different pages of the application seamlessly
Backend #
Add endpoints for project and add create project model with migrations
Design #
User flows #
Developer #
Founder #
Investor #
Universal user #
Weekly commitments #
Individual contribution of each participant #
Timur Nabiullin: Conducted survey about people experience in finding or creating projects; expanded and added user stories based on the survey
Almaz Andukov: Reorganized the backend structure and implemented API endpoints with Pydantic schemas for project management; added a Project model to represent the corresponding database table; integrated Alembic for database migrations; Updated docker-compose to include a PostgreSQL service and automatically apply migrations on startup ( PR)
Nikita Timofeev:
- Added input, card, input, avatar, skeleton components ( PR)
- Added login page ( PR)
- Added register page ( PR)
- Added root demo page with components present ( PR)
- Add main projects explore skeleton page ( PR)
- Added routing ( PR)
- Developed basic user flow diagrams for key interactions ( PR, Figma link)
Kirill Karsakov: Created an initial backlog with prioritized features/tasks; thought about questions for the survey; wrote the project report
Plan for Next Week #
- Core Feature Implementation:
- Frontend and Backend developers collaborate to implement the highest priority features from the backlog.
- Focus on making at least one end-to-end user journey functional.
- Implement basic error handling.
- User authentication/authorization.
- API Integration: Connect frontend components to backend APIs.
- Data Persistence: Ensure data is being correctly stored and retrieved from the database.
- Internal Demo & Feedback: Conduct an internal team demo of the current state. Identify bugs and areas for immediate improvement.
Confirmation of the code’s operability #
We confirm that the code in the main branch:
- In working condition.
- Run via docker-compose (or another alternative described in the
README.md).