Start here
Getting started by goal — set up only what you need
Tell Yavaren what you would like to accomplish first; it asks only for what that needs, checks each step against what really exists, shows what it would create before it does, and tells you when your first useful result has happened.
Getting started (Help › Getting started; the first page a new organisation's admin sees).
Getting started has three stages, shown at the top of the page. Each is marked done from what really exists, never from pressing a button:
- Choose your outcome.
- Set up the minimum context. One application, then only what your goals need, one step at a time.
- Complete your first useful action. One button to it, and it counts only when it really happened.
1. Choose what you would like to accomplish first
Goals are grouped under the workspace they start in (Plan, Knowledge, Build, Quality, Deliver, and connecting your tools). Start with one; each works on its own. Choose more any time:
- Plan and track work
- Knowledge and requirements
- AI development
- Test automation for an application
- Improve existing tests
- Automation repository and CI/CD
- Connect the tools you use
- The whole delivery lifecycle
- Communicate software releases, build delivery evidence, synchronise your tools
- Unit tests for your code
If you mentioned goals when you asked for access, they are ticked for you. Nothing is saved until an admin chooses Save my goals.
A goal your plan does not include is listed under "Not part of this setup", with the reason, instead of asking you for steps.
2. Describe your application
Describe the first application now and add others later. Only the name is required. Under Add details (optional) you can also give:
- its parts
- how many repositories and trackers it has
- its databases
- whether it has tests already
- its test environments
- where tests should run
"Not sure" is fine everywhere. Tick Configure repositories and environments later to skip those steps for now. Describing an application connects and creates nothing.
3. Do the steps your goals need
The current step is shown with its one button; All things your goals need lists the rest. Each step says why it is needed, what it is for, and where it is done. It is checked against what really exists:
| State | Meaning |
|---|---|
| Done | it exists (a connection you already made is never asked for again) |
| To do | it is missing: the button opens the place it is done |
| Check yourself | Yavaren cannot tell from here; the step says how to check |
| Optional | useful, not required |
Planning and knowledge need nothing outside Yavaren. Test automation needs read access to the application's repository, a test environment and a capable runner; it does not need a tracker or AI keys. AI development adds a tracker (Yavaren Boards counts), engineers and an AI budget.
4. The proposed setup
Admins see what setting up the goals would create (a Yavaren Boards work space, a knowledge space), and what is done on its own page (connections, runners), with the permissions and the cost of each. Create… asks you to confirm first, and each item is created once, however often it is pressed.
5. Your first results
Each goal has a first result, marked once it really happened:
- an item in a backlog
- an approved requirement
- an analysis
- a test run that executed tests
- a pipeline run that recorded the commit asked for
- a draft pull request
Generated code alone is not a test run.