Scrum meeting 04 22

Minutes: 79 minutes 0.5 MVP Static Pages - identify mistakes in pages & receive feedback sayaamforall.org (developing home page)

Architecture: Moving javascript bundle to s3

How are you developing application at sayaam for all ? GitHub devsecops 2 regions - North Virginia & Ireland

In webapp javascript stays in one place

2 Goals for test-salaam.netflify.app

• Impress users who visit the page (Inform users about the organization- what we are good at & what we do)
• Receive donations & join the organization

Tasks to do: 0.5 MVP Markups The YouTube video playing at the home page - https://www.youtube.com/watch?v=9CBLVoSSuwM&ab_channel=AlgoWorld

Marketing required at home page:

• A good logo
• Convert into a more interactive page

Toolbar is not clearly visible at the contact page: 

Format for hhttps://deploy-preview-514--test-saayam.netlify.app/ page

Example: https://www.riverislands.com/?utm_source=GoogleRiverIslandsWebsite&utm_medium=SearchAd&utm_campaign=SocialMediaRiverIslands&gad_source=1&gbraid=0AAAAAoZu_EUENFbObUKd61PnAo1gI5shC&gclid=Cj0KCQjw_JzABhC2ARIsAPe3ynp861M7iBOMopC7W-6KdCQbuFkQSpmTPZaTqrxJWOEdjZkR0g04NvQaAtuvEALw_wcB Functionality: Trying to achieve the picture to stop - cruise mode

Prod Meeting Notes:

• Finalize Names
• Match volunteering skills page
• Should be there in our MVP
• Review each text (such as essentials)

Wiki Documentation Process for Each Page Documentation Format: Use a three-column wiki table format:

Serial Number – Unique identifier for each step.

Page Name – The section of the page.

Details / User Story – Description of the control, expected behavior, and use case.

✅ Purpose: Create a clear and complete reference for every page in the application.

Used when filing bugs or analyzing issues, e.g., “In step 2 of ‘Create Help Request’, the system doesn’t behave as expected.”

Wiki should not refer to random text but to specific steps and controls using serial numbers.

Roles & Responsibility: Product Managers and Business Analysts must:

Go through every page and control.

Document how each field should function.

Describe the expected interaction by the end user.

Ensure the user story is clear for each field.