This repository is the collaborative hub for our Software Architecture and Design Project, where we learn and apply principles of software architecture and design to deliver a well-structured solution. The repository includes our Code of Conduct, project deliverables, and other key resources to ensure teamwork and success.
- Team Members: Maahia, Hala
- Product Manager: Evan
- Scrum Master: Mahbouba
- Time spent: Ongoing
This project focuses on implementing software architecture and design principles through teamwork, effective communication, and agile methodologies. The repository contains:
- A detailed Code of Conduct to guide the team in maintaining accountability and professionalism.
- Agile workflows managed by the Scrum Master (Mahbouba).
- Regular documentation updates for transparency and progress tracking.
- Respect and value each team member’s ideas and contributions.
- Foster an inclusive and collaborative environment.
- Communicate clearly and concisely.
- Provide updates on your task progress, blockers, or delays.
- Actively participate in meetings and provide feedback on your tasks.
- If no progress is made, explain why and how you plan to get back on track.
- Falling behind significantly without a valid reason will be reported.
- Be punctual and prepared for meetings.
- If you’re late, treats for the team are on you! -> chocolates for Mahbouba please!
- Absences:
- Missing 2 meetings will result in a warning.
- Missing 3 meetings will be escalated and reported.
- If dissatisfied with a decision (e.g., design features), provide proper reasoning.
- Present your argument to the team with supporting research for discussion.
- Provide constructive, actionable feedback.
- Escalate unresolved conflicts to Mahbouba (Scrum Master) or Evan (Product Manager).
The GitHub repository will serve as the central hub for version control, resources, and documentation.
- Ensure you have a GitHub account.
- Share your GitHub username in the team chat to be added as a collaborator.
The Code of Conduct and related project documentation will be uploaded to the repository for reference.
Regular meetings are critical for progress tracking and alignment.
Vote on your preferred meeting times:
- [In Progress]
Feel free to propose alternative slots if needed.
- Technologies Used
- Contribution Guidelines
- License Information
- GitHub: For version control and collaboration.
- Agile Practices: For sprint planning and task management.
- Markdown: For clear and structured documentation.
Contributions are key to team success:
- Progress Updates: Regularly share updates on your tasks.
- Feedback: Provide constructive suggestions on deliverables.
- Collaboration: Work closely with team members and stay involved in discussions.
MIT License
This repository is licensed under the MIT License, allowing free use, modification, and distribution with proper credit to the authors.
