Skip to main content

Fingerspell Flashcards - Done :-)

Done. This brings me to my own little pet project, the FingerSpell Flashcards.

I have a hobby. Sign Language. There is really no reason for me to have this hobby, but I have long been curious about using signs as a means of communication.

There are a lot of challenges in learning a sign language, one of which is the speed in which native speakers can sign — I suppose that's not that different from a learning a spoken language, actually.

The finger alphabet is not the same thing as the sign language. Sign languages are a much more efficient way of communicating ideas than simply spelling out words. The alphabet is still important and is used mostly for names and places, but also for words that don't have a dedicated or well-known sign.

Not finding a good tool for learning to finger spell, I wrote one. It was a double learning experience: I have gotten much better at finger spelling and I got to cut my teeth on AJAX. After showing it to colleagues in class, I was really motivated by their reactiosn to polish the program and put it on the web or even commercialize it.

So it needed a better visual design. It needed to do address a wider community so it needs to be multilingual, not just the text on the web site, but it needed to support American Sign Language (ASL), French Sign Language (LSF), German and Swiss German Sign Languages (DGS and DSGS). Each has its own alphabet. The list of wonderful features got longer and longer, and it seemed like the program would never be finished.

And then came jp's email. Eureka! Focus on getting it done!

This 'done' means more than just getting the features done. Done means the product is out there producing a return on investment. And there were plenty of cool new features to implement. So getting to done meant shortening the list.

So I thought - prioritize. What does it need to be releasable, what can be postponed to a later release? Here is the list I came up with:

Version 1.0
  1. A user can choose between ASL und DSGS signing languages
  2. An ASL user can display words from a database of US names and places
  3. An DSGS user can display words from a database of Swiss names and places
  4. A user sees the pretty new pictures Hans Peter, Norbert and I created
  5. *A user understands the licensing conditions (Creative Commons)
  6. *A user who appreciates the service can make a paypal contribution
  7. *A user can enter a word to be fingerspelled from the keyboards
  8. *A Windows User can see the screen properly with Internet Explorer
The first three points have been working for a while, the rest, those with a '*', while not a lot of work, needed be done, and with this feature set, I would be willing to tell the world about it.

Version 1.1:
  • A user can use the site in German
  • A user can use the DGS Alphabet
  • A DGS user can display words from a database of German names and places.
Version 1.2:
  • A user can use the LSF Alphabet
  • A LSF user can display words from a database of French names and places.
Version 1.x:
  • User contributions go to a new paypal account
So I was able to push a lot of work into the future and today, version 1.0 is done. Thanks to the joys of Internet Explorer, I am not sure if got all rendering issues fixed (css patches would be most welcome), but it's working well enough, that the time has come to set it free.

So where's the ROI on a project like this? Well, mostly this is about the satisfaction of having a cool tool out there, learning some interesting things along the way, and hopefully helping a lot of people learn to sign. I have no idea whether the donation model is a viable way of financing software, but shareware has a long established tradition, so we'll see. But if it weren't out there, I'd never find out.

So here goes! Version 1.0 is officially live.





Comments

Popular posts from this blog

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …