October 30th, 2012

What's on the Horizon with Agilo for Scrum?

by Thomas Bradford

Agilo for Scrum started off as a very simple concept. We wanted to create a very focused tool whose only purpose was to facilitate good Scrum practices. This remains our goal, though along the way we've battled some major performance problems in our client side implementation.

For some time, we engaged in this battle by attempting to optimize our code against the framework that we chose to implement our client side UI -- Sproutcore (version 1.4). This worked in a way, because there are some simple things one can do to squeeze significantly better performance out of Sproutcore, for example avoiding deeply nested Views helps greatly.

But eventually we hit the limit of what we were able to accomplish with Sproutcore, and the minor performance gains we were able to realize did not justify the amount of effort we were putting into generating them. It became clear that our options were either to migrate to a newer version of Sproutcore that promised greatly improved performance or to abandon it altogether.

Both options seemed to be rather painful, but in the end we decided to wash the taste of Sproutcore out of our mouths and chose to abandon it for greener pastures. Specifically, a decision was made to avoid all-encompassing frameworks altogether and instead adopt a combination of focused libraries that addressed our individual needs. The reasoning for this is if we found a library lacking, the pain involved in replacing it would be significantly less than having to replace an entire framework (again)!

Knockout was chosen as our Model/View library, jQuery UI for Widgets, jQuery for DOM manipulation, Crossroads for local URL routing, Agilo Software's objeq language for Object Querying, and plain old HTML5/CSS3 for everything else. And what has the result been? Well, we've been able to achieve exponentially improved performance, more easily maintained view code, and a greatly reduced client-side code footprint overall.

You may be asking "So when do we see it?"

And the answer is "Soon"

But in the mean time, feel free to explore our Technology Stack:


Thomas Bradford

blog comments powered by Disqus