Analyst skills/technologies

[MrMarkyMark]

I think this is a big strength of Agile, they get the chance to say "what the hell is that? That's not what we wanted, it needs to do..." very early on rather than when you deliver it for testing

The value of being able to be hands-on with some crappy prototype is invaluable, you get requirements creep caught as part of the initial requirements.

Very much a necessity to prototype where I am.

Costly "mistakes" can be made otherwise.

[d000hg]

I suppose prototypes are a part of waterfall and classic methodologies anyway, but in Agile the "make one to throw away" idea is replaced with continuous refactoring. All those little details you get even in a prototype are valuable. Unless your prototype is "I knocked this up in VBA+Excel during lunch".

[LondonManc]

I suppose prototypes are a part of waterfall and classic methodologies anyway, but in Agile the "make one to throw away" idea is replaced with continuous refactoring. All those little details you get even in a prototype are valuable. Unless your prototype is "I knocked this up in VBA+Excel during lunch".

With BI it's usually make one and shove it live

"But the numbers haven't been tested, it was just for look and feel"
"And it looks and feels good - get it promoted to live!"

[MrMarkyMark]

With BI it's usually make one and shove it live

"But the numbers haven't been tested, it was just for look and feel"
"And it looks and feels good - get it promoted to live!"

They want you back at the ranch

[LondonManc]

They want you back at the ranch

Not my fault that my prototypes are better than the other team's end product.