[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vr / w / wg] [i / ic] [r9k / s4s / vip / qa] [cm / hm / lgbt / y] [3 / aco / adv / an / asp / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / qst / sci / soc / sp / tg / toy / trv / tv / vp / wsg / wsr / x] [Settings] [Search] [Home]
Board
Settings Home
/g/ - Technology



Thread archived.
You cannot reply anymore.



File: c6f.png (106 KB, 280x291)
106 KB
106 KB PNG
>new boss wants us to start using agile development
>>
Kanban development is pretty comfy
>>
>>67081683
Exactly, and agile is awesome.

Problem is what managers call "agile" is usually the exact opposite because they are control freaks who will micromanage everything top-down.
They only use the word because they've heard it's hip.
>>
File: 1513512379158.png (953 KB, 1560x2048)
953 KB
953 KB PNG
> actually enjoying waterfall
what are you some kinda manager?
>>
>>67081710
Literally this.

My place has implemented Agile and the bosses basically have no idea what it means. Say one thing, mean another. Lot's of misinformation being tossed around lol.
>>
find a new job
>>
>>67081570
>I don't know how to break a project down into individual tasks and estimate how long each task will take
Cool story. Most people would be excited they get to add a new valuable buzzword to their resume.
>>
>>67081683

It really is. It's also the best way to demonstrate tangible progress to management without burning out the dev team or boring them by forcing them to work on the same thing forever.

The devil's in the details. If the leads understand that "waterfall with constantly-changing requirements" isn't agile, you should be fine.
>>
The problem with agile is the problem with everything else.
When idiots fuck with it, they fuck it up really badly.
>>
>>67084305
The problem with Agile is it's usually used as a stick to beat developers with it, typically by treating it like waterfall but way faster.
Nobody does Agile right just like nobody does REST right. It's a nebulous concept.
>>
>>67084305
It's very hard to do agile right, especially after a set amount of people working together is reached. That's why a good agile coach is essential to help teams.
>>
>>67084272
>waterfall with constantly-changing requirements
That's not even a thing, you idiot. By definition, waterfall methodology does not have constantly changing requirements. Are you seriously one of those retards who thinks that anything which isn't Agile must be Waterfall?
>>
>>67085413
This. It's eventually used as a Shillelagh to beat your ass with, *every fucking time*.

Just like CMU's "Software Capability Maturity Model" BS before it.

Every fucking day: "What did you do yesterday? What are you doing today? What are you doing tomorrow?"

And a lot of times there's nothing to really report, since any non-Pajeet rated task is going to take a few days at the very least, and perhaps a few weeks or months if it's a big new piece of original code.

Reporting on the glacial pace of typical large-scale, nontrivial software develolment daily makes you sound like a Sperg more often than not.

It'll make you sound like you're making shit up unless you're a real slick talker, more often than not.

I had to tell one Pajeet scrum master to stop making weird faces at me in SCRUM meetings when I reported on the arcane embedded shit I was working on, since he didn't understand a lick of it.

Like I literally had to say, "When you make funny faces at people in the U.S. like that, it makes them think you think they're lying", and so on.
>>
>>67081570
Evidence of beatings from the SCRUM site itself: the word "commit" has been deprecated.

"One of the most controversial updates to the 2011 Scrum Guide has been the removal of the term “commit” in favor of “forecast” in regards to the work selected for a Sprint. We used to say that the Development Team commits to which Product Backlog Items it will deliver by the end of the Sprint. Scrum now encourages the Development Team to forecast which Product Backlog Items it will deliver by the end of the Sprint. It may seem to be a simple wording change, but in fact there are strong reasons behind it, and surely it will have great implications.

When a commitment is broken or not fulfilled, it is usual to expect some sort of accountability, fault, or even compensation. When a forecast doesn’t come true, it is easier to think about matters such as learning from the experience, improvement and - in one word - empiricism, which at the end is what Scrum is about.

It is not uncommon (or unreasonable, frankly) for people on the business side to hear that the Development Team has committed to deliver a list of Product Backlog Items and take it literally. They expect to have every single item delivered at the end of the Sprint, at any price. And, what is even worse, they begin making plans, assumptions and decisions based on this not yet confirmed fact. Then, if the commitment is not fulfilled, they may try to “claim their guarantee”, and ask for liable individuals. This is especially frequent when the business has not yet gotten rid of their former command-and-control, non-agile project management mindset."
>>
>>67087477
Imagine working for a Pajeet
>>
File: 1532454764944.jpg (62 KB, 500x500)
62 KB
62 KB JPG
It's fucked, like someone telling you to draw and then holding the pencil with you.

