Agile is Tulip!

[vetran]

Lolz...

But seriously - is it better to do full design up front and then develop or do the users simply struggle to give full requirements until they have seen a beta of the system.

My experience tells me the latter but I am not an expert!

WOPMS.

Seems to be the most successful, however at every point you have to explain its only a prototype in 36 point. If you don't they have sold it to everyone as being ready next week and looking like your current screenshots. Not sure why they can't get over the idea that an artists impression is a finished product - I wonder if they treat archtects the same way?

[sasguru]

I think nubile methods could catch on.

Even better. Does it involve lady developers having to give presentations topless?

[eek]

WOPMS.

Seems to be the most successful, however at every point you have to explain its only a prototype in 36 point. If you don't they have sold it to everyone as being ready next week and looking like your current screenshots. Not sure why they can't get over the idea that an artists impression is a finished product - I wonder if they treat archtects the same way?

I always do design last. Functionality its all there but I keep page layouts tulip so its obvious to everyone that its not the finished project.

Actually that isn't true, the design is done as I do the work however I use an especially crap CSS layout variation especially for early demos.

[DimPrawn]

Using my patented Flexible(TM) methodology, you whip up a beta. Then change it to suit users requirements.
Flexibly, of course (TM).*

*This is the strap line of my new methodology.
I can't be arsed to do it, but I bet I could write a BS book about Flexible(TM) and many cretinous IT "managers" especially in the Public sector, would buy it.

You would probably be hired by CMD as "IT Tsar" and put on a new Quango.

Quango Bosses 'Earning Up To £700,000'

[doodab]

Even better. Does it involve lady developers having to give presentations topless?

I think

1. Your project meetings are called orgies
2. Your project leader is called a "fluffer"
3. Releases are called "money shots"
4. A requirement is called a "carnal desire"
5. You spent thousands getting someone to tell you this

[amcdonald]

WOPMS.

Seems to be the most successful, however at every point you have to explain its only a prototype in 36 point. If you don't they have sold it to everyone as being ready next week and looking like your current screenshots. Not sure why they can't get over the idea that an artists impression is a finished product - I wonder if they treat archtects the same way?

Never do it in code, Do a wireframe so that it is obviously a stylised mockup to even the thickest people in the organisation (and for people outside of management)

[doodab]

I wonder if they treat archtects the same way?

Architects never produce anything that could be mistaken for a working system.

[original PM]

yep currently developing a system - we know it will be web based, we know what it will do so the 'design' was simply putting together an excel spreadsheet with multiple tabs denoting the different web pages and we just put which fields we wanted on each tab and left the developer to do the rest.

Initial beta drop was an absolute peach and pretty much nailed it.

Had we done it Prince ways then we would still be fooking about!

[Lockhouse]

I work as a scrum master and Agile coach. I'm currently implementing Scrum at a bank in The City.

In my experience most people are using "Agile but...." or "Scrum but....", very few people are using it as prescribed. I'm not saying Agile always works but implemented correctly and with the right people it's the best way I've found way of managing development teams and their work.

[Mich the Tester]

I work as a scrum master and Agile coach. I'm currently implementing Scrum at a bank in The City.

In my experience most people are using "Agile but...." or "Scrum but....", very few people are using it as prescribed. I'm not saying Agile always works but implemented correctly and with the right people it's the best way I've found way of managing development teams and their work.

Isn't that the point of agile ideas? Do what works to build working software/value?