Shane and the participants and I had a great time at the Geographically Distributed Agile Teams workshop last week. We ran a couple of simulations, and here are some of the emails the teams had: Do you have something for us to test yet? We have completed the card Hi again. I didn’t hear back
I’ve had several conversations in email and with clients recently that have all been about this question: “What do we do about our infrastructure?” Either the project or the program has to create/update/upgraded their architecture or automated test infrastructure, pay down technical debt, or somehow do something that’s not part of a story. And, that’s
I’m tech-editing an article for the Agile Journal. I’m having a discussion with the author about the words “productivity” and “throughput.” I believe that what we measure in agile teams is throughput, the number of features through the team over time. I don’t think we measure productivity, the number of features per person or per
I just posted Managing Timezones in Geographically Distributed Agile Teams. I have a funny story to tell about it. I’m in Belgium, getting ready for Belgium Testing Days. This weekend, the US changes to Daylight Savings Time. But Europe doesn’t. So, when do I talk to my husband? My husband and I are suffering by
One of the problems in a geographically distributed team is the dreaded email chain. Someone has a problem and sends an email. Probably late in the day, when he or she is frustrated after pounding on the problem all day, getting nowhere–except more frustrated. Sally sends the email to the project team. I take offense
So where does all of this get us with budgets and dates? In many ways, estimating project budgets or dates for agile projects turns out to be irrelevant. If you have a ranked backlog, and you finish features, you can always stop the project if you hit a particular date or cost. It does matter
In Part 3, you had some knowledge of the team’s velocity. This is the option of when you do not have knowledge of the team’s velocity, because this team has not worked together before, or has not worked on a project like this before. You are all coming in blind. Your Zeroth Best Bet: Wait
You have options for estimation, once you have met the preconditions. If you don’t have the feature set in a ranked order, you are in trouble. That’s because if you use any lifecycle other than an agile lifecycle, the feature order matters to your estimates, and the team will discuss the feature order in addition
So now that you know why it’s so difficult to estimate what do you do when someone asks you for an estimate? Preconditions for Estimation First, you ask a question back: “What’s most important to you? If it’s 3 weeks before the end of the project, and we haven’t finished all the features and we
Almost every manager I know wants to know when a project will be done. Some managers decree when a project will be done. Some managers think they can decree both the date and the feature set. There is one other tiny small subset, those managers who ask, “When can you finish this set of ranked