Basecamp:
Video – Basecamp
I had the opportunity to use Basecamp during my internship. Basecamp is a project management site that allows for the easy creation of new projects. It allows you to post tasks, assign members to those tasks, invite new members to the project, specify deadlines, share with clients and more. It is an extremely helpful package; so much so that I searched for similar free software when trying to plan game creation projects with friends. (because we’re broke) I found Basecamp to be extremely helpful with the whole process as it not only allowed us to be easily assigned new tasks and deadlines, but it also gave easy access to previous projects’ archived information.
Scope:
Article – CIO How to Define the Scope of a Project
I believe that defining the scope of a project can easily make or break the entire project by itself. To define the scope you need to take into account:
- Objectives
- Goals
- Sub-phases
- Tasks
- Resources
- Budget
- Schedule
In previous projects I’ve participated in, the usual sources of failure were either an overestimation of the objectives and goals we could reasonably reach, or not taking into account our resources and schedule. I’ve tried to develop several games or applications with friends in the past and most of them fall apart due to the continuous adding of goals, mostly because we had neither the budget nor the ability to follow any sort of schedule to complete these tasks. In order to be successful in your projects, you must carefully define your scope so that you’re not overreaching your boundaries.
Site Specification:
Article – Boagworld Throw Out Your Website Specification
This article talks about how rather than making a website specification with rigid requirements, it’s better to instead make a hypothesis and make changes to the alpha and beta of the website as you study the interactions with users. While I do think the author makes an excellent point in that you save time and money by building the site around studied interactions with users, rather than wasting money developing features that are eventually going to be tossed out; I feel that completely getting rid of the site spec is also a mistake. I feel that a blending of the ideas would be best. Rather than having rigid requirements that will need to be changed, wasting time and money on the lost work; and rather than only having a hypothesis and changing the site as you go I feel that instead a more flexible site spec that allows for defining what must be while allowing easy changes and updating with user observation would be ideal.