If this methodology is overused, you will have your PM/dev team rebelling or leaving in a hurry. That said, I can see a trimmed-down of this used as an evaluat

If this methodology is overused, you will have your PM/dev team rebelling or leaving in a hurry. That said, I can see a trimmed-down of this used as an evaluation tool for more substantial product development decisions. Ideally, these questions would be posed to a PM or dev manager and not directly to a coding team. I also believe that the article is a good training piece for new(ish) general managers that have dev teams reporting to them. Along these lines, the listed criteria are a good thing to keep in mind for those GM's who (like me) sit in on product meetings while remaining fairly inactive. IOW, the GM can listen-in and try to passively assess whether the team has a handle on these points. If not, address surgically and offline with the right folks.