Embedded Files
WE ARE ENGINEERS!
WE ARE ENGINEERS!
We know very well what we are doing is not something that an AI will do for us ... but ... we think that myAgileCopilot could help Product and Engineering teams to be more productive and with that productivity you can put your focus in many other things that now you cannot take care: improve the metrics dashboard, do more PR approvals, improve the architecture decisions, ...
In this document we will explain you our proposal to integrate myAgileCopilot to your methodology and make that the teams work in a more productive way.
1. PROJECT PREPARATION
1. PROJECT PREPARATION
Before starting a project your engineering team need to take some decisions. This is something required in any project, and here we will explain you what you need to prepare.
Create Jira Components
Create Jira Components
Before starting to work on a project, there are some tasks that your engineering team needs to complete.
The first task for Senior Engineers. is to define project's tech stack and architecture which can be done using Jira Components feature.
We recommend providing some context to help MyAgileCopilot understand the project better and improve results. This context should include information such as:
The base technology and framework you'll be using.
A list of all the libraries you plan to use such as CSS framework, form validation tools, i18n libraries, ORMs, authentication libraries, query string validation tools, etc. You don't need to describe each library or technology in detail.
An identification of all the dependencies your component will have with other components.
Documentation standards to ensure your component is well-documented and easy to understand.
Testing standards to ensure your component is thoroughly tested and free of bugs.
Be sure to provide comprehensive descriptions, but try to keep them concise and to the point.
PREPARE YOUR RELEASES
PREPARE YOUR RELEASES
Preparing releases is a fundamental step in product management, as it helps define the milestones to be achieved in a given release. We recommend using the description field to provide a clear and concise explanation of your goals for each release.
Generate Your Backlog
Generate Your Backlog
To generate the backlog, you need to go to the left menu in MyAgileCopilot and click on it.
The next step is straightforward: simply click on "Generate backlog from release.
At this point, a background process will start in Jira, which may take more than 5 minutes to complete. You can track the progress of the process by monitoring the creation of epics and user stories in your backlog.
2. ANALYZE YOUR BACKLOG
2. ANALYZE YOUR BACKLOG
Before starting a project, it's essential for your engineering team to make some key decisions. In this section, we will outline what you need to prepare before diving in.
MOVE YOUR STORIES TO TO-DO STATUS
MOVE YOUR STORIES TO TO-DO STATUS
Review and analyze your user stories and epics, and make any necessary modifications. You can also add new user stories that Chat GPT may not have considered.
Once you feel comfortable with the content of an epic, its user stories, and the acceptance criteria, you can move all the stories to the "TO-DO" status, indicating that they are ready for refinement.
Refine all To Do User Stories
Refine all To Do User Stories
To generate the backlog, you need to go to the left menu in MyAgileCopilot and click on it.
The next step is clear: just click "Refine all TO-DO user stories"
After that, a background process will start in Jira, which may take more than 5 minutes. During this process, additional information will be attached to your user stories.
3. ANALYZE TECH APPROACH AND TEST CASES
3. ANALYZE TECH APPROACH AND TEST CASES
Before starting a project your engineering team needs to take some decisions. This is something required in any project, and here we will explain to you what you need to prepare.
MOVE READY SUBTASKS TO TO-DO STATUS
MOVE READY SUBTASKS TO TO-DO STATUS
Analyze the subtasks in your stories. Modify them as necessary and add any development tasks that Chat GPT may not have considered and check that each subtask is linked to a specific component.
Once you are comfortable with the subtask definitions and their coverage of the user story, you can move all the subtasks to the TO-DO status. This indicates that the user story is ready for refinement.
GENERATE CODE AND UNIT TESTS FROM all To-Do SUBTASKS IN ONE CLICK
GENERATE CODE AND UNIT TESTS FROM all To-Do SUBTASKS IN ONE CLICK
To generate the backlog, navigate to the left menu in MyAgileCopilot and click on it.
The next step is to click on "Refine all TO DO Subtasks" located in the Development Assistant.
This will initiate a background process in Jira, which may take more than 5 minutes to complete. Once finished, the subtasks will have additional information attached to them.
4. EXECUTE THE SPRINT
4. EXECUTE THE SPRINT
Before starting a project, your engineering team needs to make some key decisions. These decisions are essential for any successful project, and we will explain what you need to prepare in order to make these decisions.
START THE SPRINT WITH A FUNNY NAME
START THE SPRINT WITH A FUNNY NAME
During sprint planning, immediately after starting the sprint, we suggest that you click the "Set Title and Goal of Current Sprint" button with your entire team present, and read aloud the name and goal of the sprint.
This can be a fun exercise to ensure everyone is aligned and motivated behind the sprint goal.
GENERATE A RETROSPECTIVE REPORT
GENERATE A RETROSPECTIVE REPORT
Before closing your sprint, you can click on the "Analyze current sprint" (Retrospective) button and all team members will receive an email with the information about the sprint.
It makes sense to send this email before closing the sprint, but you can send it at any time.
Google Sites
Report abuse