Report for November 20
- Report Date
- November 2020
Achievements in Last Period
- Successful deployment of warning banner 4 Nov 20
- Communications plan for auto-forwarding completed agreed by project members
- Microsoft informed on 25 Nov 20 that the new rules would be implemented on 1 Dec 20. This not much warning for our comms but John had put together all the groups and policies required, for everyone who currently forwards and will do a doublecheck on this
- This means that anyone who currently forwards will see no difference, and anyone who doesn’t forward will no longer be able to set one.
Issues
- There has been feedback from the warning banner deployment which means some significant changes. Steve Hall has been asked to supply an estimate for these changes and is with Alex Carter to agree if they are to be completed as part of this project (which means reviewing the budget) or as BAU
- Comms plan and comms test still to be agreed by Alex so we have switched the auto-forwarding to ‘allow’ meantime until we can get the comms out. It will then be switched back to ‘automatic’
Next Steps
- Submit piccl to revise delivery and closure dates
- Alex Carter to agree where warning banner changes to be made
- Alex Carter to approve comms plan and comms text for auto-forwarding
- Agree date for auto-forwarding comms to go out
- Comms to be distributed
- Auto-forwarding status reverted to ‘automatic’ after comms out – date to be agreed
Milestones
D2.1 Block Rules to prevent Auto-Forwarding |
30-Nov-2020 |
Project Closure |
10-Dec-2020 |
Project is AMBER
- Approved budget
- 110.0 days
- Activity this month
- 3.0 days
- Activity this year
- 25.0 days
- Activity to date
- 101.0 days
- Estimate to complete current year
- 9.0 days
- Estimate to complete future years
- 0.0 days