This lesson will step you through how to conduct a Bot Behaviour Field Trial, which involves the identification of existing and new behaviours.
- Behaviour Identification Guidelines
- External Resources - GearUp Prototype (Demo App), Behaviour Field Trial Matrix, Behaviour Field Trial Presentation Template
The Bot Behaviour Field Trials help us determine how a set of behaviours cover common business requirements through the process of Continuous Modernisation.
We can use it to:
- Match interactions to behaviours
- Determine potential Codebots behaviour coverage of applications
- Scientifically determine what are Codebots’ best-fit applications
- Identify market need for future behaviours
This lesson will step you through the four steps of running a Bot Behaviour Field Trial:
- Know the behaviours
- Define segments
- Identify and capture behaviours
- Present findings
1. Know the behaviours
The Behaviour Identification Guidelines define the functionality of our Codebots behaviours.
For each behaviour, the guidelines tell us the following:
- Functionality: the basic purpose of the behaviour
- Use cases: examples of the most common applications of the behaviour
- Default capabilities: what capabilities are packaged with the behaviour out-of-the-box.
- Custom capabilities: what the behaviour can achieve using the Codebots protected regions
- Not applicable: actions that the behaviour is not suited for
Use this as a reference while you work through the Field Trial process.
2. Define segments
Gather any available UX assets. These could include:
- User stories
We will be using these UX assets to break the application into “segments”. A segment is a chunk of functionality similar in size to a user story.
Examples of segments could include a shopping cart, booking wizard, a contact form, or live syncing data. These segments can be represented by written notes and/or screenshots. If the application already has written user stories, they can be used as segments without any changes.
Open the GearUp demo app prototype from External Resources to follow along with the video tutorial.
Break an application into “segments” by collecting screenshots and/or written notes (whatever is most relevant). These don’t have to be perfect but should give an overview of all the types of interaction present throughout the application.
3. Identify and capture behaviours
Download the Behaviour Field Trials Matrix from External Resources.
Input the segments into the ‘Segments’ tab of the Behaviour Field Trials Matrix. Include the name and a brief description, as well as the file name (if there is a screenshot) and any additional notes, if necessary. Ensure that the numbers in the ID column match the number of segments.
In the ‘Traceability’ tab, assign any applicable behaviours to each segment, using the Behaviour Identification Guidelines to assist you. Enter an ‘f’ in the behaviours cell if the application is full-coverage (out-of-the-box functionality only), and a ‘c’ if it can be done with customisation.
It is important to keep in mind that this spreadsheet is not diagnostic - it is merely provides an estimate of what behaviours could be used to develop a given project.
In the ‘Stats’ tab, you can see final calculated statistics.
4. Present findings
Download the presentation template from External Resources.
On slide 5 (Segments), enter a list of all the segments you identified in Step 2.
The Behaviour Traceability Matrix generates coverage graphs and statistics in the ‘Stats’ tab. Use this data and the Segments graph to fill out slide 6. Remove any behaviours that aren’t relevant, and add details describing what customisation is required.
For the remaining slides, retain any behaviours which have been identified as useful and include screenshots of your application in the provided space.
Last updated: 16 June 2020