What type of ticketing system do you want to use and how do you imagine doing your sprint planing? Who should be creating your main engineering tickets? (Keep in mind product strategy will do epics or stories that encompass the feature, this would be dev dependent)
- (Anca) I was thinking we could create a list of features based on an MVP that we could work on in order of importance.
- Ex → before users can login we need to allow them to register first unless we only use OAuth (google signin) to start
Who’s in charge of code reviews and PRs?
- (Anca) For now it can be Frank and I
Should we have a staging environment at this point and how do you want to handle testing? (From an overall sprint version testing or a feature one at a time?)
- (Anca) Frank and I talked about setting up a staging environment with Vercel or CircleCi (CI/CD tools) that would offer live previews that can be shared with QA.
- Currently no preference over feature or sprint QA; maybe leaning toward feature based since it can be well defined.
How do you want to incorporate QA and discussions of bugs during testing (QA will be ran by Product Strategy)
- (Anca) Product Strategy can add items to dev backlog with detail of bug (including screenshots, process to produce bug etc)
- recommend that “QA Feedback” tag be added to the ticket as well as level of urgency to fix bug (can be determined by dev team)
What tech stack are you leaning onto? (UI component library, back end, are we sticking with the Phase 1 suggestions?)
What are the main languages should we focus on?
- (Anca) JS/TS in Next.js framework.
- (Frank) We are also looking into Nodejs for firebase functions REST API
How do you want to handle planning? Tickets created and handled kanban (ie take the first ticket and work)? More agile?
- (Anca) List of tickets can be created based on features and order of importance and team members can take ownership over whatever ticket they think they can tackle.