Original Project Due Date

Reply

Bamboo PM Girl replied on Wed, Feb 3 2010 4:09 PM

rated by 0 users

Hello Maria,

"Original Project Due Date" is your planned date/targeted date, i.e. it's not your Actual Due Date. When your project is finalized and at that point you want to take the snapshot of all the data (budget, cost...etc.) that would be the "Baseline End Date".

Product Team

Reply

Maria replied on Thu, Feb 4 2010 3:45 AM

rated by 0 users

Hi,

thanks for your reply!

Still, this makes me a bit confused. The "Baseline End Date" I do understand and obviously "Actual End Date". However, to me planned date/targeted date would be the field "Forecasted End Date" or maybe "Current Project Due Date". "Original Project Due Date" sounds to me a due date that was set in the beginning of the project, i.e. the same as "Baseline End Date".

Could you just briefly exaplain the differences and purpose regarding all these end dates:

1. Actual End Date
2. Baseline End Date
3. Forecasted End Date
4. Original Project Due Date
5. Current Project Due Date

Best regards,

Maria

Reply

Bamboo PM Girl replied on Thu, Feb 4 2010 10:00 AM

rated by 0 users

We defined the terms similar to the reference here:

http://www.project-management-knowledge.com/definitions/p/planned-finish-date/

In our app, we use "Original Project Due Date" instead of "Scheduled Finish Date" and "Current Project Due Date" instead of "Current Finish Date". They are there so you can associate them with AC, PV, BAC, EAC...etc.

Here're the fields:

Where is the data stored?

We provide a list template with the web part so users will have a Bamboo Project Dashboard list on the site where they deploy the web part. The Bamboo Project Dashboard list has the following columns:

1. Project Name – Single line of text
2. Project Manager – People/Groups
3. Project ID – Single line of text.
4. Project Status – Choice field with the choices shown below saved as Single line of text. These choices can be modified by the customer since we don’t expect them to be any particular value.
   1. Active
   2. Complete
   3. Cancelled
   4. Pending
5. Project Type - Choice field with the choices shown below saved as Single line of text. These choices can be modified by the customer since we don’t expect them to be any particular value.
   1. Custom
   2. Marketing
   3. Product
   4. Other
6. Project Phase - Choice field with the choices shown below saved as Single line of text. These choices can be modified by the customer since we don’t expect them to be any particular value.
   1. Initiating
   2. Planning
   3. Executing
   4. Controlling
   5. Closing
7. Executive Summary – Multi-line of text field. This is a place for the user to write a short project charter, report/summary or list issues/risks.
8. Issue Description. Single line of text describing main issue affecting overall status of the project.
9. Baseline Start Date – Date Field that stores just date (not time). User manually enters the value.
10. Baseline End Date – Date Field that stores just date (not time). User manually enters the value.
11. Actual Start Date – Date Field that stores just date (not time). User manually enters the value.
12. Actual End Date – Date Field that stores just date (not time). User manually enters the value.
13. Forecasted End Date - Date Field that stores just date (not time). User manually enters the value.
14. Project Completion (Percentile) – User manually enters the % value.
15. Duration – User manually enters the value. There is another field for duration (see #x) that we calculate.
16. Original  Project Due Date –– User manually enter the value
17. Current Project Due Date –– User manually enter the value
18. Project Original Budget (BAC) – User manually enters the value ($). Must be a number because we will use it to calculate EAC (see below).
19. Project Current Expense (AC) – User manually enters the value. Must be a number because we will use it to calculate CV and CPI (see below).
20. Project Planned Expense (PV) – User manually enters the value. Must be a number because we will use it to calculate SV and (see below).
21. Project Earned Value (EV) – User manually enters the value. Must be a number because we will use it to calculate CV, SV, CPI, and SPI (see below).
22. Project Health Overall Status (on-track, delayed, stop…etc) – User selects from a choice field. These choices can be modified by the customer since we don’t expect them to be any particular value.
23. Project Health Schedule Variance Status (on-track, early, late…etc) – User selects from a choice field. These choices can be modified by the customer since we don’t expect them to be any particular value. There is a similar field that is calculated.
24. Project Health Effort Variance Status (on-track, under, over…etc) – User selects from a choice field. These choices can be modified by the customer since we don’t expect them to be any particular value.
25. Project Health Cost Variance Status (on-track, under, over…etc) – User selects from a choice field. These choices can be modified by the customer since we don’t expect them to be any particular value.
26. Project Scope Variance Status (scope creep, cannot implement one of the requirements…etc.) – User selects from a choice field. These choices can be modified by the customer since we don’t expect them to be any particular value.
27. Project Health Customer Feedback Status (normal, under, over…etc) - User selects from a choice field. These choices can be modified by the customer since we don’t expect them to be any particular value.
28. Project Plan Effort (Hours/Days) – Duration => This is a calculated field [Baseline End Date – Baseine Start Date].
29. Project Current Effort (Hours/Days) - Duration => This is a calculated field [Forecasted End Date – Actual Start Date].
30. Link to Project Site (URL)
31. Cost Variance (CV). This is a calculated field [CV = EV – AC]. A negative result means the project is over budget; a positive result means it is under budget.
32. Schedule Variance (SV). This is a calculated field [SV = EV – PV]. Negative is behind schedule, Positive is ahead of schedule
33. Cost Performance index (CPI). This is a calculated field [CPI = EV/AC]. We are getting $____ out of every $1
34. Schedule Performance Index (SPI). This is a calculated field [SPI = EV/PV]. We are [only] progressing at ____% of the rate originally planned.
35. Estimate at Completion (EAC). This is a calculated field [EAC = BAC/CPI]. As of now, how much do we expect the total project to cost?
36. Estimate To Complete (ETC). This is a calculated field [ETC = EAC = AC]. How much more will the project cost?

Product Team