Tag Archives: developer
How many CTO’s does it take to change a lightbulb?
Two. One to screw in a new lightbulb and the other to retroactively declare it a planned outage.
How many help desk engineers does it take to change a lightbulb?
Rapid development calls for rapid decision-making. Agile practitioners sometimes make the mistake of assuming that an Agile environment doesn’t have any spare time built in for research to inform those decisions. It’s not so. You’re actually more at risk for wasting time when you don’t research.
A: 8-track tapes; sleeves on wedding gowns; heavy up-front requirements.
Q: What is nostalgia?
A: Data storage costs; mortgage industry headcount; development project documentation.
Q: What is downsizing?
A: Two face cards; Oliver and Hardy; driver/observer programming team.
Q: What is a pair?
Marketers don’t use the F word very often. It makes them peevish and erodes their self-esteem.
No, no, no, I don’t mean that F word. That one we use. A lot. Like omigod. I’ve known marketers who use that F word word like verbal hot sauce they sprinkle over everything – more frequently than “and” or “the”. Oh wait, that’s me. But I digress.
“I promise not to exclude from consideration any idea based on its source, but to consider ideas across schools and heritages in order to find the ones that best suit the current situation.”
Love, love, love this oath – from our friend Alistair Cockburn. Why is it needed? To remind turf warriors and methodology zealots that Us Versus Them intolerance robs the business of progress. The Oath has lots of uses, because projects unfortunately tend to spawn multiple factions: Read more on A Marketer’s Guide to Agile Development – I Pledge Non-Allegiance…
My own requests to get on sprint backlogs are often analytical – that whole measuring success thing, for a variety of reasons: (1) enhanced analytics the business didn’t realize would be needed when a feature or function originally went live (2) basic tagging that should have been included when a feature or function went live but didn’t make it into the original sprint(3) tag modifications made necessary by site changes (4) repairs to tags that worked in test but for some reason broke in production.
A Marketer’s Guide to Agile Development – Hello Cleveland! If You Can’t See Them, Is It Still Agile?
The scrum or stand-up meeting is a major part of Agile methodology. Ideally, everyone works in the same area (called co-location), and talking in person is considered the most effective way to work. In fact, face-to-face communication is considered so important to the effectiveness of the methodology, it has its own line in the Agile Manifesto: The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
An old boss of mine used to have a small wooden plaque on his desk. It said “JDI” – “Just Do It”. Not in the Nike “you go, girl”, self-empowerment sense. More in the “just because I’ve finished talking doesn’t mean you get a turn now” sense. Anything short of “right away!” and he would silently nudge the plaque in your direction. Good times, good times. Marrying up that imperious client attitude up with Agile development would probably be a big mistake. But here goes: Agile – The Motion Picture”