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 […]
Edit Those Epics: Stories Don’t Span Iterations was posted on Techwell, the new site of Stickyminds.com. Yes, I will have to figure out how to change my tags/categories. Please do leave comments over there, I will be responding.
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.
If you haven’t read Hiring the Best …, you may not realize how often I say it’s ok to iterate on job descriptions.Job descriptions cannot be static. To all you HR folks, sorry, you have to work with the hiring manager to determine what’s most important for the position you’re filling now. This particular developer/tester/writer/project
Tristan, the senior manager in charge of all projects, strides into Ilene’s office and plunks himself down in her visitor’s chair. “Ilene, you are the project manager in charge of the project to save the company, right?” Ilene nods. “I really need you to fit this other feature into this release,” Tristran says. “We’re toast