Iteration 2, User view and Feedback

Date: 20-Sept-2011

Meeting time: 1:20pm - 1:50pm

Attendance: All

Below is  a summary of today’s feedback by Steve:

1)      Project stages creation should be seperated from the project creation page.

2)      When we add a new stage to a project, system should be able to check if that stage has been already created or not ( in the other words it should avoid duplication in stage creation)

3)      Start and end Dates need to be validated while adding them.

4)      Every stage has an estimated end date assigned at the beginning of the project stage  creation and is equal to the planned end date which can be updated later on.( So we should not leave estimated end date blank)

5)  When one stage is done and we move to next stage, changes to actual end dates of the previous stages should not be possible.

6)      We MAY update the whole project end date.

Implementing Report iteration:

We have 4 kind of reports:

1) Customer report type 1 : Customer can review only his current projects(Customer can have only  up to 10 current projects). This report starts by searching Customer ID and then all CURRENT project belong to that customer should be avaiable to be reviewed  incluing their current stages, start date, end date,...

2)Customer report type 2: Customer can view ALL his projects(past and current),  with their details(start, planned end dates and  actual end dates). therefore a kind of historical report is expected to be viewd in this type of review.

3) Internal report type 1: A snap shot of ALL projects belong to a customer should be reviewed incluing their details(Current stages, start, end date,...)

4) Internal report type 2: The report should be about a particular project . This report starts by searching the project based on Project ID. We expect to sea currect stages(if the project is a current project) or completed/historical stages(If the project is copmleted).