Deliverable_1
A platform or mobile application is required to centralize and personalize information about future events according to users' interests. Currently, event information is fragmented, making access and organization difficult. The platform will allow personalized searches, send notifications with updated information, and facilitate both ticket purchases and event registration. Additionally, it will integrate social interaction features and generate a QR code that will be sent via email, optimizing the verification process when entering events. The goal is to improve the user experience in planning and attending events of interest.
Scrum is one of the most widely used and effective agile frameworks for software development projects, especially when the scope and requirements of the project may evolve over time. In this case, since the project involves multiple functionalities (personalized searches, notifications, social interaction, QR code generation), Scrum allows for the iterative and flexible management of these developments, delivering value to the end user in short cycles and obtaining continuous feedback.
-
Sprint Planning:
- How it will be used: Before each sprint, the team will conduct a planning session to define which user stories will be included in the sprint. Efforts will be estimated using the story points estimation technique (in Fibonacci), prioritizing based on user value and technical complexity.
- Justification: It allows the team to focus efforts on specific and achievable deliverables within a time frame (usually 2 weeks), ensuring constant and manageable progress.
-
Sprint Review:
- How it will be used: At the end of each sprint, a review will be conducted to showcase what has been completed. Stakeholders will be able to see progress and provide feedback on the product increments.
-
Backlog Refinement:
- How it will be used: Continuous review of the product backlog to ensure that user stories are clear, prioritized, and ready to be worked on in upcoming sprints.
- Justification: Keeps the backlog organized and relevant, facilitating more effective sprint planning.
-
Definition of Done (DoD):
- How it will be used: The team will clearly define what it means for a user story to be "done," including criteria such as complete testing, proper documentation, and QA approval.
| Person | Contact | Role |
|---|---|---|
| Esteban Salazar | [email protected] | Scrum Master / Coordinator |
| Samuel Santamaria | [email protected] | Developer |
| Alejandro Osorno | [email protected] | Developer |
| Juan Pablo Betancourt | [email protected] | Developer |
- User Journey
- User Persona
- Use Cases
- Sequences
- Classes
- Preconceptual Schema
- Information Centralization: The process of consolidating scattered event information in one place to facilitate access and organization.
- Content Personalization: Adapting the information presented to the user according to their preferences and past behaviors to improve the relevance of suggested events.
- Personalized Notifications: Alerts sent to the user about updates, reminders, or new events that match their interests.
- Social Interaction: Features that allow users to share events, connect with other attendees, and participate in related discussions.
- QR Code: A two-dimensional barcode that stores information and is used for quick verification of event entry through scanning.
- User Experience (UX): The quality of the user's interaction with the platform, including ease of use, accessibility, and overall satisfaction.
| Element | Description |
|---|---|
| Description of Technique Used | Scrum Meeting: A sprint planning session was used to define tasks and objectives for the sprint. |
| Evidence of Session Completion | Meeting minutes, screenshots of the Github backlog with prioritized stories, attendee list. |
| Session Participants | All |
| Topics Discussed | Sprint scope definition, user story prioritization, story point estimation, task assignment. |
| Conflicts Presented | Differences in story point estimation among developers. Resolved through a discussion facilitated by the Scrum Master. |
| Session Conclusions | Sprint planned with 5 agreed-upon user stories. An additional meeting was scheduled for mid-sprint backlog refinement. |
| Information Collected | Prioritized user stories, list of assigned tasks, agreement on the definition of done (DoD) for this sprint's stories. |
- Eventbrite
- Description: Eventbrite is a comprehensive event management platform that allows users to explore, create, and promote local events. It offers solutions from event registration to payment processing.
- Differences from WorkSphere: WorkSphere specializes in professional development and networking events, all of which are free for users.
- Whova
- Description: Whova is an event app that facilitates the management of conferences, exhibitions, and meetings. It offers real-time interaction tools such as chats and polls, and allows organizers to customize the event experience.
- Differences from WorkSphere: WorkSphere offers more detailed and personalized analysis, allowing organizers to manage events with greater precision.
- Eventscase
- Description: Eventscase is a complete platform for managing in-person, virtual, and hybrid events. It offers a wide range of tools for planning, promoting, and executing events.
- Differences from WorkSphere: WorkSphere focuses on more personal and face-to-face interaction, prioritizing direct contact and live experience.
- Visioning
- Story Mapping
