Skip to content

Objectives

Short Term

Objective:
The short-term objective is to have the software fully documented and an effective stabilization plan implemented. This involves ensuring that the most critical aspects of the software are well-documented, with a clear roadmap for identifying and addressing immediate issues.

Medium Term

Objective:
The medium-term goal is to begin incrementally adding new features. This stage focuses on enhancing the software by implementing functionalities that deliver added value and improve the overall user experience.

Long Term

Objective:
The long-term goal is to establish a sustainable development and production cycle. This includes setting up robust processes and best practices to enable continuous, efficient, and high-quality software development, deployment, and maintenance.

Teams' Contribution to Short Term Objectives

PSP 2

  • MVP Canvas and Product Backlog: Define the MVP and create a product backlog, establishing essential functionalities and prioritizing initial development tasks.
  • Field Data Collection Guide and Report: Develop guides and reports for field data collection, supporting the identification and resolution of critical issues based on real-world feedback.
  • Content Creator Journey Mapping: Map the content creator journey to identify and stabilize key user experience pain points.
  • 2 New Courses: Create two new training courses for content creators to boost user engagement and expand software capabilities.
  • Subject Final Presentation: Prepare a final presentation to showcase the improvements and new features delivered during the development phase.
  • Conecta Event Presentation: Present the project at the event, enabling direct interaction with stakeholders and gathering feedback for continuous improvement.

PSP 5

  • Field Data Collection Questions and Guide: Develop questions and a guide for effective field data collection, ensuring critical feedback is gathered for software stabilization and refinement.
  • MVP Canvas and Product Backlog: Define the MVP and product backlog, prioritizing features aligned with stabilization objectives.
  • Course Impact Indicators: Design dashboards and reports to analyze the impact of courses, aiding system stabilization and integrating feedback.
  • Backlog Compliance Checklist: Prepare a checklist to ensure all deliverables are compliant with the defined backlog, supporting transparency and development alignment.
  • Subject Final Presentation: Summarize progress and showcase newly added functionalities during the development cycle.
  • Conecta Event Presentation: Present the project at the event, collecting valuable feedback from users and stakeholders to further refine development and production cycles.

Software

  • Documentation Update (Beta_v_1.0): Create, structure, and continuously update the core project documentation, ensuring clarity on vision, scope, objectives, deliverables, and project evolution.
  • Field Data Collection Guide: Develop a field data collection guide to support system stabilization and integration of user feedback.
  • Field Data Collection Questions: Design additional questions to measure the impact of new features.
  • Define and detail backlog, requirements, and functional scope: Structure the Product Backlog, User Stories (US), and quality criteria, clearly establishing what will be developed in future phases.
  • Map architecture, database schema, and workflows: Record architectural decisions, design the database schema, and document how the main functionalities will connect in the system.
  • Standardize and centralize information: Consolidate references, links, and tools in a project Wiki, making information easily accessible to all team members.
  • Prepare for future implementation and testing: Refactor, reclassify, and enrich documentation so that future development phases (coding) are agile and based on reliable information.
  • Ensure traceability and transparency: Record authors, dates, and versions for all deliverables, enabling progress tracking and facilitating audits.
  • Egalitarian Event Presentation: Present final outcomes at the event, using feedback to refine development processes and ensure a healthy cycle for future releases.

← Back to Main Page