Report for October 2016

Report Date

October 2016

Achievements this period

• De-duplicated and categorised user stories
• Issued completed user stories summary to workshop group 
• Input user storis into JIRA Agile tool
• Assigned priority levels to each user story in conjunction with Product Owner
• Proposal put forward (with decision made) for software development platform and related architecture

Issues

• The Foundations milestone has been missed because of the time taken by Student Systems to make the decision on the software development platform and related architecture; the milestone date will be reviewed with the project sponsor in light of required resources and the approach.  This impacts on the start date for development iterations but does not yet impact on the overall project delivery date

• Although a decision has now been made on the architecture, this must be translated into an ADA document and a number of questions were raised relating to data and roles, so these must be analysed and confirmed before we closed the Foundations stage

• The developer resources will have to re-booked because of the delayed start to development iterations

• The Technology Management or Applications Management had not yet been booked because the architecture had not been decided; now that it has, these resouurces will be booked

• Unclear BI/MI requirement - A BI/MI requirement was discussed at the project brief sign-off meeting but the nature of the requirement was unclear and will require to be clarified following further analysis of the user stories.  It will also require to be prioritised appropriately for inclusion.

• No clear QA data specification on student hub/dashboard - Jamie Morton, Project Manager for Dashboards project, presented some mock-ups to a selection of School Quality Directors in October.  Initial feedback seemed positive.  I sent Jamie a list of user stories categorised as 'Analysis Tools' but my initial feeling was these stories were more for the new QA system, not the dashboard. 

• No QA Director in place for 3 Schools within CAHSS following collegues stepping down or lack of volunteers.  Whilst not essential to this project, the Product Owner is working to fill these roles as they form a key group of stakeholders for the new system.

• No appointments yet for User Group Representatives for Programme Director and School Quality Director roles, conversations taking place with Robert Mason (Product Owner) to resolve

Next steps

• Complete prioritisation and estimation of user stories
• Decide start date for development iterations
• Appoint the remainder of the core Agile product team - including the User Group representatives
• Write Application Design Architecture (ADA) document