Please enable JavaScript.
Coggle requires JavaScript to display documents.
Full scene (Web Page) - Coggle Diagram
Full scene
(Web Page)
pages
log in page
password
User Name
home page
search
log in
Read more
Trindind
Food
Categories
Articles
Fully Verified
Not Verified
Partially Verified
profile page
Author
Reader
Save articles
Change password
Bookmarks
administration
Dashboard
Articles
publish
delete
publish to trinding
Categories
Change password
Categories
Users
Reader
author
administration
back end
data base
my sql
languages
php
python
Sprint 1:project initiation
Spring Retrospective
What went well
Successfully identified and documented all project requirements.
What could be improved:
Better time management for individual tasks within the sprint.
Action items for improvement:
Adopt a requirements management tool like Trello for better tracking.
Sprint Planing
Dialy Scrum
Microsoft Teams
Duration:
6 Days
Potential Risks:
Misalignment between technical design and requirements.
Sprint review
Sprint Goal:
Gather, document, and clarify all project requirements to ensure alignment with stakeholder expectations.
Work completed:
Documented all functional and non-functional requirements
Outcomes:
Established clear goals and expectations for the Full Scene project.
Stakeholder feedback:
Suggested including more examples to clarify technical requirements for future reference.
Sprint 4:User interface design
Processes:
Analysis: Gather requirements for the profile page through discussions with stakeholders
Design: Design the user interface (UI) and user experience (UX) of the profile page
Development: Develop the frontend and backend components of the profile page
Testing:
unit tests
integration tests
system tests
Sprint Review
Feedback and Discussion
Daily Scrum
Raghad:"Designer"
Product Owner: PO
Somyah : "Programmer"
Time Boxing :1week
Sprint Retrospective
Identification of Lessons Learned
Sprint planing
Implementation
Sprint Goal:
Introduce new features such as profile picture uploads, bio sections, and social media integration
Design
Sprint backlog:
Frontend Development
Design
Backend Development
Testing and Quality Assurance
Documentation and Deployment
Analysis:Define functional and non-functional requirements for the profile page based on user needs
Sprint 5: Prepare a partial Presentation
Daily scrum
Somyah : "Programmer"
Raghad:"Designer"
Product Owner: PO
Time Boxing :1week
Sprint Review
Usability Testing Results
Sprint planing
Sprint Backlog:
Design
Frontend Development
Backend Development
Testing and Quality Assurance
Documentation and Deployment
Sprint Goal: Improve user experience and increase engagement.
Implementation
Design
Analysis: Identify key information and features that need to be included in the menu page to meet the needs of both users and stakeholders
Sprint Retrospective
Discuss Challenges and Issues
Processes
Analysis: Gather requirements for the menu page through discussions with stakeholders
Design:Design the user interface (UI) and user experience (UX) of the menu page
Development: Develop the frontend and backend components of the menu page
Testing:
integration tests
unit tests
system tests
frognt end
css
html
JavaScript
design pages
figma
Sprint 2: Analyze requirement and develop a plan
Spring Retrospective
What went well
Effective communication among team members ensured all stakeholders' needs were captured.
What could be improved:
Better collaboration tools could streamline the sharing of requirements and feedback.
Action items for improvement:
Explore project management tools to enhance collaboration and time tracking.
Sprint Planing
Dialy Scrum
Microsoft Teams
Duration:
5 Days
Potential Risks:
Overlooked technical constraints in architecture
Sprint review
Sprint Goal:
Analyze requirements and create a detailed project plan
Work completed:
Documented all functional and non-functional requirements
Outcomes:
Established clear goals and expectations for the Full Scene project.
Stakeholder feedback:
Suggested including more examples to clarify technical requirements for future reference.
Sprint 3: User interface design
Spring Retrospective
What went well
Clear requirements gathered from stakeholders ensured alignment with user needs.
What could be improved:
Minor delays in finalizing color schemes and typography due to differing opinions.
Action items for improvement:
Allocate dedicated time for usability testing in future sprints
Sprint Planing
Dialy Scrum
Microsoft Teams
Duration:
16 Days
Potential Risks:
Delays in integrating designs into code.
Sprint review
Sprint Goal:
Implement key pages such as the homepage, news categorization page, and article view page.
Work completed:
Implement layouts for key pages
Outcomes:
Convert the approved UI designs into functional components using HTML, CSS, and JavaScript
Stakeholder feedback:
Timely feedback loops allowed for rapid iterations and improvements