-
Notifications
You must be signed in to change notification settings - Fork 1
3.1. Project Management
smihman edited this page Nov 17, 2023
·
1 revision
This section outlines the project management methodologies and practices adopted in the development of the Adventure IT Recruitment Game. Our approach ensures effective collaboration, timely delivery, and alignment with project objectives.
- Next.js: A React framework for building user interfaces with server-side rendering.
- TypeScript: A strongly typed programming language that builds on JavaScript.
- TailwindCSS: A utility-first CSS framework for rapidly building custom designs.
- Three.js with React Three Fiber: A JavaScript 3D library with a React renderer for three-dimensional graphics.
- Framer Motion: A library for React to power animations.
- DrizzleORM: An ORM for structured and efficient database queries.
- PostgreSQL: A powerful, open-source object-relational database system.
- NextAuth: A complete open-source authentication solution for Next.js applications.
- We adopted an Agile framework to manage the project, emphasizing flexibility, continuous improvement, and delivering high-quality software.
- Regular sprint planning sessions were conducted to define the goals and tasks for each sprint.
- Tasks were prioritized based on their importance and urgency.
- Daily stand-up meetings helped the team stay aligned on current progress and address any immediate blockers.
- We used Github for tracking tasks, bugs, and user stories.
- A Kanban board was implemented to visualize workflow and progress.
- Discord for team communication.
- Github for version control and code collaboration.
- Github for documenting project details and decisions.
- Regular risk assessment meetings were held to identify potential project risks.
- A risk log was maintained to track and monitor identified risks.
- Proactive strategies were developed for each identified risk.
- Contingency plans were put in place to address any unforeseen issues.
- Key Performance Indicators (KPIs) were established to measure the project's success.
- Regular reports were generated to assess progress against KPIs.
- At the end of each sprint, retrospective meetings were conducted.
- The team discussed what went well, what could be improved, and action items for future sprints.
- Encouraged team members to pursue professional development opportunities.
- Regular feedback sessions were held to support personal and professional growth.