I have a new column up on project management.com. It’s called Debugging Your Geographically Distributed Agile Team. (You have to register to read it. Registration is free.) You can do agile with geographically distributed teams. You might not be able to do Scrum. You have other choices of approaches. Helping a team form is tough. […]
Back when I was a Director of many things at one company, we had an urgent patch to go to a customer. My VP wanted it “yesterday.” Well, time only goes in one direction. I gathered my continuing engineering team, explained the pickle we were in. “Everyone wants this patch right away. However the customer
Thanks to George Dinwiddie, who pointed me to the hashtag #FiveWordTechHorrors. I have been enjoying that stream. I found “We Only Hire Rock Stars” at some point. I realized I had not written about a common hiring trap in a very long time. Yes, you should hire “stars.” They have to be stars who fit
Glen Alleman seems to have nailed it, with Alert – Was Poor PM the Root Cause of ACA Difficulties? Among the many problems: No overall program manager No way for stakeholders to know what Done looks like (no release criteria) No replanning I’m a huge fan of rolling wave planning. (Read Starting with Rolling Wave
I’ve been having some strange email conversations with two testers, one business analyst, and a project manager. Yes, a total of four new people. They have each found jobs on projects. And, they are in over their heads. Each of them wrote to me, hoping I would help. The testers wanted to know how to
I’ve been working with folks making their transition to agile. One of the hardest transitions is for the managers and technical leaders. Managers are accustomed to working in timeboxes. To them, the iteration is a timebox. But, they also are accustomed to features spanning multiple timeboxes, and that’s not OK in agile. They are accustomed
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