Nested projects vs related projects

This post is a follow up on one of the points Dave mentioned in his interview last week. When we where discussing hierachical projects, he mentioned that having the ability to nest projects wouldn’t be off much use to him as most of his projects tend to only last a matter of days or weeks, so aren’t the sort of scale which would really benefit from this. He did mention a possible alternative, which would be much more useful which he referred to as “cross project viewing”.

He then went on to explain it using the following example.

such as the design of a site and system for the site. May have things like different developers or even different clients. But can still have the option of tasks that span the two, etc

It turns out Dave wasn’t the only person to think having related/linked projects is a good idea. In my interview with Sundeep, he mentioned he’d make use of both nested projects and the ability to have related projects.

Read the rest of this entry »

Projects Intro

A project is a temporary endeavour, having a defined beginning and end (usually constrained by date, but can be by funding or deliverables), undertaken to meet particular goals and objectives, usually to bring about beneficial change or added value.

The above definition of a project is taken from Wikipedia, and does a good job of summarising what a project is. At its most basic level, this application will help to complete these projects in an efficient manor by bringing together all the people involved in the project into a centralised system, where they can easily collaborate, share resources, track deadlines etc. What functionality is included as part of a project will be described in the appropriate sections, but I will outline some of the project specific functionality.

Projects can be nested

This is something which seems to be lacking from a lot of web based project management systems, but is requested by a lot of users. A project can have any number of sub projects, but each project can only have 1 parent (a top level project has no parent project).

Only one company and client account per project

At first, this may seem like a limitation, but this “limitation” combined with nested projects makes sense. If you have a project with 2 or more companies working on it, one of those companies will be leading the project. In this case, the lead company controls the top level project, and the second company is a sub project which has the parent company as its client. This even works for very complex project structures, as you can have the hierarchy of any width and depth, but at each level, there is always a company in charge of its sub hierarchy.

Projects, do it your way

Everyone manages their projects differently, so the PMS will not force a given system onto you, but aims to be as open as possible, so you can do it your way. One example of this is with deadlines, as mentioned in the opening definition, most projects are completed to a deadline, but not all of them, so this won’t be a required piece of information, although giving it will provide added value.

As mentioned earlier, the main purpose of the project is to act like a container, so it can group relevant data together, which will be discussed in more detail later.