This article outlines some tips as far as project management goes. It has listening as the number one tip, which emphasizes it. Listening is huge. I’ve been on projects before where either the project manager or the person who’d taken charge didn’t listen to the others assigned to the project. It always spells disaster. Another point is to be an effective team player. One of my favorite doodle-based explanations of teamwork is when someone writes “TEAM” in all caps and then shades in the gaps in the letter “A” to form a lowercase “i”. The person says “hey look, there was an ‘i’ in team, it was in the ‘a’ hole!” The moral of that is that some people will actually work just for themselves instead of for the good of the whole project and the others involved. When that person is the project manager, no good can come from it. These tips SHOULD help prevent something like that from happening.
This set of reviews on project management software shows some tools that can be used in the process of project management to keep things on track. Some types of project management software can keep track of everything involved, while some are better suited to budgets and other finance-based things. What’s important though is that everyone who needs to use the software needs to know how to use it. On top of that, the project manager should use it often to record which tasks have been completed and to document the processes. Documentation is huge with project management, and software that keeps track of the documentation does still need to have input, as it cannot just do that by itself. So with all things considered, project management software can help a project move along and keep everyone up to speed, but if it’s not used properly and often enough, it really won’t do any good. In that case, if it’s not a free product, it will just be a waste of money.
This article is on writing better site requirements. Site requirements are a crucial piece of the web development process, as it outlines exactly what needs to be part of the site and what the site needs to do. Without direction, one cannot simply walk into the web development process. One point the article makes is to not go into details about how something will get done, just that it will get done. I notice that I jump into detailing how things get done when I’m working on my own projects or even school-related projects. That can possibly be a downfall, and it has been one in the past. Another key point is to avoid suggestions. Don’t make suggestions about what COULD be a requirement. Write what MUST be in the site. That’s what “requirement” means. Another good thing to note is to keep all the requirements in one document. This is for organization purposes, but can be important as it doesn’t create a mess of files that are all dedicated to one site’s requirements and specifications. All in all, keep things neat and focus on the task at hand.