Bugtracking

“Flex”ing Development Muscles…

So, I bet you thought I was going dark again since it’s been almost a month without a post.

Actually, there’s been some moderate activity on the Flash For Learning grouplist. Not a ton of activity, but while there are many Flash developers and designers doing E-Learning, there’s probably not too many who are vocal. In the first month since the list was launched, we’ve got about 25 subscribers and maybe six people who post so far. Everyone’s in the same boat, realizing that there isn’t much out in the wild web on gearing Flash and related products for E-Learning. One of the members of the group is working on a full-on ActionScript class to handle the API communicaiton with SCORM. I’ve been hard at work doing something pressing that I’ll open up when I have it working.

Remember a few months back when I wrote about QA? I got a QA entry linking to a database working right out of Articulate Presenter as a tool in the upper right-hand corner. Honestly, it’s just a link to a URL, so it could be linked to anything, but the point is I have it working out of Articulate, using the LMS to provide your name when you enter a bug and Articulate to auto-fill the slide number you’re on, so all you have to do is tag what the problem is with keywords and then write a detailed description of the problem, and submit. The last week or two, I’ve been working on the management system to handle all that QA data, and I’m using it as an excuse to learn Flex 2 and AMFPHP 2.0 (currently in 1.9 beta 2). It’s fast, it’s effective, it’s efficient, it’s clean and neat — I’m surprised at how easy the combination of Flex 2 and AMFPHP 2 are to develop with. If I had tools like these when I was knocking out my first e-learning apps in 2001… well probably nothing would be different, but it sure would’ve been easier.

I’m currently gathering requirements to produce a learning game for my company. I won’t be developing it myself as the scope is just way too large for one guy to tackle. Right now we’re buying some serious games and we’re going to play and evaluate them at the same time we build the momentum from the businesses that will be served by this learning game for championing the project and get stakeholders identified and on-board. If anyone has experiences they’d like to share on the learning gaming front, I’d love to talk to you, as it’s completely foreign to me which makes it interesting to sell the idea of it to more conservative corporate types.

So this post isn’t really saying much except I’m alive, I’m active and communicating and there’s some pretty cool stuff going on that I’ll post here and on the Flash for Learning group.

Articulate
Bugtracking
Development
Flex
Productivity
QA

Comments Off

Permalink

Thoughts on Strategy: Tracking Bugs

I’m beginning to love the challenges of this new job.� I hope the love affair lasts.

There’s a couple of things I’m digging about the new job.� One is that the more strategic role I have in the� new job’s� Learning Center provides me with the opportunity to blog professionally again.� When I’m thinking through some of the issues I’m working through (content life cycle strategy, repository management, rapid learning development, aligning learning objectives to business performance goals, etc), it helps a lot to have a place to journal.� Hopefully, my sharing helps other learning, training and performance peers (and peeps, yo) that are in the same spot as me, or even further down the long tail.

So yesterday I was assigned as the “designer” on two courses currently in the last throes of review.� What that means in this scenario is that I have to review the content as both an ISD and as a technical reviewer, making sure that the content works as intended.� We don’t have a process defined for this kind of review.� We don’t have specific criteria defined to base a review on.� We don’t have a format in which feedback from such a review should be in.� We don’t have post-review actions defined.� It’s not like this team has never reviewed courses for delivery before.� It’s just not a clean and consistent (or necessarily understood) methodology for producing consistent quality training.

Guess who’s job it is to set the process in place and get the stakeholders in such a process to take ownership of it? :)� I love it.� It’s a good challenge.� It’s a good place to see impact, both positive and negative, of what I’m bringing to the table.� I think it will be pretty validating (or a really powerful gut-check, but let’s be optimistic).

Admittedly, I was never interested much in process, or quality measures and things like that.� But I never understood the impact of QA like I do right now.� So, I’m going to start with what I know and rely on the better practices I saw at CTC (and specifically ADL, which has probably the strongest quality process I’ve ever seen).� The first thing I can do with minimal buy-in necessary is on the tech side.� I need to define a consistent methodology for tracking bugs and defects in these projects that can be shared, archived and searched quickly and easily.� So I’m going to evaluate BugZilla on my own this weekend, and if anyone has ideas on other tools that can be pretty much off-the-shelf, please comment on this post.� I can certainly build my own php/mysql bug tracking solution that will be adequate enough, but it’d sure save me some time if I didn’t have to build it.

Basically, what I need is to be able to track each page/screen of a content object, as well as global issues relating to the content object as a whole.� The range of issues can be technical (e.g. content not initializing the SCORM API) to grammatical issues to instructional (e.g. the branching of a given scenario needs to be redefined).� I also need to be able to organize people either around a tool, or customize the tool use around the QA team’s roles.

A must is a way to integrate into content so that each page can launch a contextually relevant feedback form, so any reviewer can enter and view tickets related to the current screen.

Bugtracking
Development
E-Learning
Instructional Design
QA
Strategy

Comments (1)

Permalink