Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
Businesses Technology

Capital One Scraps 1,100 Tech Positions (reuters.com) 29

Consumer lending firm Capital One has cut 1,100 positions in its technology segment, Reuters is reporting citing a source familiar with the matter, a move that comes as its digital transformation matures. From the report: The company plans to eliminate its "Agile" job family and integrate it into existing engineering and product manager roles, it said in a statement. The affected employees have been invited to apply for other roles in the bank. "The Agile role in our Tech organization was critical to our earlier transformation phases but as our organization matured, the natural next step is to integrate agile delivery processes directly into our core engineering practices," the statement said.
This discussion has been archived. No new comments can be posted.

Capital One Scraps 1,100 Tech Positions

Comments Filter:
  • Stick a fork in it (Score:3, Insightful)

    by fermion ( 181285 ) on Friday January 20, 2023 @01:06PM (#63225640) Homepage Journal
    Can we officially declare the agile development fantasy kaput?
    • Nope. Lots of places use Agile and make a lot of money doing it.

      • by chill ( 34294 ) on Friday January 20, 2023 @01:36PM (#63225720) Journal

        You mean consultants?

        • I am a consultant. The employer/client chose this form of cancer. Indian engineers love it because there is a seriously askew problem with their management and engineers valuing process so highly that they don't even care about why a process should exist in the first place.

          Smiles all around if you destroy the product while following the process to the letter. A grades and head wobbles.

          I'm bitter, sorry.

      • I use Agile at work, it is the core process that keeps us on track and productive.

        To be fair, we actually use Kanban, but Agile and Rally are the tools we use. Sort of. Mostly.

      • Drain money doing it.

        Agile is not agile it is scaled cancer

    • by tristang ( 10261166 ) on Friday January 20, 2023 @01:11PM (#63225650)
      I hope so. Never bought into it, it was fluff from the beginning. Been programming since 1995 and it's always a case of developers trying to sound smarter and pretend it's difficult by changing methods or acronyms. KISS. That's all it is. Don't need fancy words or acronyms to explain something in 500 words when it can probably be explained in 15. Just people peacocking.
    • by reanjr ( 588767 ) on Friday January 20, 2023 @01:17PM (#63225666) Homepage

      Agile works pretty well when you don't know what you're building, like at startups. It's a good way to keep the team from going too far in the wrong direction before course correcting. It's also a good way to get outside stakeholders to play their part in steering the work.

      It just sort of falls apart for complex multi-stage development, where no one person understands the code. The cross-functional team composition then needs to be replaced with managed silos with contracts for interacting with each other.

      • Re: (Score:2, Insightful)

        by Darinbob ( 1142669 )

        Startups, even when they succeed, start off with a mess. The whole problem is the rapid rush to develop a product as fast as possible before funding dries up. The process isn't the problem, instead the lack of planning leads to both a bad design as well as sloppy coding. When it's done and the company survives, that dreadful codebase becomes the foundation that is taboo to change and in a decade becomes a technical debt nightmare. Process also isn't necessarily a solution either, except for the process

        • Startups must make short-term development decisions, in order to survive. They need to make money in the short term, or they can't pay their developers and it all falls apart. Truly good software designs that take into account long-term thinking wind up costing WAY too much to build in the short term. And WAY too long. While all that long-term coding is going on, one's competitors are scooping up all the clients with their short-term crap.

          So, the real trick to survival as a young software company is not

          • I find most of it crap. Mostly because startups don't hire good programmers. They hire friends of friends. Or they hire RF engineers, hardware engineers, or subject experts, and make them write code. Some appear to never have worked on code developed in a team environment before, some don't know how source code control works, and few of them in my experience understand how to write sotware that can be maintained. Much of this is just lack of experience.

        • The ultimate delusion is "knowing where you're going before you start". The destination is clear but as you know, it's not the decision to drive from San Francisco to New York that matters, it's getting the car from here to there accounting for road closures, mechanical failures, and the fact that human beings are not robots and have to rest.

          That's why Agile works. It recognizes that there are a gazillion turns and decisions along the way. It provides measurement so we know how fast the car can actually

          • You can do small iterations without Agile. Too many divide the world into Agile versus full blown Waterfall, and if you don't like Agile you must be one of those old stodgy Waterfall guys. Most real places out there are in the middle; a muddled ad-hoc mish mash. Generally a deadline is set and you have toa bide by id no matter how loud you scream you're an Agile house. As the deadline gets closer and closer then negotiations happen to drop unnecessary features. The development team and product managers

      • Agree with parent. Initially, they might have seen success with Agile, and then outgrew what it could offer. But you can be very dysfunctional with any methodology, Agile or otherwise.

        PS: I didn't RTFA

      • Even when your org or processes have matured, it's good to stay on course and not go too far in the wrong direction.

        This is a never-ending goal...

      • Agile works even better when you know what you're building. It's not just about specifications, it's also about the processes that allow teams to reliably estimate the amount of work they complete so they can promise accurate delivery. It provides regular points for introspection and formal ceremonies with specified outputs.
    • Agile rocks (Score:2, Insightful)

      by rsilvergun ( 571051 )
      when it's done right. Instead of waiting for months and months to fix broken things or add a feature people want you do it in a few weeks.

      It also comes with a whole bunch of tools & processes around casework & documentation like user stories and Kanban boards. That really helps structure changes and make sure they're done intelligently. Especially when you're PMs get lost easily...
    • Christ. I knew this comment would be here.

      Agility - this idea of smaller iterations where progress is delivered and demo'd frequently - is going nowhere. It's the most effective tool for reducing the risk of large-scale failure. It ensures a tight feedback loop between product and R&D.

      Yes, dogmatic application of Scrum/Agile methodologies is problematic. Process for the sake of process is not agility. Dogma for the sake of dogma is religion and if folks wanna do religion AND computer programming..

    • To dare to dream. No forks yet. Just a slight nudge.

  • just run of the mill restructuring.
  • by 93 Escort Wagon ( 326346 ) on Friday January 20, 2023 @01:55PM (#63225782)

    Not a paycheck anymore!

  • Looking forward to the headline "Capital One hacked. Millions of customers affected."
  • by DarkOx ( 621550 ) on Friday January 20, 2023 @02:29PM (#63225886) Journal

    With a little inside perspective having done work for (but never worked for ) them, I suspect the broader implication given how they were organized is they are shifting maintenance mode.

    My read of this is, "we are not planning any now digital/online products in the foreseeable future, its going to be just break/fix and cosmetics on our current stuff". I guess upper management thinks there will be something to all this resession talk.

  • by DraconPern ( 521756 ) on Friday January 20, 2023 @02:33PM (#63225908) Homepage
    Agile isn't a tech position.. it's project management professional. e.g. management. 
  • 'natural next step is to integrate agile delivery processes directly into our core engineering practices'

    I'm hoping this means they are disbanding the Agile-dedicated workers and integrating the roles into their general tech population.

    Otherwise, they are doing it wrong. Or did it wrong. Bad Agile is not good either.

  • All it is is an admission that you do not understand the business objectives, workflows and such.

It was kinda like stuffing the wrong card in a computer, when you're stickin' those artificial stimulants in your arm. -- Dion, noted computer scientist

Working...