3 ms·
Throw out the tools you’re using I'd like to underline this about a thousand times. (disclaimer: I teach agile to teams) What I see over and over again is fol
by DanielBMarkham 16y ago
Throw out the tools you’re using
I'd like to underline this about a thousand times.
(disclaimer: I teach agile to teams) What I see over and over again is folks picking up agile and a) getting too religious about it, and b) immediately making it 5 zillion times more complicated than it has to be. Usually with the use of tools (but creative minds have been known to create manual monstrosities)
If I could eliminate people who already know everything (either pro or con) and folks who for some reason want to complicate everything? Life would be a lot easier for agile teams.
I saw a guy once -- no shit -- that had created a 20-tab spreadsheet to "do" agile. Each sprint close he forced the team to sit down while he went through each item on a projector. Their backlog had 600 items in it. It was like taking a big dump truck with manure and just covering the team in it. I insisted they move to a physical storyboard, and when I checked up with them a few weeks later they had this storyboard that looked like the wiring diagram for a 57 Chevy. Colors and lines and tags and color-coded cards.
Agile is easy, but it's possible to screw it up if you keep trying hard enough. Start simple and then add what you need.
- aminuit 16y ago(disclaimer: Agile consultants ruined the software group I work in.) Making good software is hard, and anyone claiming to have a magical process that guarantees good software is selling snake oil. I can appreciate your wanting to make a buck, but would also seriously appreciate it if you could find some other industry besides software development to go screw up.
- SkyMarshal 16y agoConvicting one for the sins of others?
- aminuit 16y agoEver notice that virtually all Agile success stories are written by Agile consultants and not by developers? Ever notice that nobody actually claims to have built anything from scratch with Agile? The stories all read the same. Product has already been built. Developers stuck bike shedding over some piddly detail, when lo and behold the Agile consultant arrives to cut through the Gordian knot by placing the developers on a strict regimen of myopic thinking and inattention to detail. Agile is bullshit.
- jessor 16y agoI actually know a startup with a team of about 9 people who are doing just fine with agile (since the beginning). Could you elaborate with some more substantial criticism?
- aminuit 16y agoI worked at a cool little company where we built a useful product. We just built it. We didn't use waterfall, agile, or any real process. We just made sure to communicate and only hired people with good judgement and critical thinking skills. A big (very big) company decided they liked our product and bought the company. After acquisition, our new overlords decided that our process, i.e. using our brains, wasn't compliant with whatever standards they had for development. In came the agile consultants, scrum masters, TDD, CI, etc. All the things you hear these blog posts evangelize about. It brought development to a total halt as all these assholes put in their $0.02 about how we needed scrums, sprints, user stories, and story points. Developers couldn't work on the features they knew were important without cutting through miles of red tape (finding a "customer" to make a story, breaking that story down into the actual work that needed to be done, moving the story through the backlog, estimating points for the stories, etc). Like I said above. It ruined my software department. I wouldn't wish agile on my worst enemy.
- Rabidgremlin 16y agoAhhh it actually sounds like your team was originally being Agile: http://agilemanifesto.org/ http://agilemanifesto.org/ As opposed to how a lot of people land up doing Agile: http://www.halfarsedagilemanifesto.org/ http://www.halfarsedagilemanifesto.org/
- abalashov 16y agoAhhh it actually sounds like your team was originally being Agile This statement is unfalsifiable; this kind of retroactive defense makes Agile out to be an ever-moving goalpost. If any effective, basically "good," organic team behaviour was "Agile" to begin with, there is no identifiable differentiating criterion of Agile methodology from any other mode of small-scale collaboration.
- auxbuss 16y agoCan I just adjust you last sentence: Start simple and then keep throwing out stuff you don't need.
- DanielBMarkham 16y agoWorks for me. How about never do something that isn't making the team run faster? I don't care what the books or the authors say, agile is about optimizing your particular team for your particular situation. There's not a one-size-fits-all cookbook. The only caveat I'll add is this: many times people won't believe (or do not understand) that certain things will actually make them run faster and have a happier team. So you have to have an open mind. If you already know agile sucks, it's probably going to suck. If you already know that agile means TDD and everything done a certain way? It's probably going to suck a lot. In fact, the ones that think they know agile (and love it and are willing to tell everybody they hear about it) are usually the ones making life miserable on everybody else. I'd much rather have honest skeptics. With skeptics you can try something and decide whether you like it or not. In the "agilistas" minds, unless you do it perfectly, you are sinning against agile and it's no wonder you are struggling. They can be impossible to live with. (and they've lost track of the big picture) Or as I told one team, I've never had a team fail because of the way they decided to do (or not do) story points. Don't get hung up in the weeds.