Is Crank agile? We like to think so. However, perhaps more importantly I think that we are very pragmatic. We are passionate about the product, but not to the point where that passion turns into code teritoriallism.
Collectively the team at Crank has been doing embedded software development for over 50 years and are all seasoned veterans of the code trenches. We understand what bad code smells like and aren't afraid of getting into heavy refactoring to clean the code paths.
While we were developing the Storyboard Embedded Engine we made sure that our internal development milestones included what we called Shark Week, a week dedicated to tuning and performance of the engine. If features of the engine weren't turning out as planned or simply weren't being used ... we cut them out entirely, figuring that polluting the code path with baggage at this point was more costly than the time to step back, re-evaluate and re-code.
Storyboard is approaching it's second internal milestone (M2). Storyboard can map to all of the features of the embedded engine, supports action, render and event plugins and can completely round trip the existing embedded engine configuration files, importing them into the design tool for manipulation and then re-exporting them back to be executed by the engine.
Just like Shark Week, we are taking the time after M2 to run through a use, review and revise period; in other words we're sending Storyboard to Beauty School. As long as the developers don't break out in song then we should be posting some Storyboard screenshots in the next few weeks after it goes through its own visual make-over.