Join our Agile 2011 Project Portfolio Simulation: "The Bubblesphere"

Hey, you say, is it true you're presenting at next week's Agile 2011 conference in Salt Lake City? Yes indeed! I've had the privilege of developing an agile project portfolio simulation with NAVTEQ/Nokia product manager Cory Hohs, and we're fairly enthusiastic about how it turned out. Participating will be just the right way to spend a lazy summer afternoon at the conference, for sure!

Actual presentation information

We've been slated for Thursday, August 11, at 3:30pm. Hope to see you there!

Comments

How Do You Vote Someone Off of Your Agile Team?

One of the conundrums of agile conversion is that although you are ordered by management to "self-organize," you don't get to pick your own team. You may not have pictured it this way, but your agile team members are going to be the same people you worked with before, when you were all doing waterfall! I know I wasn't picturing it that way for my first agile team, so I thought I should warn you. (I thought I was going to get between six and eight original Agile Manifesto signers. That didn't happen.). Why "warn" you (as opposed to "reassure" you, say)? Because the agile process is going to reveal every wart, mole, quirk, goiter, and flatulence issue on the team within a few hours. In the old days, you could all be eccentric or even unpleasant in your own cube, communicating only by document, wiki, email, and, in extreme situations, by phone. Now you are suddenly forced to interact in real time, perhaps in person, with written messag...

A Corporate Agile 10-point Checklist

I'm pretty sure my few remaining friends in the "small, collocated team agile" community are going to desert me after this, but I actually have a checklist of 10 things to think about if you're a product owner at a big company thinking of trying out some agile today. Some of these might even apply to you if you're in a smaller place. So at the risk of inciting an anti-checklist riot (I'm sorry, Pez!), I am putting this out there in case it is helpful to someone else. From http://www.yogawithjohn.com/tag/yoga-class/ Here's what you should think about: 1. Your staffing pattern. A full agile project requires that you have the full team engaged for the whole duration of the project at the right ratios. So as you provision the project, check to see whether you can arrange this staffing pattern. If not, you will encounter risks because of missing people. Concretely it means that: a. ...

Requirements Traceability in Agile Software Development

One of the grim proving grounds for the would-be agile business analyst (henceforth "WBABA") is the "traceability conversation." Eventually, you will have to have one. You may have seen one already. If you haven't, you may want to half-avert your eyes as you read further. It gets a little brutal. But if you close them all the way, you can't read. From: http://www.highestfive.com/mind/how-to-perform-a-successful-interrogation/ Dialogue: WBABA : ...so in summary, we complete analysis on each story card, and then we support the developers as they build it that same iteration! Corporate Standards Guy: but how do you do traceability in agile? You have to have traceability. It's broadly recognized as an important factor in building rigorous software systems. These software systems permeate our society and we must entrust them with lives of everyday people on a daily basis. [The last two sentences are an actu...

Pragmatic Agilist

Search This Blog