Classic Web Portals Rolling Out

We've completed the main development of our web portals for our Classic product suite and have now moved into wide scale deployment making these available for all customers.

To date the major benefit has been teacher entry of attendance data with many teachers using their favourite smart phone (BYOD). The developers have optimised the attendance entry screen to work with any smart device. The teacher portal has also been released, with report comment entry and ability to view mark books and core student data. The full power of Classic is still best served through the main application, but routine tasks and looking up of basic information can now be done by teachers from anywhere* using any device.

Still waiting the first school (other than Mt Aspiring and Logan Park High School) to push out the parent and student access providing attendance, financial (just for the parents), timetable, NCEA and on-line reports for download. We've made it easy for schools to manage parent and student logins and remove the worry of managing passwords whilst maintaining security and control over access.

For more information contact us directly toll free on 0800 600 159.

Three things from MUSAC for Term 1

The three biggies from MUSAC for Term 1:

1. Support
2. Classic Web Portals
3. Edge

Support

• We're running free seminars nationwide each term. We come to your region. Any topics you'd like covered for Term 2 or if you'd like to host the seminar please let us know.
• MUSAC Agents are delivering more out of the box features and functions to support NCEA and National Standards
• We'll be attending all the usual annual teacher and management conferences to showcase our new developments. Stop by to learn how your school can benefit from them and provide feedback.

Classic Web Portals
These are web interfaces into MUSAC Classic. Enables web access for teachers to mark attendance from their favourite Internet connected device, view financial, pastoral and enrolment information. Next release will contain curriculum information and then finally the ability to enter report comments. Other parts for rollout Term 1 are student and parent access. In Term 2 we'll add VENIM for identity management out of MUSAC.

Edge
Our cloud based student management system has been named and branded. We will be promoting Edge through the year. Contact us now to find out more.

It's good to be back

Rest and relaxation with family and friends over the Christmas break is almost a distant memory. The team here at MUSAC starting rolling back on the 4th of January, support line opened on the 9th of January and we've now released updates to our web product, Classic and commenced roll out of the Classic Web Portals. Updates to Library and Financial Manager are imminent, and Phil and Ngaire are currently at Learning@School in Hamilton.

We are excited about 2012 with the formal release of our web product, the introduction of the Classic Web Portals and VENIM into the MUSAC product suite. The latter are being rolled out in limited release so we can meet demands - the portals themselves were tested in schools in 2011.

Following the popularity of the free MUSAC seminars in 2011, we're going to expand on these in 2012 - larger centres every term, smaller centres every second term and more remote places might just be the oncer. To keep costs down we'll be in touch to secure a host school in the region and we'll have Term 1 visits locked in and up on the website as soon as we can in February.

MUSAC Agents Edtech and Solutions and Services are also out in schools helping get the year started. Edtech and Solutions and Services have been working on ClassRoom Manager customisations with both having extensive Primary and Secondary graphing, analysis and aggregation capabilities. The key, obviously, is the conversation with the school about individual school goals and targets and ensuring staff are familiar and know how to use the functionality.

Boards will be wanting analysis of variance reports - MUSAC Agents can provide assistance if this is currently a chore.

Enough from me. It is good to be back. We're excited and energised about 2012 and look forward to continuing to be of service, meeting and discussing your ever changing needs and requirements.

Necessity: The mother of Invention

As you've heard, we're  developing a web product from the ground up. However, so many of our MUSAC schools do so much with Classic, particularly ClassRoom Manager, that it will be many more developer days of work before you'll wish to swap out to the fully online world. Timing of the roll out of of fibre another consideration.
In response to a request by his Principal at Mt Aspiring, web interfaces were developed (by Tim Harper) to:

• Enter teacher absences online (iPad, iPhone, Android, Apple platform/Linux platform ...)
• Teacher portal for school reports (further functionality available and being considered)
• Parent portal to see whats going on
• Student portal to keep informed

These tools are currently active in half a dozen schools - primary and secondary and we've sent a survey to a few schools to gauge the level of interest in MUSAC making these more widely available and supporting them. So far - lots of strong interest!

The idea here is that some schools want the best of both worlds - flexibility and breadth and depth of Classic plus a few basic web tools. When MUSAC's full hosted SaaS web product is deeper in functionality the school can choose to migrate. Those schools who don't use the breadth and depth of Classic will be more inclined to move to the fully web hosted system sooner.

At this stage we're in limited release with the web product, moving to formal release 31 March 2012. The product will continue to evolve and develop over many years. The above portals for Classic can be used until the web hosted product is developed enough for your school.

I expect to have a decision from the MUSAC Board at our next meeting (1/12/2011). I'll keep you posted.

MUSAC's Web based application: The story so far

