Hi Lukas, hi Bill, ( and JJ)
A good user story gathers resources to it. And the ball starts rolling.
Next two things are needed. Roles need to be negotiated. Someone needs to play the user. And others the developers. The user role has to entail carrying the flame. I think of this at the This-Shall-Be-Done-Bit. If the flame goes out or the Bit gets dropped then the project ends. So these must be guarded carefully.
It is also the users duty to determine and apply the acceptance tests. When the tests pass to the Users satisfaction the project is essentially done. Then we pound on the harvesters/release teams to get the code adopted into the squeak stream.
The developer role is creating the code that gets closer and closer to what the user wishes for.
Second, all along the creation there needs to be a communication between the developer and the user. The developer role is to Know-What-Can-Be-Done (easily and quickly). And for finding out from the user if the results are acceptable and what still-needs-to-be-done.
User stories are nessecarily vague. They are meant to be modified as the experience of implementation experiments informs the knowledge of the user and developer.
In the context of squeak development we often lose sight of the two roles with the developer also being the user or vice versa. Even so, its good to remember the two roles are different. It is also good when there are two people to take the separate roles (even if they switch roles at times during the project). It keeps things clear.
Start with a short user story. ( e.g. kbd focus) Then... Lukas Renggli renggli at gmail.com Fri Dec 15 07:01:49 UTC 2006 wrote:
Bill Schwab BSchwab at anest.ufl.edu Thu Dec 14 22:44:02 UTC 2006 wrote:
Squeak's lists are far too eager to grab keyboard
focus. I am
(slowly!!) working on a fix (see MouseOverMadness.cs
on Mantis), Hi Bill can you supply a url for this code? To me mantis means the bugtracking stuff. And I searched that but couldn't find anything to lead me to your code. -Jer
and
Doug Way (IIRC) provided some very useful
constructive criticism of the
first draft. Feel free to beat me to it, or to
organize a larger effort
to get this right.
Great to hear that there are people working on improving the usability. Continue!
If you need a tester, I can help.
Cheers, Lukas
squeak-dev@lists.squeakfoundation.org