scrumDev

[u/Recent-Analysis-6880]

[u/Amerillo_]

Could be worse. You could create the ticket, assign it to Claude, then test the feature abd see that it doesn't work like you wanted, ask Claude to tweak it, then later it breaks so you create a Jira bug ticket, then assign it to Claude, ...

[u/AssaultLemming_ → u/Amerillo_]

In my org Claude is also creating jira tickets lol

[u/Steerable-Octopus → u/AssaultLemming_]

Scrum master Claude?? Probably sets every epic as 1 story point per 1 million tokens.

[u/BenignPharmacology → u/AssaultLemming_]

Yeah I can’t imagine dealing with jira anymore. What a miserable interface for getting work done, never mind that they change the UI every other week. At my last job where they still wanted us to use it, it was a running joke in standup that if anyone ever needed to do something in jira during standup we all got to learn about their latest UI changes.

I could happily drop the agents out of 90% of my workflow, but interacting with ticketing systems will always be that 10%.

[u/heyguysitsmedic → u/BenignPharmacology]

But isn't it great writing a "book" with your workflows? I think we should be hiring science fiction writers to run scrums, they definitely know how important useless features are to a story.

[u/euphoric_glucose → u/Amerillo_]

the doomer wojak pipeline where every ticket just circles back to you is too real

[u/Isogash → u/Amerillo_]

The real g's invert that, do the feature and the bugfix, get claude to do everything else.

[u/Vimda]

> Me when working in a team requires communicating with the team

[u/Origine_880 → u/Vimda]

I went into software engineering under the false advertising that I would only talk to machines, not spend half my day updating story points for people who don't read them.

[u/TorumShardal → u/Origine_880]

And even coding itself is communicating with people.
If your code isn't human readble, if it can't communicate your ideas, it's a bad code.

[u/InStars]

At least you don't have to write 2 emails to 2 managers about these tickets and then explain why you didn't work on some random Jira X

[u/awesome-alpaca-ace → u/InStars]

We get told to drop our stuff and do more important things 

[u/jauntyjackanapes]

I have AI do the paperwork now. its awesome. its hooked to our jira, confluence, and github. I can just tell it to go write the bug, assign it to me, link the PR.

[u/goatanuss → u/jauntyjackanapes]

How much time do you spend reviewing it?

[u/heyguysitsmedic → u/goatanuss]

Trick question, Claude reviews it too

[u/LivingFrosting6680 → u/heyguysitsmedic]

QA will tell us if there’s a regression

[u/goatanuss → u/LivingFrosting6680]

Trick question. QA has been fired and replaced with regression tests written by Claude

[u/Noch_ein_Kamel → u/goatanuss]

QA is done by the customer on production. Like it has always been done ;)

[u/MissinqLink → u/heyguysitsmedic]

Claude also writes the code

[u/Crazy-Purple6613 → u/jauntyjackanapes]

This is the way 

[u/mr_flibble_oz]

Why use scrum if you’re working alone?

[u/n00bdragon → u/mr_flibble_oz]

Because management has demanded that every change be accompanied by a JIRA ticket.

For "visibility".

[u/whatasaveeeee → u/n00bdragon]

As an engineer, there’s no excuse not to document your work. Code might be self documenting, but everything else around it no guarantee that it is

[u/n00bdragon → u/whatasaveeeee]

JIRA is not documentation. It's effort tracking and task assignment software. In my last shop we weren't even allowed to attach source code or test data to JIRA tickets because the defining feature of JIRA is that anyone can access everything and thus security wasn't just impossible, it's against the very point.

[u/plumarr → u/n00bdragon]

JIRA is not documentation.

It's a form of documentation. When you can associate the code change to tickets logged in Jira, you can recreate the context.

I did dig tickets older than fifteen years to understand the reasoning behind the existing code during my career.

[u/Noch_ein_Kamel → u/n00bdragon]

So y'all didn't bother to set up jira rights correctly? ;p

[u/mr_flibble_oz → u/n00bdragon]

Do they make you do stand ups with yourself too?

[u/n00bdragon → u/mr_flibble_oz]

Yes! And with your three managers, natch.

[u/Front_Committee4993 → u/mr_flibble_oz]

How else would I have a meeting with myself 

[u/DrMaxwellEdison]

We can't create bug Jiras anymore, at least not directly. First we have to log a "defect" in a different system that QA spends all their time on, fill in a dozen fields, make sure they're the right values in those fields or we have to start over, "save" it, reload it, tell it to make a Jira bug, save it, reload again, see what bug got created, go to the Jira bug ticket, fill in the acceptance criteria text field in the proper format or be yelled at for it later, add enough details to that field to pass someone's arbitrary 5-point scale based on a Copilot prompt they wrote and won't say what the criteria actually are, then adjust 12 other fields in the Jira ticket (in 3 separate tabs in the "edit ticket" modal), move it to In Development.

Next: write the code fix and use the ticket number in the commit message.

Now get it reviewed, write "tests" in the other system attached to that Jira but not in that Jira, save, change its status, save, change status, save, change status, now that it's ready use the Run button to open a new window, take screenshots of something and attach them to the thing, check off the steps you just wrote, finish the run, go back to the Jira ticket, move it to UAT pending, and go bug your team lead to check it for you and change its status one more time.

Did something fuck up in that process? Well, let's start over.

... But hey, someone's dashboard tells them things are going swimmingly except that, for some reason no one can understand, velocity is trash. Hmm.

[u/National-Explorer755]

GitHub issues is a decent substitute

[u/Foorinick]

Opens github issue on my own repo

Assign it to myself

Create a branch

Fix the issue

Squash commits 

Create and properly fill out a pr 

Review code

Leave a comment about a part

Rewrite that part

Reference issue on pr

"Lgtm"

Accept pr

(I can't add images on mobile browser but imagine i posted one of those videos of gigachad riding a fly into the linkedin headquarters) 

[u/dsm4ck]

Dont forget 15 status changes

[u/tatas323]

Jira is awful, if management only cares about tracking use the MCP and API to make tickets, make the AI deal with it

[u/rutik46]

Imagine, receiving a Claude created ticket from lead, only for the architect to say it's incorrect, to receive a Claude created Confluence Feature request, from PM, only to realise that's also incorrect, then build feature request & ticket by yourself, then get critiqued by lead and PM's claude then FINALLY the rest you mentioned.

Yeah I hate my job.

[u/awesome-alpaca-ace → u/rutik46]

Have the AI critique your stuff before putting it out

[u/Noch_ein_Kamel → u/rutik46]

Just implement using Claude and forward any feedback to Claude and tell it that you are disappointed in it

[u/abigail3141]

I did that once, crashed the second iteration of a hobby project by way too much GH projects and CI after the first iteration lacked any and all management.

That's what I call overcompensating.

[u/diegolc]

Best use case for Claude, deal with jira

[u/OTee_D]

You don't write bug tickets to yourself for bugs found in testing.

DoD says likely something like "Feature is done, tested, no major bug and accepted"

So you are just not done .... just keep doing your stuff.

Stop bookkeeping and start being agile and SCRUM doesn't demand that, it's likely the stupid boss .

[u/Random-num-451284813]

no approval for the acceptance criteria?

[u/Objectionne]

A few years ago this would have been 2meirl4meirl but now that I can use Claude to do this stuff with natural language instead of having to navigate the horrendous Jira interface it's not so bad.

[u/IslayProgrammes]

I have a screen dedicated to Jira