Re: Re: Why are we still allowing the term "Agile Project Manager"?
2008-07-01 01:32:37 GMT
Hello, Robert. On Monday, June 30, 2008, at 5:08:58 PM, you wrote: > I was thinking of things that might be hard to resolve at the broader > business level, because decisions were being delayed, for example. > So if the software was for a timecard system for a company, and they > were delaying a decision about the way overtime was recorded while > they negotiated with the union. > Might that seem like an obstruction to developing the software? Only if the PO had scheduled the story and then the info wasn't available. The programmer should report the obstacle and the SM should resolve it, probably by having the story cancelled. Too often, however, teams just try to muddle through without knowing what to do, waiting long intervals between Q and A, and such. That's not so good. > But maybe you should suggest an example of an obstruction too. Handoffs, e.g. programmer to tester; Technical tasks; DBA not available; Waiting for UI design for a story already scheduled; Multi-Sprint work in progress, i.e. phased stories; ... Ron Jeffries www.XProgramming.com I must create a system, or be enslaved by another man's;(Continue reading)