Implement your DAM solution using Agile software development methodologies
- PDF / 89,191 Bytes
- 4 Pages / 595 x 765 pts Page_size
- 97 Downloads / 195 Views
Papers Implement your DAM solution using Agile software development methodologies Andrew Bates has nearly 10 years experience with DAM. His experience includes consulting, product marketing, technical management, architecture, design, and implementation of both packaged software and custom solutions. He currently works for Flatirons Solutions as Director of Rich Media Solutions. Flatirons Solutions, an Inc. 500 company, provides consulting, systems integration and systems & software engineering services to Fortune 500 companies and government agencies. It is a leading content management solution provider specializing in DAM and XML-based publishing solutions.
Keywords: DAM, Agile, user experience, rich media, project management, media and entertainment Abstract DAM solutions are real and have significant impact on business. The technology is maturing and there are numerous examples of successful deployments. If you are considering a DAM implementation, how do you ensure your success? This paper comments on the challenges with traditional project management approaches to DAM solutions and explains how Agile software development methodologies can overcome them. Journal of Digital Asset Management (2007) 3, 173–176. doi:10.1057/palgrave.dam.3650087
Andrew Bates 4747 Table Mesa Dr. Suite 200 Boulder, CO 80305 Tel: 416 418 0510 E-mail: Andrew.Bates@ FlatironsSolutions.com
Do you remember the telephone game? That is the game where you and a bunch of your friends sat in a circle and took turns whispering a message in each other’s ear. The person whispering the phrase to you could only do it once. You had to listen carefully to what they are saying and then try your best to repeat it to the next person. Inevitably, the starting phrase and the ending phrase would be different. What affected the outcome of the game and the integrity of the message? The person telling you the information was usually giggling and had a hard time repeating the phrase accurately. Other children were laughing, and carrying on while waiting in anticipation for their turn. And undoubtedly, one, or more than one person, intentionally changed the phrase to serve their purpose, which was usually to gain attention. The telephone game has a lot in common with the traditional “waterfall” software development processes commonly used for developing and deploying DAM solutions. The “waterfall” project management approach treats the project like a pipeline. It is a process that
© 2007 Palgrave Macmillan Ltd 1743–6540 $30.00
Vol. 3, 4 173–176
often sees the primary business problem and requirements identified in the beginning but not addressed by the solution that is delivered in the end. This is what typically happens. A team of project owners will gather requirements from key users. These requirements will get transcribed and communicated to team members on the project. The requirements will be reviewed and validated. The project team will go off and build a solution that most likely is a combination of existing software tools, configuration and custo
Data Loading...
