Q: When (why) might we choose to deliver information that does not conform with standards?

A: The only real reason I would choose to deviate from standards was if I was going to design and build something that was in a closed environment. That is, if I was building a site that was on a CD-ROM and was only going to be viewed on a Windows machine – I could tailor the site for that media and that platform. I might also build the site to take advantage of MS Internet Explorer. Again, this would be one of the only reasons that I wouldn’t use standards.

Q: How do standards impact our ability as communicators to reach our target audiences?

A: Standards, specifically web standards, help insure that information is stored, formatted and presented in similar ways across the Internet. The benefits of designing with standards can be found in both the cost savings for the customer and the efficiency of the site. With a standards-compliant site, one is assured that the content will render properly on most (if not all) contemporary browsers. This is a strong benefit if the customer or site owner needs to reach an audience that includes people with average or below average computers.

Back to the question – standards impact our ability as communicators in two main ways. First, the standard presents a set of rules or a framework that the code and the site must work within. This helps focus on the content and less on the need to be truly original (and possibly produce a site that doesn’t work on some browsers). Secondly, standards help ensure that the site will work today and tomorrow. Jeffery Zeldman, the author of “Designing with Web Standards” states that 99.9% of web sites are obsolete. In addition, he states “design and building with standards lowers production and maintenance costs while making sites more accessible to those who have special needs. (Translation: more customers for less cost, improved public relations decreased likelihood of accessibility)”

Q: Based on class discussion and reading, which team role most appeals to you? Which least appeals? Why?

A: For this question I’m going to focus on the web & development team structures. The team roles that most appeal to me are the Project Manger, Information Architect, HTML developer and Technology Lead. The Project Manger role is appealing because I’ve only had limited experience as a “real” project manger. I’ve found the term “Project Manger” often used and often misused. Most organizations throw the word around but don’t often realize or understand the skills and training that are required to be a good PM. I think it would be a great experience to be a PM.

The HTML developer, Tech Lead, and IA are all roles that I’m familiar with and have enjoyed in the past. Over the last several years I’ve owned a web design company and have had the opportunity to sit in the seat of all the roles from PM to QA engineer. The team roles that carry the least amount of appeal for me are the Editor/copywriter, Database admin and the QA engineer. Although I’ve participated in each of these roles, the skill set I have doesn’t match well. In addition, when working on a large project, I’ve found that it’s almost always a good idea to hire an expert in these fields if you want the overall quality of the application (or site) to remain high.

Q: How do you prefer to communicate with team members? Why?

A: When communicating with a team (or individual team members) I usually prefer to discuss issues with email or IRC. There are three main reasons for this: first, the communications are not as distracting as face-to-face meetings. Secondly, an email or IRC session can be used as a reference tool. For example, if someone sends me a list of several tasks, I have that list typed out for me. Lastly, the saved communication can ask as supporting information if there’s a disagreement among team members.

Q: Think of a team you’ve worked on before. Was it effective or not? Why?

A: The teams I’ve worked on have usually been small (2-5 people) and have been associated with projects that had a short time to completion. For example, I’ve worked on several teams whose purpose was to build a web site or application within a time frame of 1-6 months. When I was just starting in web development I was usually placed into a team with other people. I didn’t know what their strengths and weaknesses were until we were well into the project. Like most teams in this situation, the need for clear and concise communication was necessary for us to accomplish our shared goal. In more current circumstances, the teams I’m apart of now are comprised of people I know and have worked well with in the past. That said, the team’s shared goal(s) tends to be easier to achieve.

The traits I find most beneficial in team environments include: excellent communication skills, positive attitude, and strong motivation.

The traits I find most distracting in team environments include: narcissism, apathy and a poor demeanor.