October 21, 2008 – 4:45 pm by Nathanael Boehm
I’ve been working on-site with the co-located development build team for a week now although I’ve been back and forth between the two offices quite a bit over the past three weeks. Things are moving at a rapid pace - we have three streams of work occuring simultaneously with detailed design and architecture documentation and modeling across the database, data management tools, public websites and web services.
The project team including developers, architects and project managers with our vendor as well as our own people and contractors now consists of 21 people.
We’re also entering an intense stage of stakeholder consultation and engagement which includes utilisation of mailing lists and on-site visits around Australia; Marty, Leanne and Alison have been travelling this week kicking off this round of engagement with RTOs. I’ll probably be travelling to Adelaide next week to help out with that stakeholder consultation as well as firing up the web services mailing lists. I have a draft version of the web services spec on my desk for review - it’s currently around a hundred pages.
We’ve changed the model slightly so the specification includes all three web services interfaces so I’ll just have to figure out a way to pull out the relevant sections of that document to circulate to Industry Skills Councils, Registering Bodies and third parties (software developers) as part of the external consultation.
Also reviewing the Master Test Plan which details how testing for each of the system components will be conducted and working with Leanne our project coordinator to fit the system testing in with usability and accessibility testing as well as user acceptance testing (UAT).
What is user acceptance testing? Basically the purpose of UAT is for the client or user to determine for themselves that a certain component is fit for purpose. The functionality should at that stage all be working and defect-free so nothing should break, but it’s about making up your mind and having confidence that it is actually good to go. Now, considering that the project team are not the end users of many of the components of Training.gov.au we’re going to be inviting some of our stakeholders to be involved in that user acceptance testing.
Not sure exactly what the format of that testing will be - whether we’ll send you a link to a testing environment for you to “play” with a certain piece of Training.gov.au or whether we’ll come out and visit you and ask you to go through several business scenarios so you can familiarise yourselves with the entirety of a component to the point where you can say that you are confident it’s ready to start using.
Given the quick turnaround times on UAT in the project schedule we won’t be able to get to everyone who’ll be using each of the interfaces and sites and in some cases we might only invite a single person to be part of that process - however we also will need real end users to help with usability testing too. If you specifically want to be involved in either of these testing phases please get in early and let us know now so we can plan accordingly and try and incorporate such requests into our travel schedule.
Tags: build, development, engagement, RTO, staff, stakeholders, team, testing, travel, uat, usability, useracceptance, webservice
Posted in RTOs and training professionals, Software developers, The project | No Comments »