Dealing with requests
March 4th, 2009 by Michael Christian
Recently we were discussing about development of an Intranet system for a large organisation and capture how it seen from different roles involved in the projects:
My classic problem is how you translate this requests into software:
Exec, “I want my company collaborate more efficiently and effectively which lead into more productivity and increase revenue.”
Marketing, “My laptop drives me mad and I have to wait for ages before someone put a new press release on the web. I want a quick non techie way to communicate ideas and it has to be super user friendly.”
IT,“ We’re barely cope dealing with IT problems here, is this another let’s try a cool new software kind a thing ?”
HR,“So we’re going to share all users detail on the system through web, It’s OK but my HR stuff is still private right ?
Finance, “Is this secure? Does it work with my payroll system? Can it automate some of my excel nightmares?”
Average staff, “Intranet project? Sounds cool, do I get a pay rise ? I hope we’re going to have lavish launch party.”
LOL, It’s so true!
I bet you’ve seen this cartoon before – http://static.flickr.com/29/53006710_5ec44aa728_o.gif – describing the variety of ailments associated with today’s software development processes.