developers-designers-testers interaction [closed]
- by user29124
Sorry for my bad English, and also you may not read this and waste your time, because it is just a lament of layman developer...
Seems no one want to learn anything at my workplace.
We have Mantis bug tracker, but our testers use google-docs for reports and only developers and team lead report bugs in Mantis.
We have SVN for version control and use Smarty as template system, but our designers give us pure HTML (sometimes it's ugly for programmers, but mostly it's OK) in archives, and changes to design made by programmers go nowhere (I mean designers use their own obsolete HTML and CSS most of the time).
We have a testing environment but designers don't have access with restricted accounts to it. So we can only ask them where to look for the problem and then investigate the problem by ourselves (and made changes to CSS by ourselves (that go nowhere most of the time...)).
I will not mention legacy code without documentation, tests, or any requirements, just an absence of real interaction in triangle programmers-designers-testers.
I'm not talking about using HAML, SASS, continuous integration, or something else, just about using basic tools by all participants of the development process. Maybe the absence of communication is not a problem in short-time projects, which will finish up in 2 months time but rather on the types of projects that lasts for years.
Any comments please...