On 22 Feb 2013, at 10:37, Joe Cutting <[log in to unmask]> wrote:
>
> it unbalances control of the project in favour of the software expert.
my experience is that an iterative approach is essential:
1. the project initiator doesn't have full understanding of what is possible with the available technology.
2. the project implementation team discover new possibilities as the technology is explored.
3. the software team may add or extend the technology as the project's needs are explored and communicated.
(this is sometimes referred to disparagingly as scope creep, but with digital projects, fast moving technology and an ever changing medium, scope creep is inevitable and should be planned for.)
It's my belief that a digital project is never *finished* it just ends when the budget runs out.
Designing a project that accepts the *never finished, always evolving* philosophy will allow the project team to take a more relaxed approach - approach it with a set of milestones, such that you can report success when you reach one, knowing that there are many more that may not be reached with the available funding.
:)
****************************************************************
website: http://museumscomputergroup.org.uk/
Twitter: http://www.twitter.com/ukmcg
Facebook: http://www.facebook.com/museumscomputergroup
[un]subscribe: http://museumscomputergroup.org.uk/email-list/
****************************************************************
|