Stakerholder Meeting

Minutes of the Meeting

Mental Model

Product - built and is running Projects - A section of a product, could be a product release with new features Roles - Roles are assigned to a project, this will have a lot of turnover Peoples - People fill up the roles

General Questions

1. What type of communication behavior do you guys want from us? Don't want to seem entitled but it seems like as users, you guys are directly our users?

   • if necessary, try to set aside time (be mindful of their schedule)
   • Staging Website ASAP, have Trello cards or some sort of asynchrnous note

2. who is going to be using this app exactly? is it Bernie? in the long run, any new users? Engineering Manager (Bernie/ Hess) Product Manager (Parth/Elizabeth) Senior Leads (Ronny) Student

A program management system for high staff turnover, high project count.

1. Is this going to obsolete existing resources used? Or will it run in tandem and integrate with them (Trello/Notion)? a) What are those current mostly commonly used resources? b) If listed, what are the most common resources?

   Case by case basis (we will be integrating with Trello and pulling most relevant information) Whereas for AirTable it will be obsoleting the input forms and summary views

2. What's been actually done? See Below.

3. What is a Labs Cycle? Do PVD, approval for PVD, release canvas -> approval -> release canvas -> approval -> etc. a) What are the red flags?

   - Duration of time spent on a product cycle
   

   b) What is the information do they want?

   - Repositories being used
   - Total cost of ownership (Heroku account, Netlify accounts, etc.)
   

   c) What are the metrics are they using to track?

   - a ton (might need to get the exhaustive list after meeting)
   - development history (code reviews, comments, commit history)
   

4. Different views between user (SL vs Engineering Manager vs etc.)? The PPRP model will dictate the permission levels. Students might only be able to see their own project. The structure of the application will be identical or similar across users, but restricted access to data.

5. When you were talking about the product, project, roles, and people does that imply the user experience, in terms of a drop down from a list? Answered above.

6. How would a problem be reflected, what are the most common metrics? Answered above.

7. When you started talking about Docker, this seems to be a bit beyond the scope of just a management system and actually trending towards a platform for development? Or I misinterpreted it?

   • have the ability to terminate a Labs project's deployment at will
   • have the ability to deploy and run Labs projects locally

8. Are there any relevant communications or back-ups that'll make Mission Control contintuation easier?

   • should be in the readme and the documentation

Labs18 Team Questions

1. Technical Research - Branching - Clarify the naming of the feature branches

2. Technical - It says REST API, but I thought it was GraphQL?

3. What's our flexiblity with changing the existing tech stack?

4. What's been actually done?

5. user flows guide isn't filled out?

6. Why did you guys end up choosing Acta? What features did they prefer?

7. What are the details on the architecture? Naming conventions? Linter preferences? What's the best way to get onboarded?

Notes

• a way to take notes in meetings

• what Mission Control doesn't do?

  • not into product management tool, no tasks, no timelines

• no access to production data, will need a staging environment

• look into Code Climate (Mission Control just wants high level data)

Current State of Affairs

• Labs17 used their own authentication, that Labs18 ended up using Acta(sp?)
• Labs18 is currently working on CRUD
• Labs17 used Rest API, Labs18 moved it to GraphQL [Apollo Server 2 (GraphQL Server)]
• Express to check the authentication results
• PRISMA - Object relationship management later
  • hides the database behind a GraphQL interface
  • doesn't want to be a full featured GraphQl server
• Docker