Posts Tagged: agile


12
Jan 10

Project Management Trends

Leading Answers has a thoughtful article on Project Trends Every PM Should be Aware Of. My favorite bit:

“The World Has Changed – Why Haven’t Your PM Tools and Approaches?
In the last 10 years many changes have occurred in the world of managing IT projects, yet we still see the same tools and approaches being employed. Is this because they are classic and timeless? Are the traditional PM approaches so successful that they do not need to be dragged here and there following trends and immature technology fads? No, I fear it is more that people are creatures of habit, and the usually more mature project management community, are worse than most at evaluating and adopting new approaches.”

The first thing you must do is admit you have a problem with your project management process. It isn’t the business analysis, coders, or testers that is broken. It’s the process that is broken. Not the people. Once you can admit that, the world becomes much much less stressful.


19
Dec 09

About that functional spec…

David Heinemeier Hansson’s perspective:

“I think of functional spec as one of the worst inflictions that has ever happened to the software development world. I think functional specs are a relic of a time when building features was a very, very hard and long process and you had to do all of this upfront planning because once you wrote anything in software, it was pretty much impossible to change it. I don’t think that functional specs is a technique that’s any longer relevant.”


9
Nov 09

Wisdom of Twitter (ie, some good quotes)

Jim Highsmith (@jimhighsmith):
“Agility is the ability to think and learn rather than blindly following a recipe.”

Bob Marshall (@flowchainsensei):
“You really have no clue as to how much your business success depends on software, do you?” #neversaid

Ben Simo (@QualityFrog):
“Compliance with standards makes sense when & where interoperability is more important than innovation & improvement.”

Wil Harris (@wilharris)
“New Apple mouse proves not only does Steve think we are too dumb for two buttons, we can’t even handle one. A mouse with no buttons. Nice.”

Jared M. Spool (@jmspool):
“Remember, if you torture data long enough, you can get it to confess to anything you want.”

Jeff Patton (@jeffpatton)
“Requirements are the boundary between what I get to decide and what you get to decide. It’s a fuzzy discussion, or DMZ”

Esther Derby (@estherderby)
“ppl talk about commitment as if it is an act of will. commitment requires will AND time, resources, skill, authority”

Bob Marshall (@flowchainsensei):
“So you’re all far too busy politicking and CYA-ing to actually bother about delivering stuff to the paying customer?” #neversaid

37signals (@37signals)
“The best way to have a good idea is to have a lot of ideas.” -Linus Pauling

Naresh Jain (@nashjain)
“Consistency is over-rated. Consistency is a big innovation killer. Let diversity & positive deviance help us explore better ways”


7
Nov 09

Visual Management

Visual Management is one of those things that feels obvious, but isn’t. The idea is that you manage projects, tasks, and other bits of work-in-progress using something visual (ie, not digital). It’s a chart on the wall that everyone can see, that everyone can modify, and is updated regularly.

There was a workshop specifically for Visual Management at Agile 2009 and a subsequent write-up on the presenter’s Visual Management Blog. But don’t be fooled – while this may be gaining traction in more technical areas, this will work for anyone’s project. There are lots of great pictures of examples and is worth your time to browse the pictures even if you don’t read the whole post. I’d suggest starting here.

I’m amazed at how well a non-technical solution can communicate to everyone on (or off) the team.

XQA_9556


5
Nov 09

Plans aren’t sacrosanct

Projects@Work has perhaps the most succinct description of the problem with plans:

“Plans aren’t sacrosanct — they’re meant to be flexible guides, not straightjackets. Agile project leaders focus on adapting to inevitable changes rather than opposing them. In this way, value and quality are the end goals and the plan becomes a means to achieve them, not the goal itself.”