Prompt Title: Sprint For Litguide - March MIA 2023

Sure, here is a brief explanation of each point in the Google Sprint week checklist:

Day 1: Understand and Define

• Introduce the problem and set the stage for the Sprint: The facilitator or project lead introduces the challenge or problem the team will be working on during the Sprint.
• Define a clear long-term goal and short-term sprint goal: The team establishes a clear, measurable goal for the Sprint, as well as a broader, long-term goal that the project is working towards.
• Map out the user journey and identify key pain points: The team creates a visual representation of the user journey and identifies specific points where users may experience frustration or difficulty.
• Create a "How Might We" question to guide ideation: The team creates a question or challenge statement that frames the problem in a positive, solution-oriented way.
• Sketch out individual ideas and share with the team: Each team member generates their own ideas for how to solve the problem and shares them with the rest of the group.
• Discuss and combine the best parts of each idea into a "concept storyboard": The team reviews each idea and combines the best parts into a visual storyboard that outlines a potential solution.

Day 2: Diverge

• Review and refine the concept storyboard: The team reviews the concept storyboard created on Day 1 and refines it as needed.
• Sketch individual solutions for the sprint goal: Each team member generates their own ideas for how to solve the sprint goal and shares them with the rest of the group.
• Discuss and prioritize solutions as a group: The team reviews each idea and discusses the pros and cons of each solution, ultimately choosing one to pursue further.
• Decide on one solution to pursue: The team selects one solution to build a prototype for during the Sprint.
• Create a storyboard for the prototype: The team creates a visual storyboard for the solution they've chosen to prototype.
• Identify key features and functionality of the solution: The team identifies the most important features and functionality that the prototype should include.
• Outline a plan for building the prototype: The team outlines a plan for building the prototype, including who will do what and what materials or resources will be needed.

Day 3: Decide

• Review the prototype plan and make any necessary adjustments: The team reviews the prototype plan and makes any necessary adjustments based on feedback or new information.
• Assign roles and responsibilities for building the prototype: The team assigns specific roles and responsibilities to each team member to ensure that the prototype is built efficiently and effectively.
• Begin building the prototype: The team starts building the prototype according to the plan outlined on Day 2.
• Identify any resources or materials needed to build the prototype: The team identifies any resources or materials that are needed to build the prototype and makes sure they are available.
• Conduct a mid-sprint review to check progress and adjust as needed: The team reviews progress and makes any necessary adjustments to the plan based on feedback or unexpected challenges.
• Plan for user testing and feedback: The team plans for how they will test the prototype with users and gather feedback.

Day 4: Prototype

• Complete the prototype: The team completes the prototype according to the plan and specifications outlined on Day 3.
• Make sure it is realistic and functional: The team ensures that the prototype is realistic and functional enough to be tested with users.
• Test the prototype internally to ensure it works as expected: The team tests the prototype internally to ensure that it works as intended and to identify any issues that need to be addressed before user testing.
• Prepare for user testing and feedback: The team prepares to test the prototype with users and gather feedback on how well it meets their needs.

Day 5: Test

• Conduct user testing with real users: The team tests the prototype with real users and gathers feedback on how