-
Notifications
You must be signed in to change notification settings - Fork 1
Sprint 2 Planning Meeting
Mahfuz Anam edited this page Nov 3, 2024
·
1 revision
- Date: 03 November 2024
- Time: 10:00 PM
- Platform: Google Meet
- Product Owner: Farhan Ahmed Onu
- Scrum Master: Mahfuz Anam
- Team Members: Mohammed Tamjid Islam, Suraiya Mahmuda, Abdullah Al Mamun, Kamrul Hasan Nahid
-
Daily Scrum Meeting Time
We will conduct meeting in every two days 10 pm in google meet. -
Feature Distribution
We discussed and assigned functionalities that need to be implemented in this sprint using TDD approach. -
Coding Conventions, Architectural Pattern & Documentation
- Team members are required to follow our set coding conventions for consistent style and readability.
- Adherence to the agreed architectural pattern is essential for project scalability and maintainability.
- All code must be properly documented in accordance with our guidelines.
-
Testing
-
Unit Testing: Each team member must perform unit tests using
pytest
to ensure code accuracy and robustness. -
Integration Testing: We will use
CircleCI
to automate integration testing across the project.
-
Unit Testing: Each team member must perform unit tests using
-
Time Tracking
- All team members must use Toggl to track their activities.
-
Branch Naming Convention
- For each feature or task, create a new branch in the repository using the following format:
Example:
<functionality>-<DeveloperName>
ApplyForMarksheet-Tamjid
- For each feature or task, create a new branch in the repository using the following format:
-
Commit Message Convention
- We established a standard for commit messages to ensure clarity and consistency. The format for commit messages is:
<tag>: <What did you do>
-
Tags:
-
feature
: Adding a new feature
Example:feature: Added student attendance tracking
-
bug_fix
: Fixing a bug
Example:bug_fix: Resolved issue with login authentication
-
update
: General updates not affecting others' code
Example:update: Modified UI layout for dashboard
-
doc
: Adding documentation
Example:doc: Added API documentation for user management
-
test
: Updating or adding test code
Example:test: Added unit tests for exam scheduling
-
- We established a standard for commit messages to ensure clarity and consistency. The format for commit messages is:
User Story | Assigned Member | Deadline |
---|---|---|
Publish Exam Calendar | Abdullah Al Mamun | 11-11-2024 |
Manage Exam Materials | Kamrul Hasan Nahid | 11-11-2024 |
Manage Answer Scripts | Farhan Ahmed Onu | 11-11-2024 |
Remunerate Teachers | Mahfuz Anam | 11-11-2024 |
Track Students' and Teachers' Attendance During Exam | Mohammed Tamjid Islam | 11-11-2024 |
Approve Application for Physically Disabled and Sick Students | Suraiya Mahmuda | 11-11-2024 |
Each team member is responsible for their respective tasks, adhering to the coding standards, branching conventions, commit message guidelines, and testing practices as agreed.