Rimu Research
Home
Immediate Storytest Feedback
Coaching/Consulting
Paper and Talks
Background
Contact
|
Coaching/Consulting on Executable Specifications
The following are examples of what's possible. Consulting and coaching will
be tailored to your needs.
1. One Day Assessment
For teams that are already practicing agile techniques, including advanced
Storytest Driven Development.
- You've been using Fit and/or FitNesse for some time
- But you're finding that storytests are not working as effectively as you'd
expected.
|
You'd find it valuable to have an expert come in and assess your approach,
understand your issues, and make recommendations for improvement
A one day assessment of your team(s) can provide insight into your issues
(both known and to be discovered), on how to solve your problems, and how to
make a leap forward. The issues probably won't be restricted to your storytests.
|
2. A Few Days Onsite Coaching on Executable Specifications
For teams that are already practicing agile techniques, including advanced
Storytest Driven Development.
- You've been using Fit and/or FitNesse for some time
- But you're finding that storytests are not working as effectively as you'd
expected.
- You are interested in the latest thinking and approaches to developing
storytests with an emphasis on executable specifications.
- You want to start applying the latest approaches on your stories
immediately
Contents:
- A review of your current approach
|
Overview of executable specifications (why and how) to the whole team.
Half to one day coaching the customer team on writing storytests as
executable specifications, working with project stories
Half to one day coaching the developers on driving development from
storytests as executable specifications, driving the domain into the code
A variant of this coaching is available that's relevant to top-level agile
coaches and consultants who want to learn first-hand about the latest techniques
in executable specifications and how to apply them.
|
Multi-day Onsite Coaching on Executable Specifications
For teams that are already practicing many agile techniques, and are still
building expertise in Storytest Driven Development. Here's one
example. Contents:
- Present overview of executable specifications (why and how) to the whole team.
- Coach customer team for 2-4 days. Chose several stories to work on
that are coming up for development. Start with a simple example for the
first story. Initially I'll sketch Fit tables on the whiteboard and alter them as we progress.
We may start with a simple workflow if the Customers are used to use cases.
Then we'll write a second storytest for a variant workflow. Then we'll focus
on the underlying business rule and express that as a calculation rule. After we'd tackled a few
stories, the Customers will gradually do more of the development of the storytests. I
won't formally introduce the details of Fit tables, but will show by example what could be done.
I'll also show by example how to use
FitNesse.
|
Present talk with more detail of fixtures, etc to developers.
Coach programmers for 2-5 days. Start with two programmers on one of
the storytests. How to write fixtures. How to drive into the code. When to
start test driving with unit tests. Driving domain into the code. Resolving
differences between current code and storytests. Handling design smells.
Ongoing coaching, one day a week for several weeks, to locate issues and
to help with those
that arise.
This can take longer than initially expected because the storytests often expose problems in the way that the software
is being developed. Coaching in OO design, TDD, and domain design may be needed
as much as coaching in storytest
driven development.
I've carried this out this general approach with several organizations, with groups of from 15 to 60 people.
|
|
