Skip to main content

Rituals

What rituals are there for an agile scrum team?

Each sprint (ours are 3 weeks) has

Scrum aka standup
The goal is 15 minute daily meeting

The common three questions are:
What did you do yesterday?
What will you do today?
What is in your way?

The goal is transparency, everyone on the team should have the opportunity to know what each person is working on, and for the team to all get an idea of where they are on the commitments for the sprint, what issues there are, and use the opportunity to help out other team mates as needed.

Grooming
The goal is to prepare work for upcoming sprints, break epics (large goals that will span sprints) into stories (a deliverable piece of work, as small as you can make it and still assign value). Each story should be assigned a complexity rating, or story point. These are Fibonacci numbers (1, 3, 5, 8). These are complexity not hours!

Retrospective
At the end of the sprint look back
What action items did we have last sprint, did we make progress?
How many points did we complete?
How many did we rollover into this upcoming sprint?
How does this compare to our average?
Did we point these stories correctly?
What stories rolled? Why? How can we prevent this in the future?
What went well and we should keep doing?
What did not go well and we need to improve - and action items to make that happen.

Demos
Show off what you finished to stakeholders, customers, product owners... Anyone you think might like to see it and provide feedback. You can to get feedback as fast as possible to make sure you are going the right direction.

Sprint planning
Figure out how many story points you have done in the past, what your teams availability is, and commit to finish a specific set of stories (preferably in priority order where possible) totalling that number of story points. You need to break these stories into tasks, with estimate hours (if you do that, once a team matures enough you can skip that if there is a regular cadence of tasks completing - but the team needs to get good at sizing the tasks small enough for this first).
Always assume 20% meetings and misc.

Comments

Popular posts from this blog

How do I find the Custom Field ID in Jira Cloud?

So you need to find the Custom Field ID in Jira Cloud. Perhaps you need the ID for a custom field to work on soem code, an API call or a script. How do you find it? You can find the ID in the URL when managing custom fields Jira - Settings - Issues - Fields - Custom Fields https://***.atlassian.net/secure/admin/ViewCustomFields.jspa Select "Edit" on the desired custom field .../admin/EditCustomField!default.jspa?id=12802 There you go! It is that number at the end of the URL Alternately, you can use ScriptRunner Jira - Setttings - Add-ons - Script Runner - Script Console and run the following def issueKey = '***-####' def result = get('/rest/api/2/issue/' + issueKey)         .header('Content-Type', 'application/json')         .asObject(Map) if (result.status == 200){     return result.body.fields } else {     return "Failed to find issue: Status: ${result.status} ${result....

Jira Administration

Some things I have setup in Jira to make life better for me, with the way we work. Use Case 1: You should not close a story when sub tasks are not complete How? Jira - Workflow - Edit Transition Condition, before allowing a story to Status Category Done "All sub-tasks must have one of the following statuses to allow parent issue transitions:" (All done statuses) Use Case 2: You should not close a story until the blocker or impediment is resolved. How? Jira - Workflow - Edit Transition Condition, before allowing a story to Status Category Done "Value Field" The field Flagged will have to be not equal to value '"Impediment"'. Compared as String. Use Case 3: Set resolution when completing an item. Why? If no resolution is set some reports and metrics don't calculate correctly. How? Jira - Workflow - Edit Transition Done Post Function, Status Category = Done JMWE The value(s) of field Resolution of the current...

The dreaded "Clone" in Jira

Jira Cloud Scrum Teams Case: We clone template issues, as our work is repetitive, and get “clone” in the summary and it makes it hard to read. Built-In Jira allows you to remove "Clone" from the story you are cloning, but if you are also copying the sub-tasks there is not the option to remove it. There are ways to turn this off in Jira Server, but I could not find it in Jira cloud. Solution: Jira - Settings - Add-Ons - ScriptRunner - Escalation Service The Escalation Service called: Remove Clone In Summary As this user: (myself) Checked - enabled On this schedule: Every Hour For first 50 results returned by this query:  Project in (pipe) and Summary ~ "CLONE" Will run this code:  // check if issue.fields.summary looks like "CLONE -" def updatedSummary ="" if (issue.fields.summary.startsWith("CLONE -")) {     //if so, modify issue.fields.summary to not suck.     updatedSummary = issue.fields.summar...