Allen Holub

@allenholub

I help you build software better & build better software. . Get in touch; my DM is open.

Berkeley, CA
Vrijeme pridruživanja: veljača 2009.

Tweetovi

Blokirali ste korisnika/cu @allenholub

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @allenholub

  1. Prikvačeni tweet
    31. svi 2019.

    Educating a team slows you down for a week or two. Not educating the team slows you down forever. Time spent in learning is never wasted.

    Poništi
  2. prije 16 sati

    "Not realistic" is code for "I can't do that at the fucked up place that I work." Don't assume that your experience is universal.

    Poništi
  3. prije 16 sati

    Zappos has always been one of the more innovative (and radical) experimenters in decentralized organizations with lightweight-to-no traditional management. They're fearless, w/ massive experiments. Some work; some don't. Here's the latest incarnation.

    Poništi
  4. prije 17 sati

    Sometimes, the "change management" organization, particularly if it's a PMO, is the biggest obstacle to change, and should be the first thing to go. They actively try to prevent changes that would make them irrelevant.

    Poništi
  5. prije 17 sati

    If you try to do that incrementally, your director of QA will be fighting tooth and nail to prevent any agility from happening, because they see the writing on the wall for them. It's best to just pull off the band-aid and get it over with. 4/4

    Prikaži ovu nit
    Poništi
  6. prije 17 sati

    But more to the point, adding testers doesn't eliminate the wait times associated with submitting to test, getting back changes, resubmitting to test, etc. The solution is to integrate all testing (and testers) with dev. 3/4

    Prikaži ovu nit
    Poništi
  7. prije 17 sati

    It slows the entire value chain. That particular bottleneck cannot be optimized—you need to eliminate it entirely. Adding enough testers, for example, is usually politically impossible. 2/4

    Prikaži ovu nit
    Poništi
  8. prije 17 sati

    Though it's best to change incrementally, sometimes you just have to rip off the band-aid and deal with the pain. Maybe not for the whole org, but definitely for some parts of it. Take a testing group as a case in point. That group is almost always a huge bottleneck. 1/4

    Prikaži ovu nit
    Poništi
  9. prije 19 sati

    No real change is possible without psychological safety, so start there.

    Poništi
  10. proslijedio/la je Tweet

    NIMBY 2.0: - Buy 50 cheap androids. - Buy a small programmable RC car. - Ensure no more drive through traffic in your neighborhood.

    Prikaži ovu nit
    Poništi
  11. 2. velj

    This thing you call Agile, but isn't, isn't helping you. Hopefully, knowing that will lead to learning about alternatives that actually are agile, and which will help you.

    Poništi
  12. proslijedio/la je Tweet
    2. velj
    Odgovor korisnicima i sljedećem broju korisnika:

    There are some folks who's "professional identity" is "I get to decide." Those folks will always create problems for everyone else. And they do struggle when that identity as the one who gets to decide gets subsumed into a team-oriented, human-centered process.

    Poništi
  13. proslijedio/la je Tweet
    2. velj
    Odgovor korisnicima

    I have been in situations where I've observed organizations attempt to 'install agile' with some sort of scaled framework ... only to find out too late that if you're not already Agile, all you're doing is scaling the existing dysfunction ... regardless of any certified training.

    Poništi
  14. 2. velj

    Agile has nothing at all to do with Sprints, backlogs, fixed roles, meetings, stories, etc. Don't confuse tools (some useful, some not, all contextual) with the thing itself.

    Poništi
  15. 2. velj

    Starting with a customer request is probably a better starting point that something a dev just invents, but in both cases, building that is the beginning of an iterative and collaborative process that will home in on what's actually needed. 3/3

    Prikaži ovu nit
    Poništi
  16. 2. velj

    Anything that can elevate the devs over the customers is suspect to me. Instead of denigrating the customers, I'd rather work with them collaboratively. Fact is, nobody knows exactly what's needed until you build it. 1/

    Prikaži ovu nit
    Poništi
  17. 2. velj

    My problem with "give them what they need, not what they think they need" is that, in the wrong hands, it can lead to an arrogant "I know more what they need than they do" posture. 1/

    Prikaži ovu nit
    Poništi
  18. 2. velj

    I hate the "customers don't know what they want" POV. Of course they do. They want better lives & to get their work done with less pain and more joy. They may not know how best to achieve that, but they certainly know what they want. Collaborate iteratively to figure out the how.

    Poništi
  19. 2. velj
    Poništi
  20. 1. velj

    So, what's the best alternative? Google is creepy. Apple forces me to put everything into Documents. Amazon is too much work. What solution do you use? 3/3

    Prikaži ovu nit
    Poništi
  21. 1. velj

    You can send an email (which they take WEEKS to answer with a canned message that doesn't address the problem). THERE IS NO WAY TO TALK TO ANYBODY ON THE PHONE! The web site is simplified to the level of uselessness. I'm done. 2/3

    Prikaži ovu nit
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·