Iteration 3, Increment 1, Day 2

Date: 23-09-2011
Venue: Sheppard Library
Meeting time: 11am - 2:00pm
Attendance: Aylin, Sara, EdwardCustomer reporting - First Stage done

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,...

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.

Other Feeds

Development Notes:

• CreateProject page need to be link to ProjectDetails page after creation
• Project End Date should be editable in the ProjectDetails page
• Add ‘actual end date’ to the Project Details view (which takes value from last stage`s end date)
• Display name of the next addable stage in AddStage page.

Iteration 3, Increment 1, Day 1

Date: 22-09-2011
Venue: Sheppard Library
Meeting time: 11am - 3:00pm
Attendance: Aylin, Durand, Edward

Redesign of Project Management Stage creation

Move creation to separate page

Perform Validations - Ongoing

Report Screen Drafts - Done

Reporting Using Asp.NET - Solution found, implementation on project yet to start

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).

Iteration 2, Increment 1, Day 2

Date: 16-Sept-2011
Meeting time: 11am - 3:30pm
Attendance: Sara and Edward

Meeting time for sub-team A, at the end of the day, the task status was as follows

User Interface/Section	Tasks	Status
Project Details Page
	UI Design	Done
	Get Customer Details, selected site details and selected project details from search page.	Done
	Update project end date and stage end date in database.	Done
Add Site
	UI redesign	Done
	Save new site details into database	Done
	Get customer details	Done
Site Details
	UI Design	Done
	Get Customer Details, selected site details and list of projects from search page.	Done
	Update site details to database.	Done
	Included check box to update correspondence site
	Added links to view site details, back , home	Done
Create Project Page
	Included jquery calendar for date fields	Done
	Did NULL validation of all required fields	Done

Iteration 2, Increment 1 Day 1

Date 15-Sep-2011
Meeting Time: 11am- 14:30pm
Venue: Sheppard Library S223
Attendance: Aylin, Durand, Edward

Meeting time for Sub-Team A. By the close of day, task status was as follows

Create Project Page	Tasks	Status
	UI Design	Done
	Get Customer Details and selected site details from search page.	Done
	Save project and stage details into the DB.	Done
	Prompt User to confirm creation of project.	Not done
	Validation of project and stage fields.	Incomplete
	Get Customer Details, selected site details and selected project details from search page.	Done

Project Details Page	Tasks	Status
	UI Design	Done
	Get Customer Details, selected site details and selected project details from search page.	Done
	Update project end date and stage end date in database.	Incomplete

Iteration 2 Plan, Reflective Workshop, Methodology shaping session

After yesterday's meeting with end-user and gathering the necessary requirements to progress into the 2nd iteration, we were back to have our iteration plan.

Reflective Workshop

We held this session to identify our working habits, see the things we are doing right that we should keep, those that we should try and the the problems being encountered. Below is a summary of what was collected from the session

Keep These	Try These
·        Effective communication habits	·        Personal Safety
·        Daily stand-ups	·        Frequent feedback on part A – Weekly
·        Pair programming	·        Adjust time to cover for work load
·        Assign development tasks	·        Have agreed screen designs ready for all before development
·        More documentation	·        Provide template document for teams to fill during tasks
	·        Introduce voice recording during feedback with permission
Problems
·        Not enough feedback time on Research section

Method Shaping (Methodology Shaping in Crystal Clear)

Alistair Cockburn,  Crystal Clear 2005

Here is a refined process cycle we ended up with after discussing the terms such as what a delivery, iteration, increment , integration should be in terms of our project. 

Refined Process cycle - Courtesy Alistar Cockburn

From the above, we consider our whole project having one delivery with 3 iterations. We replace the terms integration with the term increment based on our understanding and considering the process diagram explanations in Alistair's book (pp 116). We have therefore had to update all references to these terms in our documentation.

Iteration 2 Plan

After using the blitz planning technique to identify all the needed pages and functionality, we divided the tasks once again according to sub groups and scheduled development to start the next day. These outputs were however ready by the close of day

 Database Tables - Task Done by Durand

•  Project Table 
•  Stage Table 

 UI screen drafts - Done by Aylin

•  Add Site Page 
•  Create Project Page 
•  Project Details Page 
•  Site Details Page  

Iteration 2 Requirements Gather

After meeting with User on iteration 1, we were poised to start the 2nd Iteration. Below is the requirements specification we gathered from end-user.


• Create Project Page, Specify start and end dates of project
• Allow for update on end date only
• Create project stages. Project stages are of four pre-defined types, Start-up, Initiation, Testing and Documentation. Projects have ids and project stages have ids.
• On Stage creation, specify stage start date and end dates

Additional team suggestions
1. Update Class and Entity relationship diagrams
2. Update database table

Iteration 1 User View and Feedback

Date: 13-09-2011
Meeting time: 1:00 pm - 2:00 pm
Venue: TG 11 Office
Attendance: ALL  + Steve

Meeting was held to show the status of work regarding iteration 1 as well as receive feedback on PART A. We were able to show documents for History of OOA/D , UML, Agile MDA/ MDE, Comparison of Agile Methods. Feedback received identified several errors that have to be amended in the research though he was pleased we presented something.

Feedback of the system developed so far showed so satisfaction from end-user. Minor changes requested and  new requirements given from Iteration 2 on Project Management.

There seems to be a confusion of terms regarding iteration and increment, delivery etc. We plan to hold a method shaping in order to clarify these issues amongst the team.

Details will be looked at in the next group meeting, here is a brief overview of some change requests noted

• Customer Details Page: there will be a options only as button or link for Add Site, Update Customer Details, and Update Existing Site Details.
• Site Management on the main page will go under Customer Management and
• Our third Heading will be View and Reporting

And 2nd iteration is Project Management 

• Creating Project (going to include Customer details while adding Project)
• Update Project / Updating Estimated Actual end date
• All three codes (Customer, Project and Site) will some how combined

Next meeting: 14-09-2011 11:00 am

Iteration 1 Plan and Status Documentation

Here we have tried to come up with documentation to indicate the progress or work for this iteration


DELIVERY 1 - ITERATION 2


End user feedback and change requests

1. Remove edit/ select from grid view
2. Customer search option
3. Correspondence site among customer sites
4. Create site together with customer
5. No View for customer list
6. Add site link to main page
7. Prompt user for confirmation before creating customer
8. Modify menu on main page

Additional team modifications

1. Customer codes should be alphanumeric and sorted
2. Include detail view

DELIVERY 1 , ITERATION 2 PLAN  

Planned Duration	Planned Start Date	Planned End Date
3 days	30th Aug 2011	2nd Sept 2011
Actual Duration	Actual Start Date	Actual End Date
5 days	30th Aug 2011	6th Sept 2011

GROUPED TASKS AND ASSIGNMENTS

Sub-Team A:      Durand and Aylin

Sub-Team B:      Edward and Sara

	MODIFICATION TASK	USER INTEFACE	ASSIGNED TO
1.1 1.2 1.3	·         Modify menu structure ·         Include Add site link ·         Customer search link	Main Page	Sub-Team B
2.1 2.2 2.3	·         Create site together with customer ·         Prompt user to confirm creation of customer ·         Sorting - customer codes and site codes	Create Customer Page	Sub-Team B
3.1 3.2	·         Remove Edit /Select from Grid view ·         Include Details View	Customer Details Page	Sub-Team A
4.1	·         Customer Search on code and name	Search Customer Page	Sub-Team A
5.1 5.2	·         Create site for existing customer ·         Add Correspondence site among customer sites	Add Site Page	Sub-Team A

DELIVERY 1, ITERATION 2 STATUS

	MODIFICATION TASK	Status	Date Completed
1.1 1.2 1.3	·         Modify menu structure ·         Include Add site link ·         Customer search link	Done Done Done	31/08/2011 30/08/2011 30/08/2011
2.1 2.2 2.3	·         Create site together with customer ·         Prompt user to confirm creation of customer ·         Sorting - customer codes and site codes	Done Done Done	30/08/2011 30/08/2011 30/08/2011
3.1 3.2	·         Remove Edit /Select from Grid view ·         Include Details View	Done Done	30/08/2011 31/08/2011
4.1	·         Customer Search on code and name	Done	02/09/2011
5.1 5.2	·         Create site for existing customer ·         Add Correspondence site among customer sites	Modified – included in Customer details Done	02/09/2011 31/08/2011

Final Integration and Mop-up:   06 Sept 2011

Iteration 2 Timeline and cycle breakdown