Commit f343536a authored by Piotr Surowiec's avatar Piotr Surowiec Committed by Xavier Antoviaque

[BB-1819] Replace old sprint report links

parent e0ceb099
......@@ -7,7 +7,7 @@ in sync.
| Day of Sprint | |
|-------------------|----------------------------------------------------------|
| Day 0 (Monday) | Each cell holds a [sprint planning meeting](sprint_planning_agenda.md) to do a final review of the plans for the upcoming sprint, and start the sprint. We use the [Sprint Planning Report](https://tasks.opencraft.com/rest/scriptrunner/latest/custom/showOpenCraftReport) to plan our team's time (that everyone has enough work and nobody will be overcommitted) and to collectively make sure we're staying on track with each client's monthly budget and each epic/project budget. |
| Day 0 (Monday) | Each cell holds a [sprint planning meeting](sprint_planning_agenda.md) to do a final review of the plans for the upcoming sprint, and start the sprint. We use the [Sprints app] to plan our team's time (that everyone has enough work and nobody will be overcommitted) and to collectively make sure we're staying on track with each client's monthly budget and each epic/project budget. |
| Day 0 or 1 | Each developer should review every ticket they have in the sprint, to confirm the due date, plan when/how to approach the work, coordinate with the reviewer for time-sensitive reviews, etc. |
| Days 0-4 | Development - each team member works on their tickets and code reviews. Tasks move from left to right until completion on our JIRA tracker. |
| Day 7 (Monday) | Each cell holds a [mid-sprint meeting](sprint_planning_agenda.md) to ensure everything is going smoothly, and discuss how to help with tasks that are at risk of not being finished by the end of the sprint. |
......@@ -25,8 +25,8 @@ in sync.
than it is to start a whole new task. This reduces context switching, which will help get
things done more quickly. With that said, if you are blocked on a task, move on to another
task, until unblocked.
* Daily, use the Tempo time tracking on the Jira board to record the time spent on each task
and update each ticket being worked on once finished on it for the day. Even just a quick
* Daily, use the Tempo time tracking on the Jira board to record the time spent on each task
and update each ticket being worked on once finished on it for the day. Even just a quick
summary or sentence of where you're at with the task is useful to your reviewer.
### Developer Team
......@@ -35,12 +35,12 @@ in sync.
* Near the end of each sprint, in preparation for the next one, the team
will do an asynchronous "grooming" session. This means that we each
estimate the complexity of each task in the upcoming sprint in terms
of "story points". The person in the cell responsible for the sprint planning is the one who
of "story points". The person in the cell responsible for the sprint planning is the one who
starts this grooming session and invites everyone to it.
* We use story points as a shorthand for agreeing about the complexity of a task.
Story points are meant to be a relatively objective measure of "complexity",
and not necessarily indicate how long it would take any particular developer to do.
* We use a fibonacci scale for story points (please see
* We use a fibonacci scale for story points (please see
[task workflows](task_workflows.md) for more detail on story points for different types
of tasks).
* If anything about the task or the acceptance criteria is unclear,
......@@ -59,7 +59,7 @@ in sync.
this; this is also documented
[in our Jira bot Crafty's code](https://gitlab.com/opencraft/dev/jira-scripts/blob/bf4ea0ae3447fc2ae2098444c2b13a7d2f9e06c3/ReadyForSprintReminder.groovy#L112-124)
* Epic owners should also check the
[Sprint Planning Report](https://tasks.opencraft.com/rest/scriptrunner/latest/custom/showOpenCraftReport)
[Sprints app]
for the upcoming sprint, ensuring that the tasks the team plans to take on
for the upcoming sprint are in line with each client's budget and each
epic's budget.
......@@ -69,19 +69,21 @@ in sync.
* The meeting link is in the calendar invite.
* If you don't see the meetings as recurring events on your calendar, ask Xavier to send
you the invitation.
* After the sprint has been planned and started, it's time to code! If it's your first sprint, your
* After the sprint has been planned and started, it's time to code! If it's your first sprint, your
mentor should have assigned you a task, in addition to the onboarding task.
During the sprint:
* Take a look at the [current sprint board](https://tasks.opencraft.com/secure/RapidBoard.jspa?rapidView=5).
There are filters at the top such as <em>My Issues</em>, <em>My code reviews</em>, and your
There are filters at the top such as <em>My Issues</em>, <em>My code reviews</em>, and your
name, which can be toggled to show only issues relevant to you.
* Drag a task from column to column on the sprint board to update its status as you work through it.
The various statuses/columns are described below. Tasks move from left to right until completion.
* In general, "work from the right" - it's better to finish a task that's already in progress than
it is to start a whole new task. This reduces context switching, which will help get things done
more quickly; it also demonstrates reactivity to upstream reviewers (which pushes them to be
* In general, "work from the right" - it's better to finish a task that's already in progress than
it is to start a whole new task. This reduces context switching, which will help get things done
more quickly; it also demonstrates reactivity to upstream reviewers (which pushes them to be
reactive too).
* Use the Tempo timekeeping system built into our JIRA board for tracking the time you spend on
each task.
[Sprints app]: https://sprints.opencraft.com
......@@ -213,7 +213,7 @@ person:
* Firefighting budget: 7.5% (30h/week for 10 full times, split between two firefighters each sprint)
* Discovery budget: 2.5% (10h/week for 10 full times) - The discovery budget and the discovery duty allocation are two different things. The weekly discovery duty allocation (5h/cell/week) is to be used for new tasks that pop-up in the course of a sprint - it is funded by the discovery budget. Any leftover discovery budget can be used for discovery tasks that are planned in advance.
* Handling the delivery to the client and the verification of the tasks by the clients.
* Update the [sprint commitments spreadsheet](https://docs.google.com/spreadsheets/d/1FXjV9GCugQbX9gS7at2LDDAYvw8A8Z_PrRBG0DaFOho/edit) for your cell during the sprint planning meeting, every week, using the [sprint planning dashboard](https://tasks.opencraft.com/rest/scriptrunner/latest/custom/showOpenCraftReport). When the person handling the sprint management is also leading the sprint planning meeting, this responsibility can be delegated to the person taking notes that sprint.
* Update the [sprint commitments spreadsheet](https://docs.google.com/spreadsheets/d/1FXjV9GCugQbX9gS7at2LDDAYvw8A8Z_PrRBG0DaFOho/edit) for your cell during the sprint planning meeting, every week, using the [Sprints](https://sprints.opencraft.com). When the person handling the sprint management is also leading the sprint planning meeting, this responsibility can be delegated to the person taking notes that sprint.
### Cell manager - Epic planning
......@@ -776,7 +776,7 @@ There are a few exceptions:
We have a few clients with monthly development budgets. For those clients, the assigned client owner
is also responsible for reviewing the monthly budget before and during each sprint planning meeting,
to ensure that we are not going too far above or below the budget. They should refer to the
[Sprint Planning Report](https://tasks.opencraft.com/rest/scriptrunner/latest/custom/showOpenCraftReport)
[Sprints](https://sprints.opencraft.com)
which can monitor and project the status of each budget as of the end of the upcoming sprint.
When we get a new client, or when the client owner changes (or we start working with a new
......
......@@ -69,11 +69,11 @@ ensure that it helps your sprint and stress levels.
## Improve task estimates
If you're using the [Sprint planning report] to avoid overcommitting, but you find that you're consistently logging more
If you're using the [Sprints app] to avoid overcommitting, but you find that you're consistently logging more
hours than you initially estimated, then you might need to work on improving your task estimates.
One of the common traps when taking on a task is to "estimate" it by looking at the hours you have remaining on the
[Sprint planning report], and using that to determine how much time the task will take. This consistently skews
[Sprints app], and using that to determine how much time the task will take. This consistently skews
estimates into being too small, so don't do it! Please evaluate each task independently, based on time required to
achieve its acceptance criteria, not how much time you have left to do it.
......@@ -160,7 +160,7 @@ Here are some of the ways to reduce and eliminate spillovers.
1. Track your own spillovers and reasons.<br />
This makes it possible to identify the most common reasons for spillover, and to figure out what you need to work on.
1. Improve your task estimates.<br />
If you're consistently logging time over your tasks' Initial Estimate, then this makes the [Sprint planning report]
If you're consistently logging time over your tasks' Initial Estimate, then this makes the [Sprints app]
a much less useful tool. See [Improve task estimates](#improve-task-estimates) for ideas and tips.
1. Take on tasks which are related to reduce context switching.<br />
If there are several related tasks in the upcoming sprint, try to take on as many as possible to reduce context
......@@ -188,7 +188,7 @@ Here are some of the ways to reduce and eliminate spillovers.
[Are you feeling productive?]: https://docs.google.com/document/d/1aIle4F5itEcmPY0xKg3zXB0Yo8ySQ6KLosPmFCm_2cY/edit?usp=sharing
[jira own tasks above estimate]: https://tasks.opencraft.com/issues/?filter=-1&jql=assignee%20%3D%20currentUser()%20AND%20issueFunction%20in%20expression(%22%22%2C%22timeoriginalestimate%20%3C%20timespent%22)%20order%20by%20updated%20DESC
[Sprint Planning Report]: https://tasks.opencraft.com/rest/scriptrunner/latest/custom/showOpenCraftReport
[Sprints app]: https://sprints.opencraft.com
## Tips and tricks
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment