SE401:Group58:ActionListBacklog

Main Menu	Work Plan	Progress	Research Backlog	Functional Backlog
Meeting Minutes	Supervisor Meeting Minutes	Sprint Log	Conference	Poster

Action List History

[24/09/08]

1. Finish off compendium

2. Write contents of compendium to disc

[11/09/08]

1. Finish off final report

2. Finish off poster

3. Print poster

[3/08/08]

1. Need to do retrospective for sprint 3

2. Need to get TANDBERG's feedback for the result of sprint 3

[16/07/08]

1. Need to get TANDBERG's input for the Sprint 1 results and input for Sprint 2 Requirements.

[10/6/08]

1. Llyle: Create Silverlight DAL API which will wrap the TANDBERG API and be used to mock while we sort out the Cross Domain and Meta Data issues currently being faced. All logic must be under unit tests.

2. Weng Hao: To create a Video player interface. Be careful not to make the view too thick (if in doubt ask me please). Design with a Presenter First methodology in mind. All presenter logic must be under unit tests. Mock test as appropriate using Rhino mocks 3.5 (again if in doubt please ask me).

[14/5/08]

1. Llyle: Create a C# / Java proxy which communicates with the TANDBERG content server. This does not incorporate the Silverlight application as the aim is to check if the server can or will communicate with a server given current settings.

2. Weng Hao: Keep trying to make the example work. If it work then record the steps taken to make it work. (for future reference)

3. Add minutes to Wiki

[9/5/08]

1. Put current modified example in the shared repository under source control.

2. Connect the example to the content server and achieve media streaming from end point to example.

[3/5/08]

1. Complete Research Topics on Research Backlog before [3/5/08 6pm]

[30/4/08]

1. Fiddle with the example given by Tandberg before [28/4/08].

• Hence before the first iteration so that we are somewhat familiar with XAML, Proxies and Cross-domain issues.

2. First client meeting with Jesse (from Tandberg)

• He will be adding features to the feature backlog developed from the requirements meeting.
• He will be responsible for the reprioritisation and modification of all features on the feature backlog.
• He will be responsible for OKing the final feature backlog at the end of the meeting. (A verbal "This feature backlog is what I want" is good)

3. Incorporate the research iterations into the work plan.

[24/4/08]

1. Push out the first iteration until Monday 28 April (reflect on Work Plan)

• The hardware did not arrive in time for the first iteration but we expect all the initial "stuff" to be sorted before [28/4/08]

2. First client meeting with Jesse (from Tandberg)

• He will be adding features to the feature backlog developed from the requirements meeting.
• He will be responsible for the reprioritisation and modification of all features on the feature backlog.
• He will be responsible for OKing the final feature backlog at the end of the meeting. (A verbal "This feature backlog is what I want" is good)

3. Fiddle with the example given by Tandberg before [28/4/08].

• Hence before the first iteration so that we are somewhat familiar with XAML, Proxies and Cross-domain issues.

4. Incorporate the research iterations into the work plan.

[12/4/08]

1. Weng Hao to do his allocated prioritisations
2. Expand apon the Research Backlog (Prioritise and add estimated duration as you expand)
3. Get ready for first iteration

[10/4/08]

1. Prioritise allocated Categories, and give an 'Estimated Duration'. (Person's name is next to category to 'do' in Research Backlog)
2. Add to 11 April Agenda Meeting List
3. Expand apon the Research Backlog
4. Pick Research Item and do the research. Write the results on a page that links to the prioritised entry in the Research Backlog. Make note of time spent and note this on Prioritised Research Backlog under 'Actual Time'.

Prior to [9/4/08]

1. Work Plan Breakdown
2. Give Prioritisation Levels a Color and create a Prioritisation Color Box. Use imagination. Hopefully to right of screen like the T.O.C
3. Create the Prioritisation Table Structure. (Possible headings: "Title", "Target", "Estimated Time", "Actual Time", "Priority")