If you haven’t read Duane Nathaniel’s thoughtful comment on What Happens When You Can’t Finish What You Wanted in an Iteration?, do so now. Duane makes some great points. RUP has iterations; they’re not timeboxed–they’re deliverable-based. (Take a look at the link that Duane points to.) In the RUP, an iteration results in a deliverable. […]
Pawel caught me being ambiguous. See his comment, “1. I’ve seen features/fixes which required 2 days to be developed and released.” Sorry, me too. But what I tried to say was this: A feature was estimated to be some duration of person-hours. Those person-hours have come and gone. The feature still requires another 10-12
I ran a little workshop today about transitioning to agile. I was talking about timeboxed iterations, and one of the participants asked this question. “So I don’t quite finish one of the features I want to finish in this iteration–and it’s the end of the project. I think it’s going to take me a
I facilitated a management problem-solving session at the STARWest conference yesterday. When I was debriefing the activities, one participant said he’s met a bunch of testers and test managers who had a “siege” mentality. He was surprised by that. I’m still surprised when I meet people like that. I sometimes see developers who feel
A colleague asked me what to do when you’re in an iteration and you realize that the story you’re working on spawns other requirements. I suggested that the person add them to the product backlog (the backlog of everything you want to do for the product) and re-rank the requirements in preparation for the next
So after I posted the Probabilistic Scheduling post, I was working merrily away. I had made some small progress on the book, but was still finishing up other things. Finally, Wednesday I had cleared the entire day to work on the book. I was having trouble with one chapter, so I decided to make
It’s been quite the Monday so far. My office toilet started spewing water, a cabinet door fell off one of the cabinets in the kitchen, and I’m trying to back up and duplicate my hard disk because both latches on my Powerbook broke at the Agile conference and I need to send my computer
Several years ago, a colleague emailed me, asking how to keep sponsors involved. My colleague was using company-mandated phase-gate lifecycle with long project durations (18-24 months). I’d recommended providing a project dashboard and showing the sponsor progress. My colleague was stumped–the dashboard wasn’t particularly helpful until they were in the testing phase and it
A reader was reading Characteristics of Great Project Managers and asked, “Do you feel that to be a great Project Manager one need not know completely about the technology involved?” No. Project managers need to understand enough about the technology so that they can make tradeoff decisions (or help product owners make tradeoff decisions) about
I’m working with a group of people who are new to iterative development. They’re doing more of a staged delivery lifecycle than an agile lifecycle, but they are releasing about once a month. They don’t like it, because they say they’re releasing too frequently. The problem is that their planning and releasing take too