Better find a new job. :(
>>
>>67087477
>reddit spacing
>>
File: 1523935167960.jpg (61 KB, 590x750)
61 KB
61 KB JPG
>>67087536
It can happen to you, too!
>>
File: 1528936345454.jpg (37 KB, 555x350)
37 KB
37 KB JPG
>>67087540
No, paragraphs, motherfucker.

Do you use them?
>>
>>67087271
It's all shit that iterates, evolves and changes to a greater or lesser degree, whether you admit (incremental/agile/spiral) or deny (waterfall) it.
>>
>>67087555
>almost every sentence is a paragraph by itself
sure, buddy
>>
>>67087580
Waterfall has all the requirements defined before development starts. They do not change until they have been completed. If you have a changing requirements, it is not waterfall. That isn't even up for debate.
>>
>that wasn't real agile
>>
>real agile has never been tried
>>
>>67081570
>”we’re going to use agile!”
>ends up meaning “we don’t want to spend time coming up with requirements, so just work your ass off while we move the goalposts and shovel on feature creep”
>>
DON'T

My company introduced that shit a year ago, since then it's all been downhill. People working on whatever they feel like, shit isn't getting done and suddenly it's 4 weeks until shipping and you've still got an assload of bugs nobody wants to fix.
>>
>>67087896
>brainlet detected
>>
>>67087685
You misunderstand, all projects have changing requirements, even the FDA regulated ones I have worked on, the difference is if the methodology and manglement acknowledge this.

Agile embraces and manages changing requirements by using iterative development with a quick feedback cycle.

Waterfall ignores the changing requirements with no scheduling changes to accommodate the extra work but it still has to happen, so the development team swallows it somehow and the client only gets sight of the product at the end of the 6 months, at which point they realise its not what they want.
>>
>>67088101
No that's my experience of agile development as well.

t. eri
>>
Me and some other guy own a business together. And this is what we do.

Every day everyone writes down the tasks that he has.
Then everyone has to give it a letter. A, B or C.
A is important right now. C is not important.
Then we start working on A.

Its quite simple really.
>>
>>67088214
And everyone knows what the others are up to.
>>
>>67081710
this. it's great when people aren't shitting down your throat, just hope your managers are good
>>
>>67088231
>>67088214
And then you also don't have people saddling each other up with useless work. Because the priorities are clear.
>you want to do me X?
>sure, I'll list it among my C tasks
>>
>>67088214
So that sounds like agile development with sprint cycles of 1 day.
>>
>>67089066
but he didn't mentioned a representative of the company hes developing the software to
>>
>>67081710
>>67083107
Why are managers like this, my dudes? It's like they've never learned any management at all.
>>
>>67089362
Congrats on cracking the code.
>>
>>67081570
No problem. Your boss is a moron who does not know what agile development is, so just make a few pretty charts for him and then keep doing everything the same old way you've been doing it. Duh.
>>
File: KIVaAam.png (442 KB, 599x799)
442 KB
442 KB PNG
OK fine then explain to us what agile should be
and what it shoudn't be
>>
>>67081570
>being a wage slave
i hope the pay is good and you know when to quit OP
>>
File: 1531142000177.png (55 KB, 480x406)
55 KB
55 KB PNG
>More software dev methodologies bullshit because heads want to jerk themselves off
>>
>>67081683
Using it right now
>tfw ignoring the board and fucking around until the boss starts yelling
heh
>>
>>67090383
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

Just that.
>>
SCRUM and agile are different beast. In fact SCRUM no longer uses "agile" in it's defenition. SCRUM can be agile.

Agile is just mantra, manifesto etc. Just attitude and philosophy. Not a set of rules.
Still, the best "agile" process you can have is XP.
>>
>>67089362
Since when is actual management knowledge required for management positions? Every manager I ever knew was just a huge cocksucker that specialized in climbing the corporate ladder.
>>
>>67088150
Not an argument. It's still not waterfall.
>>
>>67091711
Some managers know how to manage. Rare breeds.
>>
>>67091719
because true waterfall is simply not possible.
>>
>>67091711
I guess that explains it. One would think the profit-motive would make companies look for qualified managers, instead of doing that.
>>
>>67087811
>>67087775
Agile is just like communism
>>
File: file.png (39 KB, 250x250)
39 KB
39 KB PNG
>>67083107
>>67081710
What book/online ressource would you recommend to follow and teach agile?
>>
>>67081722
Not him but waterfall is great if you're autistic and like not only structure, but planning for the future. All of my personal projects use waterfall.
>>
>we just have a bunch of tickets to do
>boss assigns tickets at sprint meeting
>finish your tickets early and claim extras for yourself and get gud shit
It's hella comfy but the problem is documentation. It's not consistent and I usually have to find the guy that wrote the code and ask him for more details if I'm adding a feature or something onto something he did for another ticket
>>
>>67091775
>One would think the profit-motive would make companies look for qualified managers

There is no such thing as a degree in management therefore no manager is qualified.
>>
>>67094066
>boss assigns tickets
Why?
Everybody should pick their tickets themselves, or decide as a team.
>>
>>67094203
Well I'm new here so I've been getting easy things that my boss picks out
People volunteer for things they'd like to do, but if someone doesn't have a preference or something really needs to be done that no one volunteers for, it gets assigned




Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.