We've been a little quiet about our web based application. We've had a number of focus groups (and continue to do so) and also a short road trip talking about our concept and vision. However, I thought I'd share the story so far as a prelude to greater depth of information about where we're headed and why.
MUSAC forecasted that the foundations for Classic that are serving us well would  need to change in the future and school expectations would evolve. In 2007, MUSAC completed a development of Symphony Attendance which was the first "Symphony" module. This module was SQL server based, latest in software technologies, windows application based and Ministry approved for Electronic Roll Returns. Sitting alongside this was eTrack, the Early Notification system. The intention was the new Symphony module would sit along side Classic performing synchronisation overnight.

This approach had a number of issues:

1. The schools we trialled it in really struggled to have anyone that knew enough about SQL server for us to be anything other than very hands on with installation and management. Equals cost and frustration for the school.
2. The batch synchronisation of live data scared me. Imagine enrolling a student in the morning but couldn't mark them in class until the next day -- unacceptable.
3. The pain MUSAC often experienced with schools was associated with poor networks and server capacity - this approach wasn't going to address that.
4. The wave of new SaaS and web based applications begged the question of the long term life expectancy of another in-school based application. I predict Classic has 5-10 years in it - I don't think this application would have been any different.

Furthermore, the expectations of the Ministry around Data Sharing Approvals were not going to be addressed for all MUSAC schools by the strategy we'd adopted. Namely:

1. Roll Returns
2. Electronic Roll Returns
3. SMS-LMS v1 (and now 2, soon to be 3)
4. Early Notification
5. Electronic Attendance Registers

The latter part of 2007 focused on addressing, in Classic, Data Sharing requirements, issues customers had shared with me in my first few months at MUSAC. Out of this came MUSAC Essentials and Premier, all of the above Ministry of Education approvals,  and work on single sign-on and a menu driven system for driving Classic (remove the perceptions of independent products) plus the mega installer. The risk profile of the Classic menu driven system became such we had to abandon that. I still hear from time to time that Classic is not integrated. Its not strictly true, but could look that way in terms of navigation.

At the start of 2008 I took a bold step and dumped the "Symphony project". We were going web based, end of story. A number of developers were already reasonably on top of the web concept and we invested in PD. We still had a lot of Classic work on - finishing single logon, unpicking the menu system and completing AB6 so all MUSAC schools had a compliant electronic attendance register.

By the end of 2008 we had a web concept, but our lack of experience in web based development was showing. Similarly, we had turned our development processes on its head trying to get away from the waterfall approaches to that of Agile. We knew this would be a much better approach. We got some external help to review where we were with the product and our processes. The reviews were not great, but the team responded beyond my expectations. We turned around in 3-4 months what the reviewer thought was a train smash.

In July 2009 we convinced three schools to have a crack at being beta schools for what was a very rudimentary web based student management system. What was important for MUSAC was to get real schools using and commenting on the product and feeding back into our Agile development lifecycle.
Latter in 2009, a non-target segment school convinced us they too should join as a beta school. This was a rather defining moment for us (always in hindsight!). Our plan was to get a product out that covered the bases of a Student Management system, but only just enough functionality. In 2010, this approached was slam dunked by this school. They were very clear that we needed greater depth and that they would rather wait for width but be able to totally rely on the beta product for specific aspects to be taken care of in totality. At this stage we had Electronic Roll Return approval and electronic Attendance Register approval. One of the best pieces of feedback in 2010 was when we received a call asking if the school had done Roll Returns correctly online - because it was so easy and hardly took any time to do.
At this time we had now been through 3 changes in the look and feel - I expect we'll continue to evolve this. The nature of the MUSAC team has also radically changed. More staff having more input into shaping all products. The management structure had also gone through a number of iterations of change and we also tried to ensure key people in the organisation were oriented to provide best value to schools and our agents. Our delivery processes are better and our phone system finally gives the team some real tools to work from. the support team from predominantly reactive to predominantly proactive and this journey has started.

In the background however, was a continual buzz of: "where is it?" "what is it?" "when can we have it?" "give me a date." At the same time, acknowledgement across the sector the predominantly things were pretty good with MUSAC in schools that had invested in PD and in development of the documents and reports that MUSAC agents excel at. Any conversation that starts with "MUSAC Classic can't ..." can usually be turned around to "let me show you how". I digress.
As we've pushed development of our web product forward, we've always had very clearly in mind that Massey University would host this. We knew conceptually that Massey was part of the KAREN network and were leveraging this to establish a campus fail-over system i.e. if Palmerston North was isolated, all other campuses could continue using IT systems without pain. That is our plan.

