Completion Report

Project Summary:

This project has significantly improved the document of agile methods within Applications Division.  It has also configured and documented JIRA Agile, which has been of huge benefit in supporting agile projects.

The original objectives of the project were as follows:

• enhanced documentation of the methodology for agile projects within Applications Division - delivered
• configuration and documentation of JIRA Agile (previously known as Greenhopper) -delivered
• further training materials, sufficient for a one-day workshop training Apps staff and customers in agile technique - mostly removed from scope
• delivery of four training days - removed from scope
• setting up a practitioner's group and preparing its first meeting - not delivered

The enhanced documentation is included in the documentation for Agile projects: https://www.wiki.ed.ac.uk/display/insite/Agile+project+organisation

As noted in Issue 1, the project scope was extended to upgrade the version of JIRA that we use to JIRA 6.1.6. 

As noted in issue 3, the configuration of JIRA Agile took more time and effort than planned.  To compensate for this, most of the tasks to produce training materials and deliver training were removed from scope.  A training session was delivered for Production Management team leaders on their role in the agile process and a short overview session was given to Project Services to help them understand the pros & cons of choosing the agile methodology

In addition to the documentation, the project also delivered project estimation templates for use in the annual planning process.

The core of the project was completed by October 2014.  The project code has been used since that date to record small ongoing improvements to the documentation.  Some form of time recording code will be needed for this ongoing maintenance and improvement.

Analysis of Resource Usage:

Staff Usage Estimate: 45 days

Staff Usage Actual: 63 days

Staff Usage Variance: 40%

Other Resource Estimate: 0 days

Other Resource Actual: 0 days

Other Resource Variance: 0%

Explanation for variance:

The project scope was extended to include an upgrade of JIRA.

Configuration of JIRA Agile took longer than expected.

The project was kept open in order to allow ongoing improvements to the documentation.

Key Learning Points:

JIRA Agile has been a significant benefit for the division and our business partners.

Time is required each year to keep development tools up to date.  This is now provided by a an annual upgrade compliance project.

Outstanding issues:

Time is also required each year for ongoing maintenance and improvement of documentation.  Divisional management need to agree a method for recording such time, such as an RDS code.

It would be useful to review the Agile documentation with Production Management to determine whether any changes or additions are required to support their needs.