Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Jira Sprints for an Operations team


To begin with; should a fully operations team be doing 'Sprints'? Or this this just for Dev \ Dev-Ops or project team?

When would an ops team do sprints?

whats the benefits?

Should ops team be having stories?

1 comment

Carlos Garcia Navarro
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jan 09, 2020

Hi Kaizad,

In my experience, although sprints work well for dev teams, or for teams with development tasks, a kanban board fits better the flow of work for Ops teams.  I've tried sprints for Ops /Devops teams sometimes because JIRA offers very interesting sprint reports that summarize what happened during that sprint. In my example I've defined 1 week sprints and named the sprints as the week (W1-TeamA, W2-TeamA, etc.)  But that's a matter of preference. Also in my experience, Ops teams using JIRA use stories, but you can also use tasks or other custom issue types. I wouldn't spend much time (or any time) estimating or assigning points if the tasks are mainly support requests or issues that make your workload unpredictable anyway.


Like kaizad.irani likes this


Log in or Sign up to comment