We've also continued being Agile and deliver an update to customers every month. Changes are then incremental and the schools grow with our additional functionality. We like this as we get fairly quick feedback, although it doesn't suit all - some like big bang delivery. In 2011, the team execution has been great and our delivery trajectory continues to reforecast ahead of plan. The real question is: Is this fast enough for those who want something different? MUSAC and the University is playing the long game. We now have a reasonably sustainable model and confident we can ensure a long term roadmap of continuous development and improvement - possibly something the Ministry was not so sure of around the time of accreditation.
So what can you expect from our web product this year?

1. A name (!) - internal joke ...
2. Approved as an Electronic Attendance Register (done)
3. Electronic roll returns (done)
4. Enrolments (done)
5. Recording and rudimentary analysis of Primary assessment tools (done)
6. NCEA basics (done)
7. General secondary assessment capability (next year)
8. The timetable algorithm from TTSM - (but not all the bells and whistles just yet!) (next year)
9. Essentials for timetable management (on track)
10. Basics of school/parent reports (done)
11. Course management (done)
12. Rudimentary student fees (by March 2012)
13. Basic Pastoral (watching the behaviour for learning initiative here i.e. PB4L)

What I've learned in recent years is that many schools don't scratch the surface of their student management system - irrespective of what flavour they ended up with. This makes the approach of when to pick up the MUSAC online product or is MUSAC Classic the better choice not so clear cut. What we do have is not only product but professionals across the country that can work with schools on their internal management processes and guide the school to best use their MUSAC software. I also believe that most schools want to see a real live person from time to time. Yes technology can deal with some day to day work - but education after all is a people thing.

I'll post up soon where our focus will be for 2012 and beyond and what we believe will differentiate this product forom others.

SMS-LMS v2.2 Update

Quick update on SMS-LMS v2.2. The addition of a more robust validation tool (Saxon for the technically interested), addressing of several defects and addition of 2.2 changes has been integrated and is now through to testing. The MUSAC Interoperability Control Centre (MICC, not to be confused with the Cricket Council) will also need regression testing as part of our standard process.

Next step is working with Watchdog and Edtech for KnowledgeNET, Moodle and UltraNET provisioning for target release of early October, as previously indicated.

LMS interoperability has been a long road for all vendors. As I mentioned, we waited until some of the dust settled before diving in, hence why it appears we're "slow". Our downfall was primarily that we did not have very good validation at the SMS end, else we would be in a better position now.

As I mentioned previously, we're looking to to take a more leading role. We believe we have wider support for an incremental change to the interoperability schema than more wholesale at this time. Of course, we also need to be looking ahead and establishing requirements for the future now so we can be ready.

Modern Learning Environments

With my many hats of MUSAC MD, Dad and BoT representative, I'm lucky to be exposed to similar issues and concepts in all the roles. One of those is that of Modern Learning Environments. Our school is looking to upgrade some classrooms to that more better suited to more modern pedagogy, I see my kids learning in ways that contrasts significantly with my primary school days and have recently heard the Ministry policy and seen an implementation of this first hand in regards to Modern Learning Environments.

With my MUSAC MD hat on I attended the SEO conference in Rotorua last week and sat in on the Ministry talk about Modern Learning Environments in relation to property. Yesterday I was in Auckland as part of a reference group which was hosted by Stonefields Primary School. We were given a tour and I assume saw the Ministry property policy (amongst others) in action.

I asked the teacher showing us around whether the new environment changed the way she taught or made it easier. Her response was both. She indicated that the new environment better supported the way she had taught in previous schools but was also contributing to changing the way she taught because the three teachers in her hub were able to observe each others practice and help each other improve.

Being some one who goes off on tangents and this is my blog ... I linked two other things I'm associated with/doing:

1. Reading Sir Ken Robinson's book on creativity "Out of Our Minds" in which he speaks of the stifling of creativity and Education being stuck in an industrial revolution paradigm. Stonefields Primary might sit on top of an old quarry, but they (like many other schools in NZ) seem not to quite fit the out of date model Sir Ken (with respect) refers. OK - I'm only up to chapter 6!
2. The great structure and scaffold around profession development of teachers and linkages with Initial Teacher Education (ITE) at College Street Normal school here in Palmerston North. Mr Kennedy has developed with his team a positive and proactive structure that leverages internal  expertise and teacher observation (peer and self review) to grow individual capabilities. Not sure if a case study has been written up, but had great feedback from ITE students on practicum in the school. Maybe at next years Inspired Impact conference?

My point. These modern learning environments seem to be a step in the right direction if the comments from the Stonefields teacher yesterday, the types of scaffold around professional development with peer review/observation that make a difference for students, over laid with the issues Sir Ken so eloquently portrays, are anything to go by.

Almost sounds like an endorsement of Ministry policy :)