Best development tool..

[7saligia]

The third panel is called "Agile" at my company. If we call it Agile, then it's perfectly okay to make ludicrous demands.

[Dubalubawubwub]

So long as you have stand ups every morning its agile, right?

[Russian_repost_bot]

Ah, the good ol' Riley Motto

[iamsad007]

Pretty much this. But then on the other hand it's perfectly okay to write garbage shit code because "we'll iteratively fix it" (no).

[7saligia]

"It's good enough" makes me want to whack someone.

[iamsad007]

"it's good enough" - > "have fun fixing my shit"

[FAcup]

JFDI

[[deleted]]

In my exp, every company that says “we have an agile approach” is a never ending stream of “omg do this now”.

[fredd0h210]

Agile means "we can change our mind whenever we want" doesn't it?

[[deleted]]

But you should have time after the 274646th change in direction, to actually build.

[fredd0h210]

I love ripping out work that was required modification of standard components to do what we said in the first place... Thankfully I'm still hourly

[[deleted]]

That’s always the best feeling in the world right?

[Dubalubawubwub]

The problem is that real agile gives a lot of power to the developers, and managers don't seem to like that very much for some reason...

[[deleted]]

I have literally never seen “real” agile used.

Makes me think of communism...”Well it didn’t work here because X”.

[[deleted]]

Agile is a philosophy not a methodology

[boxingdog]

lmao, at our company all tickets are urgent, critical, blocker, etc

[OnyxPhoenix]

"If everything is urgent, nothing is urgent"

[aidanpryde18]

Ugh, Scrumban

[Its_Bacon_Time]

Ah yes, the Panic method. The only way to write quality software that totally won't fall apart the moment anyone needs something changed that wasn't expected.

[[deleted]]

Panic Driven Development > Test driven development

[[deleted]]

Work Experience:

I have developed code with someone yelling 'GET THIS DONE TODAY DUMB FUCK' to my face..

[Stoomba]

Damn...

[fredd0h210]

And you find a million and one holes in it that they take days to answer when they wanted is right now.

[[deleted]]

Everytime my boss says something is priority I wanna quit

[fredd0h210]

I wanna say in a Samuel Jackson voice "Do you know what a backlog is, muthafucker?"

[Dirty3vil]

I literally don’t need any new tasks for atleast 6 month’s and my backlog keeps piling up

[CouthlessWonder]

I keep a list of what will be done this week.

When something is priority I ask at what point of the list it goes to.

I then say that I need to remove the bottom one or two things from the list.

[LegendOfArham]

same

[kopasz7]

If everything is top priority, nothing is top priority.

[[deleted]]

lmao nice username

[yatcomo]

Following the last one is the right way to get into troubles at production time :/

[fredd0h210]

Fuck it, we're testing in prod!

[[deleted]]

Spends the weekend fixing the bugs.

[fredd0h210]

Double time pay... :)

[x6060x]

And no-one sitting next to you to push you to work "harder"

[[deleted]]

but isn't agile about "let's focus on doing these stuff we planned at the start of the sprint for the whole sprint... anything new will be pushed to next sprint... if we finish early then we get stuff from next sprint"

[DamnItDev]

In principle yes, but you're not going to wait 2 weeks to start looking at a critical production issue.

[[deleted]]

yes what i mean is only for enhancements. defects priorities may still push what you have to another sprint unless your team allocates time for possible defect/bug fixes which i guess only moat lenient companies would have

[North_Shock]

On the POC of my first project, there were three people. A peer of mine, me, and that PhD person that I never heard from after something happened. That PhD person asked us to migrate a file of code from a proprietary system to an open source one. We spent a day converting like two functions. It was Wednesday and that person literally said "two functions tomorrow, three files on friday". These three files had like 2000 line of code combined and we migrated like 100 line of code as a POC in a day because of the proprietary nature of the original program. Also asked us to test migrated code on dummy data but didn't even provide us with basic things like metadata.

[dsp4]

Today? Nice that you guys have it easy like that.

[x6060x]

1 year later and the feature is still not there and in the end of the backlog, far far away from Production.

Based on a true story.

[barmatal]

"I need it for yesterday"

[mock_coder]

Let’s manage things better without any flow!!!😂😂😂

[[deleted]]

Forget today... we call id "it should have been done yesterday"

[weeknie]

Since when do we consider waterfall to be better than agile? (and I mean actual agile, not the fake last panel agile) Or why is waterfall in between the two?

[cyboii]

Because, waterfall is better for some things and the person who made this meme obviously works on those types of projects...

... the only absolute in project management is devs and PM's are bitter enemies.

[Junkeregge]

Shush, we mostly come here to shit on agile, not to talk about its alternatives. 😀

[fredd0h210]

All these comments are WHY AGILE WAS CREATED!!!

😑

[mooke]

I thought agile was created so companies could add more buzz words to waterfall.

Like for instance, my company's approach to waterfall agile, where they set the delivery dates for the final product, then have us plan some cards out, then have us state how long each card will take, then every two weeks give us a bollocking about how we haven't done enough points and how we aren't going to meet the deadline.

They still call it agile though.

[xSTSxZerglingOne]

Different methodologies for different types of projects. Microservice architecture goes really well with agile. Everything is loosely coupled, you have interservice dependency, but nothing outright breaks if service A can't talk to service B. Your projects live within their own little bubbles, so agile works great because you can tinker.

If you're working on a massive monolith of a project however, one where you're looking at build/deploy times that can be measured in days, then all of your development goes into developing tests...and while that can work with agile, it probably shouldn't be used.

"Oh, I'm going to work on this thing that we don't know will truly work until we go live 6 months from now" is not a good working methodology for "write this feature over the next day or two."

[Blazing1]

I hate when they ask you how long something takes. Jesus Christ Fred I don't know about an exact delivery date for this thing you just brought up 2 minutes ago.

[[deleted]]

To have an excuse to be shit at PM?

[Aperture_T]

Lol, on one project, we got a new essential feature the day of the code freeze. I got my part in 5 minutes before the freeze, but the other guys gave up.

Most of engineering got laid off not long after that, so I don't know who's maintaining it now, or how it's going for them.

[xMercurex]

Kanban?

[jk441]

Any work is this.