Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Engineering process adjustment documentation #33

Closed
neil-iohk opened this issue Dec 10, 2024 · 0 comments · Fixed by #34
Closed

Engineering process adjustment documentation #33

neil-iohk opened this issue Dec 10, 2024 · 0 comments · Fixed by #34
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@neil-iohk
Copy link
Contributor

neil-iohk commented Dec 10, 2024

Task Description:

  • **Add Documentation for the New Review Process **

    • Document the new review process as per the provided slides. Slides
    • If no existing docs exist, create a new file.
    • Include details on draft PR creation, daily architectural reviews, and handling of PR Walkthrough tags.
  • Add Documentation for Backlog Grooming & Developer Meetings

    • Create/update documentation outlining the main developer meetings (Standup, Engineering Discussions, Team Meeting, Sprint Demo, Sprint Retro, Backlog Grooming, etc.).

Acceptance Criteria:

  • New review process documentation is clear, structured, and based on the provided slides.
  • Developer meetings and backlog grooming documents provide a concise, high-level understanding of meeting expectations.
@neil-iohk neil-iohk added the documentation Improvements or additions to documentation label Dec 10, 2024
@neil-iohk neil-iohk moved this from New to 🏗 In progress in Catalyst Dec 11, 2024
@github-project-automation github-project-automation bot moved this from 🏗 In progress to 🔬 Ready For QA in Catalyst Dec 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants