Eight points for one team is two points for another team
lloydatkinson.net
Eight points for one team is two points for another team
1–10 of 105 posts
Re: Eight points for one team is two points for another team
#2Whatever Agile was, it's absolute garbage these days. It largely exists to hold developers maximally accountable to the business, at the expense of technical excellence or even maintenance, which can be expressed in its gun-language of Jira tickets and so get ignored. Fuck user stories, fuck sprints, fuck Jira, and fuck product management (a job in which one defines success by getting into one's boss's job as fast as possible, leaving no concern for quality) in general with extreme prejudice.
If the people who started the computing revolution last century knew that their descendants would be attending daily standups and debating "story points", they'd never have done it--in fact, they'd have blocked it from happening in the first place.
Re: Eight points for one team is two points for another team
#31 point per ticket so you can see the jira metrics and try to break down tickets enough that everyone feels they have enough information to get started and understand why the work is valuable.
That's enough.
Re: Eight points for one team is two points for another team
#4Whatever Agile was, it's absolute garbage these days. It largely exists to hold developers maximally accountable to the business, at the expense of technical excellence or even maintenance, which can be expressed in its gun-language of Jira tickets and so get ignored. Fuck user stories, fuck sprints, fuck Jira, and fuck product management (a job in which one defines success by getting into one's boss's job as fast as…
Agile is assuredly garbage but having every development company use the exact same process and terminology is too valuable to give up. It reduces training times, increases tool familiarity, and gets the process out of the way of developers.
Re: Eight points for one team is two points for another team
#5Whatever Agile was, it's absolute garbage these days. It largely exists to hold developers maximally accountable to the business, at the expense of technical excellence or even maintenance, which can be expressed in its gun-language of Jira tickets and so get ignored. Fuck user stories, fuck sprints, fuck Jira, and fuck product management (a job in which one defines success by getting into one's boss's job as fast as…
Agile is assuredly garbage but having every development company use the exact same process and terminology is too valuable to give up. It reduces training times, increases tool familiarity, and gets the process out of the way of developers.
> Agile is assuredly garbage but having every development company use the exact same process and terminology is too valuable to give up.
But...Agile doesn't involve that. Even when the same words are used, they don't have the same meaning, often, and the substantive processes even within vaguely Scrum-ish methodologies vary widely.
Re: Eight points for one team is two points for another team
#6Whatever Agile was, it's absolute garbage these days. It largely exists to hold developers maximally accountable to the business, at the expense of technical excellence or even maintenance, which can be expressed in its gun-language of Jira tickets and so get ignored. Fuck user stories, fuck sprints, fuck Jira, and fuck product management (a job in which one defines success by getting into one's boss's job as fast as…
Agile is assuredly garbage but having every development company use the exact same process and terminology is too valuable to give up. It reduces training times, increases tool familiarity, and gets the process out of the way of developers.
This is actually a good point.
We should be fighting against the standardization of the industry because it allows more competition for wages.
On the other hand, damn near every company seems to only want to hire 'senior' developers who can deliver working software in spite of process, which I assume is somehow related to all the nonobvious process skills being commoditized.
Re: Eight points for one team is two points for another team
#7This is so true. I've been on teams that did 100x work with like 3 engineers. I've also been on teams that do near 0x work with over 10.
What I can confidently state is that you must work the people and then the process to improve anything.
We need to stop adopting things just because other teams use them or because they are an "industry norm".
If we just truly kept true to the original agile manifesto, there would be amazing results everywhere.
Sadly most EMs have the training of a scrum master and never want to work to actually improve their process/discipline. The solution of getting rid of everything is a sound one because at least you can focus on the core agile ideas that make shipping software successful.
Re: Eight points for one team is two points for another team
#8I have never seen a ton of value in the exact number of story points, but they are a good way to have the "30 minute debate" that the author decries. If a task is so unclearly written that the team can't get a rough idea of the complexity in a reasonable amount of time, then it's a signal that the story can't be done or that something needs to change; more knowledge sharing, clearer success criteria for the story/task, etc. I get that the meeting is annoying, but not doing the discussion is just going to hide other problems. The longer you hide problems, the more severe they come. Having no idea what the "done" condition is in any of your tickets is tech debt just like long dev cycle times or code that breaks production every time someone touches it; at the project level instead of the code level.
If the only problem is deciding between a 1 or a 2 though, I'd just remove "1" from the list of options.
Re: Eight points for one team is two points for another team
#9Whatever Agile was, it's absolute garbage these days. It largely exists to hold developers maximally accountable to the business, at the expense of technical excellence or even maintenance, which can be expressed in its gun-language of Jira tickets and so get ignored. Fuck user stories, fuck sprints, fuck Jira, and fuck product management (a job in which one defines success by getting into one's boss's job as fast as…
> Whatever Agile was
Has it changed? The Manifesto[1] is still there, unmodified, to provide thoughts on what you need to consider if you are going to run a software project without managers.
> Fuck user stories, fuck sprints, fuck Jira, and fuck product management
That does not sound like Aglie, especially given that you specifically call out managers, which are incongruent with Agile. The top-down organization where process flows down from management at the top to the developers at the bottom that you speak of is what is colloquially known as 'Waterfall'. This 'Waterfall' organization structure is what many believe the Manifesto was written to counteract, so it is interesting that you’re now calling it Agile.
Re: Eight points for one team is two points for another team
#10Whatever Agile was, it's absolute garbage these days. It largely exists to hold developers maximally accountable to the business, at the expense of technical excellence or even maintenance, which can be expressed in its gun-language of Jira tickets and so get ignored. Fuck user stories, fuck sprints, fuck Jira, and fuck product management (a job in which one defines success by getting into one's boss's job as fast as…
I’ve been feeling a similar sentiment. This sprint some higher up agile coach or whatever their title is has been observing our team and making sure we follow the agile law to a T at the cost of real work efficiency.