Iteration 7

Initial planning session with the MAD team - if all goes well, a ES, CP and BP should be delivered in this iteration from the development side - however, the time frame does not allow for adequate testing before the end of the iteration.

Summary of discussion points

• AA to follow up (later next week?) with how the heck are we going to  test of the CT
•  DKto investigate / add a task for the Get Locality ES
•  I’ve already spoken to DM regarding scope and learning curve for this iteration
• The Bug fixing tasks have 0 hours estimated – I will follow this up with AW / DW and the BA’s to determine a good way of estimating this task.
• MJ raised concerns regarding the development of the CT transactions at the end of the process, as opposed to in conjunction – this probably needs to be followed up with the developers (MJ?)

TFS - Update Membership - Completed

Lots of pain, hopefully long term gain.

The existing UpdateMembership in TFS is now set up correctly, the next stages are to get some hour estimations against the tasks, to determine what we can realistically achieve in the next 2.5 weeks.

I still need to add the remaining stories, and tasks to enable a full view of the UpdateMembership scope.

Issues and Spikes - Process Flow

A proposed process flow was circulate to the team today, with the aim  of this process is to isolate the time spent on spikes, rework and issue investigation from the ‘normal’ development time, and to provide additional visibility of the impact any issues are having on the project.

TFS - Update Membership Changes

The changes continue - still updating the existing stories and tasks - not sure about the value of this rework yet again - can't say I'll be happy if we change it up another time.

Most of the tasks have been entered, and assigned to the correct person and iteration - a few more hours in the morning should get the Update Membership in a position to add hour estimates to the task.

TFS: Update Membership Changes

The new TFS structure for Update Membership is partially implemented.

All the old stories have been renamed, and where redundant closed, or set to removed.

There are still some legacy tasks, and the test cases and acceptance critera may no longer be on the correct story, so there will be further work to be completed to ensure that TFS correctly reflects the scope of the work to be done, and the scope of the work that has been completed.

Standup 5/8/2014

First Daily Standup new team

DK - Iteration Mgmt tasks in TFS

1. Set up Iteration 7 Tasks
2. Update UpdateMembership new tasks and rename tasks based on MFS story spreadsheet

DK - Project Level tasks

1. Consolidate Rework Stories
2. BP Maps for remaining stories (Benefit Statements, Documents, Mem Communications

MJ - Comms Container work to complete (I6 holdover)

MJ - Membership Container work to completed (DK to find or create new story / tasks)

AN - Issues testing with Soap Sonar, JP  advises network issues, traces have been setup

AN - Testing documentation and Project level testing strategies