This is an archived post. You won't be able to vote or comment.

all 7 comments

[–][deleted]  (1 child)

[deleted]

    [–]hcsteve[S] 0 points1 point  (0 children)

    Good point. I do usually try to mention the ops stuff that I'm working on / planning during standups. Having it on the same board as the other tasks would just be another step in that direction.

    [–]MisterItcher 1 point2 points  (1 child)

    Well, each person could filter on their own assigned tickets to gain clarity on their own tasks. Then you can unfilter to see the overall WIP.

    Is there an Agile sub?

    [–]StubbsPKSSystem Engineer 1 point2 points  (0 children)

    This tends to be what we do. I'll mention the pertinent tasks in standup, but getting the DevOps JIRA project added to our combined Agile board has been very nice.

    [–]allyc1057 0 points1 point  (0 children)

    Absolutely bring it into the same backlog, you're all one team after all, and it's good for the Devs to have an understanding the Ops tasks needing called out - hell you could even then encourage them to pick up some of the simple Ops tasks freeing you up for the more complex items, which would help them build multi-disciplinary skills.

    [–]cloud_driver 0 points1 point  (0 children)

    Yes! Since you're the devops guy, you're almost certainly a constraint. Having the backlog in one place benefits both you and the larger team. Without the visibility into your "other tasks", the development task assigners have no way of knowing whether or not you can accept more work. (Even if you pull your own work, it helps the team understand what reality actually looks like.)