Milestones

Hi

Okay, first, I’ve just started using evaluating LP for internal use – we implement an internet-based software service. I’m just trying to get my head around the different methodology that LP uses as versus something like MS Project (although I’ve only used that a little). So apologies if this question sounds stupid.

If I have a project milestone, like a “Go Live” date for the client to start using our software, is that something that I should be adding to the workitems? If I create a workitem and don’t enter any scheduling info, but I do enter a promise by date, a diamond duly appears on the timeline. But, in my project this affects the other items. I’d like to use it as a marker to see what we should be aiming for. Or am I just thinking in the wrong way?

Or… should I create a sub-project that IS the milestone and let LP effectively calculate the go live date for me? It’s just that generally, the go live date is critical for our clients, and that’s why I thought the promise by date would be the option in this scenario.

Hope this makes sense.

Chris.

I think that makes perfect sense Chris. Here is how we tend to structure things:

-Stage One (Project) Promise Date: 4/1/08
  - Implement Mind Reading (Workitem)
  - Develop Time Machine (Workitem)
  ...
- Stage Two (Project) Promise Date 4/15/08
  - Investigate Ethics of Time Travel (Workitem)
  - Implement Retroactive Rescheduling (Workitem)

By placing the Promise Date on your project, LiquidPlanner will let you know whether you are on schedule for each release. Generally, I would suggest only putting Promise Dates on Projects, and using the Projects to group your releases.

Does that seem reasonable to you?

Thanks Adam.

I think that makes sense to me. I guess that, even with my limited knowledge of things like MS Project, I was thinking in the “wrong way”. Hopefully, over the next few weeks my colleague and I can test the product a little more to see if it’s suitable. Thanks.