Many UX practitioners own their own TARDIS – it’s the pattern many of us have adopted so designers can work with development teams using Agile methods by designing up-front and then working behind to iterate the designs. While some suggest that its best practice, does it actually reap the benefits that Agile has to offer? What are its pitfalls, what are the advantages and disadvantages compared to just doing up-front design, and are there any smarter ways of becoming agile, whether working solo, in design teams, or working on end-to-end projects?
[gigya embed id=”preziEmbed_zymr7j3uiqvw” name=”preziEmbed_zymr7j3uiqvw” src=”http://prezi.com/bin/preziloader.swf” type=”application/x-shockwave-flash” allowfullscreen=”true” allowFullScreenInteractive=”true” allowscriptaccess=”always” width=”450″ height=”350″ bgcolor=”#ffffff” flashvars=”prezi_id=zymr7j3uiqvw&lock_to_path=0&color=ffffff&autoplay=no&autohide_ctrls=0″ ]
This presentation was given at WebDU 2012 in Sydney, with a second iteration given at Agile Australia 2012 in Melbourne.
How do you lead strategic outcomes faster to customers with lower risk, higher quality and lower cost? ContinuousNext describes a path to achieve these outomes,