News for hackers. Stuff that matters.
Re:Independence, autonomy, and too many small teams by beaker52 on Wednesday July 29, 2020 @07:26AM (#23985495)
At the company I work at, we're definitely not autonomous. If as a team we have a goal, as a dev, I don't know what it is. We have roadmapped (read: itineraried) work items, basically handed to our team to produce. Devs are resources who are paid for by budget that was earned by committing to said roadmap items delivery.

So what does it look like? Well, as devs, we have specific feature requirements handed to us with little-to-no prior input, we're always behind schedule so we're never afforded the time and space to do things right, it's always "we'll fix it later". We occassionally have some kind of "our competitor is doing this, we have to do this" piece of work that comes in and shifts all of our roadmap items later of course. No one ever stops to ask whether we're having the impact we anticipated, or whether it's even worth keeping the work.

Combine this with a replatforming-through-new-work effort on the go, you've got a slow mutation from the old platform into an even uglier new platform that doesn't get the right effort applied to it.

But hey, we're "agile", we have mission teams, we have two-pizza teams, we're goal oriented. I mean, we say these things, but in reality it's planned out work, with deadlines, delivered by multiple generic teams named after areas of the customer journey that end up being the center of philosophical debate about whether this bit of work lives with _this team_ or _that team_.

Although I don't think the team size or the number of them is necessarily the problem, the article rings true in my experiences - but it's down to culture of the organisation, more than the topology.

Re:Independence, autonomy, and too many small teams by JamesBarney on Wednesday July 29, 2020 @11:33AM (#23987775)
This is why I hate Agile. It's much harder to convince management that they won't be getting a pre-determined set of functionality by a certain date (we will have feature x,y and z developed by October 13th) than to convince a team to stop doing upfront planning and design. So almost every project I've been on that was "Agile" was actually waterfall sans upfront planning and design.
Re:Independence, autonomy, and too many small teams by devtul on Wednesday July 29, 2020 @11:59AM (#23988212)
My understanding about Agile is planning ahead for the next step instead of planning the whole project before starting and then hoping all your assumptions turns out true.

The product owner will create and prioritize the stories in the backlog(plan), the team will discuss and break down a story into actionable and weighted tasks(more planning), then they will fit those tasks into the sprint based on their previous performance(even more planning!)

Re:Independence, autonomy, and too many small teams by undro on Wednesday July 29, 2020 @12:24PM (#23988542)
I think the business concept missing from Agile is investment/ROI and risk. Until budgeting processes are also Agile, everyone will be operating on the idea that "we paid $x to get 'y', and now you aren't giving us 'y'. What the hell?"

Agile works (when it works) because it treats software as a complex system that is best studied and modified through experimentation after accepting a high initial degree of uncertainty (which is slowly reduced through the creation of knowledge). The only comparable things in business terminology are investment and risk. Each iteration (I hate "sprint") needs to be treated as an investment with some risk percentage of failing completely. Until the money is handled that way, business people will keep expecting to get exactly what they think they're paying for, exactly when they feel they were promised they'd get it.

Re:Independence, autonomy, and too many small teams by jkarneges on Wednesday July 29, 2020 @12:34PM (#23988645)
> I hate "sprint"

Me too. It sounds exhausting.

Re:Independence, autonomy, and too many small teams by undro on Wednesday July 29, 2020 @02:29PM (#23990038)
Uncle Bob has the best quote on this subject (in Clean Agile): "A software project is a marathon, and in a marathon you don't want to sprint."
Re:Independence, autonomy, and too many small teams by rch on Wednesday July 29, 2020 @05:59PM (#23992048)
What if the term "sprint" only applied to the final integration, testing, deployment, and validation phases of feature development?
Re:Independence, autonomy, and too many small teams by JamesBarney on Wednesday July 29, 2020 @01:10PM (#23989101)
Right and the fundamental issue is that the next step in agile is an iteration which occurs over 1-4 weeks. But most companies "iterations" are quarterly or yearly. So every quarter or year the business plans and discusses what money they want to spend and what they want to spend it on. And quite reasonably executives are going to want to know what they are purchasing with that budget allocation.
Re:Independence, autonomy, and too many small teams by Beldur on Wednesday July 29, 2020 @04:11PM (#23991035)
I think this is where the "beyond budgeting" movement comes in.

See: https://bbrt.org/what-is-beyond-budgeting/

Re:Independence, autonomy, and too many small teams by cygned on Wednesday July 29, 2020 @02:35PM (#23990103)
The key in communicating is that you give a roadmap, but not put the date into the sand.

Following the idea of the iron triangle, with Agile we fix budget and time, but we keep the scope flexible, however, we estimate a scope and refine that along the way.

If you follow an iterative Agile approach like Scrum, given you know your velocity and you have a backlog in good shape, you can work from one milestone to the other.

Re:Independence, autonomy, and too many small teams by JamesBarney on Wednesday July 29, 2020 @04:19PM (#23991124)
I'm sure some upper management is fine with "we will work on these features and some of them will be done by December."

But in a lot of organizations upper management asks middle management when those features will be delivered so they can plan client communications or internal teams around that.

Re:Independence, autonomy, and too many small teams by d-man on Friday July 31, 2020 @09:01AM (#24008178)
IMO, the core principle of agile is “early feedback means smaller corrective action”. Everything else is just process to achieve that without running afoul of the evil twin “noisy feedback means constant corrections hunting for the solution.”

Agile goes wrong when you don’t get and use good feedback.

You do upfront planning and design, but you only do enough to establish your general course of action. Because good feedback requires context about your goals. If you don’t care where you’re going, then any direction will get you there.

Re:Independence, autonomy, and too many small teams by brainzap on Wednesday July 29, 2020 @03:34PM (#23990712)
who said to skip upfront planning?
Re:Independence, autonomy, and too many small teams by JamesBarney on Wednesday July 29, 2020 @04:16PM (#23991086)
I don't know many agile teams that plan and design and estimate the next 3-6 months of work.

It's my understand that would not be considered agile.

Re:Independence, autonomy, and too many small teams by sitkack on Monday August 03, 2020 @08:40AM (#24036960)
I think I just realized the crux of why some folks dislike agile but weren't able to express it and it has to do with the idea of what-is and what-isn't and how much dominance the "isn't" has over the owner of the belief.

If someone tries to get you to believe something and part of that belief is the active suppression of certain types of thought, and those types of thought are what actually make us intelligent. Then in some regards, agile is trying to make us less intelligent. It might be accidental, it might be unintended, but it is there. Agile attempts to create a social norm where certain thoughts are banned. Yet our ability to anticipate and predict the future is one of our largest defining traits.

There are some aspects of agile that have cult like qualities. I think agile has _improved_ many software teams and projects, esp with how those teams approach planning, but it is still important to be cognizant of thoughts that have been removed from view.

Re:Independence, autonomy, and too many small teams by matsemann on Wednesday July 29, 2020 @09:08AM (#23986209)
> No one ever stops to ask whether we're having the impact we anticipated

"Signs you’re working in a feature factory" sounds relevant to you. https://news.ycombinator.com/item?id=22335738

Re:Independence, autonomy, and too many small teams by delusional on Wednesday July 29, 2020 @01:08PM (#23989074)
I think he knows he's working in a feature factory. What's hard is knowing what you can do to change it.

Where I work, we happen to have a pretty relaxed management. While they always have a ton of deadlines and always push for more work, they largely don't care about the outcome, so you can just ignore it. Every once in a while something will be actually important, but mostly it's just dumb roadmaps for features that don't add value.

What my team has found helpful is to just ignore those fake tasks, and just create the features we actually believe will be valuable. Hopefully we can leverage our outcomes (and the collected data) to convince management that our way is better. Some day.

Re:Independence, autonomy, and too many small teams by cygned on Wednesday July 29, 2020 @08:12AM (#23985746)
> Well, as devs, we have specific feature requirements

> Devs are resources who are paid for by budget that was earned by committing to said roadmap items delivery.

That’s “classical” fixing of all dimensions of the “magic triangle” (scope, budget, time), not agile by any stretch, rather a practice from waterfall management.

I argue that there’s a fourth dimension; quality. How do you see the quality of the teams’ work?

Re:Independence, autonomy, and too many small teams by waheoo on Wednesday July 29, 2020 @08:37AM (#23985946)
I actually prefer a systems lifetime as the 4th dimension.

Quality is just a function of the system time to live being fit against the other three constraints. Scope, budget and time. (I'd actually say time is a subset of budget.)

Re:Independence, autonomy, and too many small teams by WrtCdEvrydy on Wednesday July 29, 2020 @09:15AM (#23986265)
To be honest, most "deadlines" are really just cost boundaries in the first place.

If you're not publicly traded and made an announcement about something going live on a certain date, or have a regulatory body that requires something by a certain date, your deadline is just a cost-cutting measure.

Re:Independence, autonomy, and too many small teams by ric2b on Wednesday July 29, 2020 @01:27PM (#23989337)
Quality is part of scope.

Is it in scope for this to be maintainable? To be stable? To have a nice UX?

Re:Independence, autonomy, and too many small teams by waheoo on Wednesday July 29, 2020 @09:27PM (#23993380)
I guess time to live is scope too but I think it's far too often ignored.

Scope generally determines feature coverage, not quality or how long we expect to use the system.

Re:Independence, autonomy, and too many small teams by pjmorris on Wednesday July 29, 2020 @04:01PM (#23990942)
Johanna Rothman, in 'Manage It', suggests these dimensions to what we usually think of as the 'triangle': features, quality, schedule, cost, team size, team members, and resources (infra, sw, etc...)
Re:Independence, autonomy, and too many small teams by mercer on Wednesday July 29, 2020 @09:41AM (#23986537)
Both your comment and the article sound a bit like the inverse of the problem addressed by "Domain Driven Design".

In the case of the book/approach, the problem is that the IT side doesn't match the business side (in terminology, code organization, etc.). The solution is for IT to become more aligned with the rest of the company.

But in the case of your comment and the article, the mismatch seems to work the other way around. Out of some 'two-pizza methodology' or whatever, the business side now has to split up what should be a single problem/domain in a nonsensical collection of different domains.

I might be entirely off here, though. But if I'm not, is this problem perhaps particular to companies where IT is more in charge than in the types of companies where DDD has been a solution?

Re:Independence, autonomy, and too many small teams by coredog64 on Wednesday July 29, 2020 @11:54AM (#23988136)
I think we work at the same company.
Re:Independence, autonomy, and too many small teams by kmclean on Thursday July 30, 2020 @08:27AM (#23997280)
Wow we must have worked at the same place. I could have written this description. I wonder how common it is.
Re:Independence, autonomy, and too many small teams by jtdev on Wednesday July 29, 2020 @09:43AM (#23986558)
No, this is not “agile”. This is what agile critics think agile is...