black belt tips for jira software
Post on 19-Mar-2017
16.749 Views
Preview:
TRANSCRIPT
NICK PELLOW DEV MANAGER • ATLASSIAN
@NIICK
BRYDIE MCCOY TEAM LEAD • ATLASSIAN
Black belt tipsFor JIRA Software
Photo of the JIRA Software Team
Some assumptions first
You’re in a software teamSoftware is eating the world after all :)
You “get” boardsBoards are just backed by a JQL filter. Even across multiple projects!
You are agileScrum - time based sprints!Kanban - where work flows
Michael Tokar: JIRA Platform
Esther Asenjo: Atlassian Purchasing
Ed Zhang: JIRA Service Desk
Andy Drizen : JIRA Mobile
Esther AsenjoTeam lead on Atlassian Purchasing
Separate estimation from planning
Time to go into detailFocused Identify your blockers
Separate estimation session
Photo of team doing planning. Someone is looking out the window, bored
Epics and quick filters to focus the content
Epic panel
Click to filter
Quick filters
“Story Points” is EMPTY
Status in ("To Do", "Ready for Dev”)
labels = squirtle-squad
Quick filter JQLUnestimated
Not Started
Sub team
Issue detail panel
Customise your board’s issue detail view
Stay in the context of your backlog
Customise to have relevant fields
Edit any field
inline
Photo of the meeting with someone saying that we need a new issue
Create issue
Create issue in epic
Inline issue create
Create issue inline
Epic
Label
Sprint
Version
Component
And more..Project
Assignee
Populates fields based on filters
When stories get too big: Split issue
Right click
The keyboard shortcuts to success
Assign to meAssign
Send to bottomSend to top
+ +
Use the dot
The dot dialog
Photo of team interested and engaged
Michael Tokar: JIRA Platform
Esther Asenjo: Atlassian Purchasing
Ed Zhang: JIRA Service Desk
Andy Drizen : JIRA Mobile
Andy Drizen JIRA Mobile team lead and SCRUM guru!
Estimating is hard!
So keep it fresh!
Planning poker
Some > noneSometimes so hard, plenty of teams skip it entirely…
Can often seem very arbitrary.Hard to calibrate a team on story points
Low engagement == low commitment
Relative estimation
Assign story pointsOrder cardsPlanning prepRough set of stories
for sprint.
Prints the agile cards.
From simplest to most complex
Start with simplest set: 1s
Then next simplest set: 3s, etc etc
Relative estimation
Simple
Complex
New story!
1s
1s
3s
1s
3s
5s
1s
3s5s8s13s?
3s
1s
5s
8s
Relative estimation sessions
:) More involvement
:) Easier to estimateFaster to compare 2 stories than all the stories!
Having tangible cards on a table is fun! No open laptops!
:( Extra data entryAn extra data-entry step afterwards.May lose some of the discussion
Michael Tokar: JIRA Platform
Esther Asenjo: Atlassian Purchasing
Ed Zhang: JIRA Service Desk
Andy Drizen : JIRA Mobile
Michael Tokar Tokes
JIRA Platform team lead
Automated workflow triggers
• Big cool statistic
• 2,569
• Add-Ons in Marketplace
The board is backedby a workflow
The workflow should be flexible
Issues can move toany status
Adding the trigger
Branch created
Pull request merged
Deployment successful
Type your annotation here,the dotted line can be moved and/or re-sized.
Branch created
Pull request merged
Deployment successful
Type your annotation here,the dotted line can be moved and/or re-sized.
Branch naming conventions
feature/JSW-3429_editable_issue_details <prefix>/<issue-key>_<description>
• Big cool statistic
• 2,569
• Add-Ons in Marketplace
Branch created
Pull request merged
Deployment successful
Type your annotation here,the dotted line can be moved and/or re-sized.
Master means customers
Definition of Done includes ‘deployed’
‘Awaiting deployment’ as a holding ground
On pull request merged
Branch created
Pull request merged
Deployment successful
Type your annotation here,the dotted line can be moved and/or re-sized.
Branch created
Pull request merged
Deployment successful
One pull request per issue
The Experiment
Its not perfect:
Each team is different:
Experiment:Introduce slowly, allow for critique
Find the ones that work for you
Perfection is not necessary to make an impact
Michael Tokar: JIRA Platform
Esther Asenjo: Atlassian Purchasing
Ed Zhang: JIRA Service Desk
Andy Drizen : JIRA Mobile
Ed ZhangJIRA Service Desk team lead
Sprints are tough…
Quality of demos
Lack of focus
Lack of progressAre we there yet ?
Many, unrelated streams of work in flight
Bad reflection on the teamBad vibe in the team
Sprint goals
MeasurableDemo drivenDecide as a teamWith input from PM, however team needs buy-in & commitment
During pre-planning, imagine what the demo will be like
Be specific.
Build your measurement first!
Sprint goals
D3 conversion demoable and the dashboard performance improved by 10% on 9 August
S E RV I C E D E S K # S P R I N T G O A L
“ ”
Build measurement first
Applause
Standups!
Traditional Standups…
Justification
Bit of a chore
People centricAll attendees talk…
Are you talking about the most important stuff?
Humans are human - and will want to justify themselves in this setting
Task centric standups
Themed sprints: this release is MoviesSprint goals
Build a standup board
Task-centric standup
Participants only
Less waffle
Leaner“Cut our standup time in half!”
Use this time wisely to discuss what’s important - the actual work!
Only active sprint participants will talk
Automatic workflow triggers
Separate estimation sessions
Epics and quick filters
Our Black Belt tips for JIRA Software
Relative estimation
Sprint goals
Task centric standups
Our Black Belt tips for JIRA Software
Split issue
Create issues inline
Use the dot
Our Black Belt tips for JIRA Software
Applause
Thank you!
BRYDIE MCCOY TEAM LEAD • ATLASSIAN
NICK PELLOW DEV MANAGER • ATLASSIAN
@NIICK
Questions *
* conditions apply
In which version of JIRA was JQL introduced?
4.0
What JQL allows you to find all issues
created in the past 2 weeks?
created > -14d
Find all issues in an open sprint?
Sprint in openSprints()
Select all issues where the label ‘foo’
does NOT exist?
labels != “foo” OR labels is EMPTY
Thank you!
BRYDIE MCCOY TEAM LEAD • ATLASSIAN
NICK PELLOW DEV MANAGER • ATLASSIAN
@NIICK
top related