For more information or questions reach out to Phase 2 leads:
Client Feedback: We met with the client to gather feedback on the current prototype. We included questions from the entire team. This meeting made it clear that we needed to more accurately communicate the product vision: site purpose, tone, and trust in order to build the foundation for the website. The client reaction gave Design and Content guidance for refinements and also a starting point for Research.
See the recording here: https://zoom.us/rec/share/FazCEkFzGeAnNteaM4j2naMt0SkxGwsXYricSNtY81tjKKLq_8vDey1XDk_mIkGq.X6eOlgrZPcLg1IxJ?startTime=1690993936000&pwd=yj4bCl8iKvwboodwmUlAC2kshcr22wTk
Features/User Stories: We began by working with other teams to choose the most essential user stories and features. We sorted them by prioritized stories, pages on the Site Map and by core features. We assigned user stories to each sprint, creating a user story road map. (MVP Scope)
Research/Testing: Working with research we chose to test and focus initial efforts on building trust, positive first impression and understanding of site purpose. Teams started by completing pages and components that allowed for testing of those areas. We planned to include the functionality of making contact with the Lalich Center, signing up for the newsletter and making a donation as they are central to the client/user needs.
Intake: We explored the process of intake and identified friction points that we could improve upon. (see Intake Process Doc)
Sprint Planning: Our sprint management system relied on the Notion Kanban board to streamline sprint planning and execution. We designated "tickets" for significant project milestones and "tasks" for smaller units of work within each ticket. Additionally, we maintained a separate Kanban board for user stories, which were linked to their respective tickets. At the beginning of each sprint, we reviewed the Kanban board with each team to make sure they remained on course with their tickets and tasks.
MVP/Product Vision: Phase 3 will begin with a live website with an established site purpose, clear mission and tone that reflects the product vision. The essential features: donate, contact, newsletter need to be tested for functionality. This version represents a lean MVP that will be refined and expanded.
Sprint Planning: Although the Kanban board was helpful for sprint planning, we recognized opportunities for improvement in terms of cross-team alignment and providing a more comprehensive project roadmap. This system could be refined through increased collaboration and team engagement. A workshop at the beginning teaching everyone how to use the Kanban board could be helpful. Additionally, we identified the importance of maintaining consistent updates of user stories and acceptance criteria to ensure the accuracy of project documentation.
User Segments: We began to explore features for other user segments that are part of the longer term goal. We began the development of user stories for the professional user segment. (see Feature/User Story Professional) User stories can be expanded in this area. Three features were identified as a starting point and requirements and stories were created for: