Feat: Add more checkin form and updates base checkin form questions #167
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ct Owner and Scrum Master Two new form titles, "Sprint Check-in (Product Owner)" and "Sprint Check-in (Scrum Master)", have been added to the FormTitles constant. These titles are used to identify specific forms related to the sprint check-in process for the Product Owner and Scrum Master roles.
Two new files, `checkinformPO.ts` and `checkinformSM.ts`, have been added to the `prisma/seed/forms` directory. These files contain functions to populate the database with check-in forms for the Product Owner and Scrum Master roles respectively. The `populateCheckinFormPO` function creates a check-in form for the Product Owner role. It includes questions about the Product Owner's strengths and allows for additional feedback. The form is associated with the "voyage member" form type. The `populateCheckinFormSM` function creates a check-in form for the Scrum Master role. It includes questions about Scrum training, issue resolution, event management, and allows for additional feedback. The form is also associated with the "voyage member" form type. These forms are added to gather feedback and insights from team members about the Product Owner and Scrum Master roles during sprints. Note: The `FormTitles` constant is imported from the `src/global/constants/formTitles` module to provide consistent and predefined titles for the forms. The addition of these check-in forms enhances the feedback and communication process within the team, allowing for better collaboration and improvement of the Product Owner and Scrum Master roles.
… teams' PO and SM The populateFormsAndResponses function now includes calls to populateCheckinFormPO and populateCheckinFormSM, which are responsible for populating checkin forms specifically for teams with product owners and scrum masters. This allows for more comprehensive form population and better support for different roles within the application.
The description of the checkin form for product owners has been updated to provide more context and guidance to the users. The new description emphasizes the importance of Agile/Scrum in a Voyage and requests feedback on how the users are following it and how their Product Owner and Scrum Master are supporting their team.
…xt and guidance The description of the checkinFormSM has been updated to provide more context and guidance to the users. This will help them understand the purpose of the form and what kind of feedback is expected from them.
…r product owner and scrum master The CHANGELOG.md file has been updated to include an entry for the addition of weekly sprint checkin forms for the product owner and scrum master. This change was made in pull request #167.
JoshuaHinman
previously approved these changes
Jun 19, 2024
cherylli
reviewed
Jun 20, 2024
…better clarity and relevance chore(checkinform.ts): reorganize the order of the questions in the check-in form The check-in form questions and options have been updated to provide clearer and more relevant information. The "How did you communicate with your team this past week?" question has been changed to "Which Scrum events did your team hold in the prior sprint? Please answer 'yes' to any you did even if they were combined in another meeting." to gather more specific information about the team's Scrum events. The options for this question have also been updated to reflect common Scrum events. The "Did you contribute to the project for your team this past week?" question has been changed to "How would you rate your team's progress right now?" to gather information about the team's progress. The options for this question have been updated to reflect different progress levels. The "How did you communicate with your team this past week?" question has been changed to "How did you communicate with your team this past week?" to gather information about the team's communication methods. The options for this question have been updated to reflect different communication methods. The "What topics did your meetings cover this week? (Select all that apply)" question has been changed to "Did you contribute to the project this past week by designing, coding, or testing your teams app?" to gather information about the team's contributions. The options for this question have been updated to reflect different contribution types. The order of the questions in the check-in form has been reorganized for better flow and clarity.
A new question has been added to the check-in form for Product Owners. The question asks if a Product Owner has been assigned to the team. The question is of type "radio" and has three options: "Yes", "No", and "I'm the Product Owner". The question is required to be answered. The question has been added as the first question in the form. Additionally, the order of an existing question has been changed. The question that was previously at order 2 is now at order 3. These changes have been made to improve the check-in form for Product Owners and gather more relevant information during the check-in process.
A new question has been added to the checkinformSM form. The question asks if the team has a Scrum Master. The question is of type "radio" and is required to be answered. The question has three options: "Yes", "No", and "I'm the Scrum Master". This addition enhances the checkinformSM form by gathering information about the presence of a Scrum Master in the team.
…roduct Owner assignment and update order of remaining questions The question about whether a Product Owner has been assigned to the team has been removed as it is handled in the database. The order of the remaining questions has been updated accordingly. This change improves the clarity and relevance of the check-in form for Product Owners.
cherylli
previously approved these changes
Jun 24, 2024
JoshuaHinman
approved these changes
Jun 27, 2024
cherylli
approved these changes
Jun 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR add checkin forms that ask team members for feedback on Product Owners and scrum masters that are on their teams.
checkinformPO.tsandcheckinformSM.ts, have been added to theprisma/seed/formsfolder.Issue link
Fixes # add more checkin forms
Type of change
How Has This Been Tested?
I tested this by:
run
yarn seedto populate the databaserun
yarn studioand look in the form for "Sprint Check-in (Product Owner)" and "Sprint Check-in (Scrum Master)" in the title sectionin the form, the "Sprint Check-in (Product Owner)" form should show
2questions and "Sprint Check-in (Scrum Master)" should show4questions.Checklist: