You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Nikola has played a pivotal role in developing our voice assistant feature, making our website more accessible for users with visual impairments or those who prefer audio navigation. His innovative thinking and dedication to enhancing user experience have been invaluable.
@@ -248,8 +253,8 @@ Buttons and form elements have descriptive icons and ARIA labels for better scre
248
253
- Ahmad took the lead in designing and creating this very page. His dedication to highlighting the team's contributions and presenting a cohesive narrative has made the About Us section a central part of our website’s storytelling.
@@ -306,11 +309,72 @@ The development of our project is guided by a structured yet adaptable approach,
306
309
307
310
*<spanstyle="color: blue;">[Back to Content](#content)</span>*
308
311
309
-
### Agile Methodology
312
+
# Agile Methodology
313
+
314
+
## Sprint Process and Team Workflow
315
+
At the beginning of each sprint, our team conducts Sprint Planning to set the course for the upcoming work. This process includes:
316
+
317
+
- Prioritizing the Product Backlog: We ensure the most important tasks are addressed first, focusing on features and improvements that bring the most value to users.
318
+
- Setting Sprint Goals: Clear goals are established, aligned with project milestones, to provide direction and ensure we stay on track.
319
+
- Assigning Tasks: Tasks are distributed based on each team member’s expertise and workload to promote efficiency and collaboration.
320
+
Throughout the sprint, we carefully manage trade-offs between scope, quality, time, and resources. Our aim is to deliver high-quality work while meeting deadlines and user needs. By adopting Agile methodologies, we remain adaptable, focused, and committed to continuous improvement.
321
+
322
+
## Task Prioritization Using MOSCOW
323
+
Tasks are organized using the MOSCOW method, which helps us prioritize and manage our work effectively:
324
+
325
+
- Must Have: Essential features or tasks that are critical for the success of the project and must be completed in the current sprint.
326
+
Should Have: Important tasks that are not essential but should be completed if possible, as they will improve the user experience or functionality.
327
+
- Could Have: Tasks that are nice to have but are not critical. These may be included if there is time available after the must-have and should-have tasks are completed.
328
+
- Won’t Have: Tasks that are not a priority for the current sprint and will be deferred or removed from the current scope.
329
+
This prioritization technique allows us to focus on the most important tasks first, ensuring that we are always addressing the highest-value work.
330
+
331
+
## Team Meetings Summary
332
+
### First Team Meeting:
333
+
334
+
Our first team meeting took place with Vernell, Nicola, and Ben, where we introduced ourselves and discussed the project's objectives. In this session, we:
335
+
336
+
- Planned the project schedule.
337
+
- Decided on a team name. Initially, it was "Access Ok," but after a team vote, it was changed to "Access Granted."
338
+
- Brainstormed ideas for our project’s page. The first suggestion was to create a platform for people with visual impairments, incorporating voice control and vision accessibility. Vernell later proposed expanding the concept to include options for individuals with dyslexia, enhancing the project's inclusivity.
339
+
340
+
### Second Team Meeting:
341
+
342
+
The following day, new team members joined us. During this meeting, we:
343
+
344
+
- Introduced ourselves and shared our skills and availability.
345
+
- Assigned tasks and responsibilities to ensure a smooth workflow and alignment of efforts across the team.
346
+
347
+
### Ongoing Daily Meetings:
348
+
349
+
After the initial meetings, our team continued with two daily sessions:
350
+
351
+
- Sprint Planning Meeting (10:00 AM): During this meeting, we:
352
+
353
+
-- Provide status updates on tasks.
354
+
-- Assign or reassign tasks based on each team member’s progress and workload.
355
+
356
+
- Retrospective Meeting (6:00 PM):
357
+
-- At the retrospective, we reflect on the sprint, evaluate what went well, and identify areas for improvement to ensure smoother workflows and a more efficient development process.
358
+
359
+
### Informal Meetings:
360
+
361
+
Throughout the day, team members can meet informally and make decisions without the presence of the full team or SCRUM lead. These meetings are facilitated through Slack, where status updates on tasks are shared, and decisions are communicated to keep the project board updated.
362
+
363
+
## Kanban Board for Task Management
364
+
To manage and visualize the workflow, we use a Kanban board. This tool helps us track the progress of tasks across different stages of development. Tasks are moved through the following columns:
365
+
366
+
- To Do: Tasks that need to be started.
367
+
- In Progress: Tasks that are currently being worked on.
368
+
- Review: Completed tasks that are being reviewed or tested.
369
+
- Done: Fully completed tasks.
370
+
By using the Kanban board, we ensure that tasks are organized and transparent, making it easy for team members to see the overall project status and ensure that work is progressing smoothly.
371
+
372
+
## MVP Focus and Collaboration
373
+
In the early stages, the team worked towards creating a Minimum Viable Product (MVP). As the team adjusted to working together, we found our balance, rhythm, and flow state. Over time, we transitioned from working individually to collaborating more closely, solving problems together, and helping each other complete tasks effectively.
374
+
375
+
310
376
311
-
Our project follows the Agile methodology, a framework that enables us to tackle the inherent unpredictability of software development through incremental, iterative work cycles, known as sprints. This approach promotes adaptability and allows us to respond quickly to changes, which is crucial in the fast-paced world of software development.
312
377
313
-
At the beginning of each sprint, our team conducts sprint planning to set the course for the upcoming work. This includes prioritizing the product backlog to address the most important tasks first, establishing clear sprint goals aligned with project milestones, and assigning tasks based on expertise and workload. During development, we carefully manage trade-offs between scope, quality, time, and resources to ensure a balance between delivering high-quality work and meeting deadlines. By adopting Agile methodologies, we stay adaptable and focused, ensuring that we meet user needs while striving for excellence.
314
378
315
379
316
380
*<spanstyle="color: blue;">[Back to Content](#content)</span>*
@@ -335,23 +399,33 @@ The Team used slack team channel Canvas to ensure everyone stayed updated on pro
335
399
-## Technologies Used
336
400
337
401
338
-
-[](https://git-scm.com) used for version control. (`git add`, `git commit`, `git push`)
339
-
-[](https://github.com) used for secure online code storage.
340
-
-[](https://gitpod.io) used as a cloud-based IDE for development.
341
-
-[](https://code.visualstudio.com) used as a local IDE for development.
342
-
-[](https://en.wikipedia.org/wiki/HTML) used for the main site content.
343
-
-[](https://en.wikipedia.org/wiki/CSS) used for the main site design and layout.
344
-
-[](https://www.javascript.com) used for user interaction on the site.
345
-
-[](https://getbootstrap.com) used as the front-end CSS framework for modern responsiveness and pre-built components.
346
-
-[](https://fontawesome.com) used for the icons.
347
-
-[](https://chat.openai.com) used to help debug, troubleshoot, and explain things.
| [Git](https://git-scm.com) |Acros website|used for version control.(`git add`, `git commit`, `git push`)
405
+
|[GitHub](https://github.com)||used for secure online code storage.
406
+
|[Gitpod](https://gitpod.io)||used as a cloud-based IDE for development.
407
+
|[VSCode](https://code.visualstudio.com)||used as a local IDE for development.
408
+
|[HTML](https://en.wikipedia.org/wiki/HTML)||used for the main site content.
409
+
|[CSS](https://en.wikipedia.org/wiki/CSS)||used for the main site design and layout.
410
+
|[JavaScript](https://www.javascript.com)||used for user interaction on the site.
411
+
|[YouTube](https://www.youtube.com/)| Acros website | Tutorial for troubleshouting |
412
+
|[Font Awesome](https://fontawesome.com/)| Across website | Inspiration for icons |
413
+
|[Fonts Google](https://fonts.google.com/)| Across website | Font selection |
414
+
|[Coolors](https://coolors.co/)| Across website | Colour palette selection |
415
+
|[W3Schools](https://www.w3schools.com/)| Across website | Various help pages |
416
+
|[Lucid.App](https://lucid.app/documents#/documents?folder_id=home)| Across website | Wireframes creation |
417
+
|[Bootstrap](https://getbootstrap.com/docs/4.3/getting-started/introduction/)| Across website | used as the front-end CSS framework for modern responsiveness and pre-built components. |
418
+
|[Email.js](https://www.emailjs.com/)| Across website | For replying to users contact|
419
+
|[tiny.png](https://tinypng.com/)| Across website | For image convertion |
420
+
|[Bootstrap](https://getbootstrap.com/docs/4.3/getting-started/introduction/)| Across website | Responcivness |
421
+
|[ChatGPT](https://chat.openai.com)| Across website | Used to help debug, troubleshoot, and explain things. |
422
+
|[DeepAI](https://deepai.org/)||Website for creation Avatars
0 commit comments