Open Issues Need Help
View All on GitHubAI Summary: Fix bugs #28 and #29 in the REQ-T2 project to ensure the software is functional and available.
AI Summary: The project lacks evidence of key requirements engineering activities: Lean Inception Workshop prioritization, Epics definition, Lean Inception Workshop with Product Backlog Building (PBB), PBB itself, and Risk/Feasibility Analysis. The task is to provide this missing evidence, likely through documentation of the processes and their outcomes.
AI Summary: Investigate and address the lack of deliverables in the first seven sprints of the REQ-T2 project. This involves analyzing the project's Scrum/XP implementation, identifying the reasons for the delay in the first implementation (Sprint 8), and proposing solutions to improve the process for future sprints. Evidence of the ESW process execution should be provided.
AI Summary: The task involves improving the specifications of two use cases in a software project. The current specifications lack crucial details such as functional requirements (FRs), business rules (BRs), alternative flows (AFs), exception flows (EFs), and proper use case closure. The improvements should include clearly defined FRs, BRs, AFs, and EFs, ensuring complete and accurate use case descriptions.
AI Summary: The task requires completing missing project documentation for the REQ-T2 course, specifically addressing the lack of a schedule, planning, review, and comprehensive evidence of ER and ESW processes. This includes providing detailed documentation of interfaces and demonstrating the completion of all project phases.
AI Summary: Correct and concretize the Behavior Driven Development (BDD) scenarios for a patient management system. The task involves reviewing existing BDDs, identifying inconsistencies, and improving them based on a provided example. The example shows how to add more detail and specificity, including specifying the logged-in user and the expected output format (a table with patient CPF and name).
AI Summary: The task involves refining user stories (US) within a software project for a healthcare system. Several US are currently incorrect or too broad and need to be broken down into smaller, more specific user stories, each with clear requirements (RFs). This includes clarifying the requirements for adding notes and diagnostics, sending appointment reminders, monitoring system health, and generating audit reports.
AI Summary: The project's README indicates an outdated project schedule. The task is to update the project's schedule to reflect the current status of the REQ-T2 project.
AI Summary: Define a comprehensive Definition of Done (DoD) for the REQ-T2 project, clarifying ambiguities around code review processes, testing coverage, documentation requirements, interface validation criteria, bug severity definitions, and the role of the Sprint Review in the DoD process. The goal is to create a clear and actionable DoD that ensures consistent quality and completion criteria for all project deliverables.
AI Summary: Clarify and improve the Definition of Ready (DoR) for user stories. Address ambiguities and vagueness in the current DoR, providing concrete examples and explanations for each point, particularly regarding clarity vs. objectivity, collaborative writing, technical impediments, progressive refinement, and the application of XP, TDD, and CI/CD practices.
AI Summary: Improve the project's requirements engineering process documentation by detailing the techniques used and mapping the activities to the ScrumXP framework. The current documentation is incomplete, lacking descriptions of techniques and ScrumXP activity mappings.
AI Summary: Update the project's schedule and delivery plan to explicitly list the user stories (US) included in each sprint. The current plan lacks this crucial connection between the timeline and the specific features being developed.