Getting Started

Set up Frankee and generate your first stories

This guide takes you from a new account to your first set of generated user stories. Allow about twenty minutes. Most of that is one-time setup that the rest of your team never has to repeat.

What you will need

• An organization admin. Connecting a work tracker and verifying your company domain are admin-only tasks. If you are joining an organization someone else already set up, skip to Configure your team.
• Access to Jira or Azure DevOps. Frankee reads your real sprint data, so almost everything it does gets better once a tracker is connected. You will need permission to authorize an app in whichever one your team uses.

1. Create your account

1. Sign up

   Register at app.frankee.ai/register with your work email address. Using your company domain matters: it is how Frankee can later connect you to an organization your colleagues have already created.

2. Verify your email

   We send a verification link straight away. You will not be able to use the product until you click it, so if it has not arrived within a few minutes, check your spam folder before requesting another.

3. Land in the right place

   If someone has already invited you, you will see your pending invitations and can accept one. If your email domain matches an organization that requires approval, you will wait briefly while an admin lets you in. Otherwise you will be prompted to create an organization of your own.

2. Set up your organization

Organization admins get a short checklist covering the three things that make onboarding the rest of the team painless.

• Verify your domain. Adding your company domain means colleagues who sign up with a matching email address can find your organization instead of accidentally creating a second one.
• Create your first team. Teams are how Frankee scopes everything: a team has its own framework, its own tracker project, its own product context, and its own generated work.
• Invite a teammate. Frankee is most useful when the whole team can see the same standup starter, retrospective analysis, and review prep.

3. Connect your work tracker

Go to Settings › Org Settings and connect either Jira or Azure DevOps. The connection is made once, at the organization level, and every team in your organization then works from it. An organization admin should do this, since they are also the person who can grant the permissions the connection needs on the tracker side.

What follows is enough to get you connected. Integrations is the full reference for both trackers: the authorization steps in detail, the per-team project and board settings, which Azure DevOps process templates are supported, and what to check when something does not line up.

If you use Jira

You will be sent to Atlassian to authorize Frankee. Frankee reads boards, sprints, and issues, and writes only the stories and action items you explicitly push. If your Atlassian account can reach more than one site, read Integrations before you start: Frankee does not ask which site to use.

If you use Azure DevOps

You will sign in with your Microsoft work account, then choose which Azure DevOps organization to use. Frankee supports projects on the Agile and Scrum process templates. Projects on CMMI or Basic are not supported and will not appear in the project picker. You will need a work or school account: see Integrations for why, and for the per-team project, team, and area path settings.

4. Configure your team

Open Settings › Team Setup. This is where you tell Frankee how your team actually works, which shapes every piece of output it produces.

• Framework. Scrum, Kanban, Scrumban, Custom, or Other. This is not cosmetic: it changes which ceremonies are available and how Frankee talks about your work. A Scrum team gets sprint goals and Sprint Review; a Kanban team gets a date range and a Stakeholder Review instead.
• Sprint length and team size. Used when Frankee reasons about capacity and cadence. Kanban teams are not asked for a sprint length.
• Tracker project. Pick the Jira board or the Azure DevOps project, team, and area path this Frankee team maps to. If two of your Frankee teams share one tracker project, setting the area path correctly is what keeps their work separate.
• Standup settings. How many days without movement counts as stuck, work-in-progress limits, and which priority values you treat as urgent.

5. Add Product Context

On the Product Context tab of Team Setup, describe what you are building. This is the single highest-leverage thing you can do for story quality: it is the difference between a generic story about a login form and one written for your product, your users, and your stack.

• Product name and description. What it does and who it helps.
• Domain and tech stack. Grounds acceptance criteria in reality.
• User personas. Who your stories are written for. Frankee writes from these perspectives rather than inventing generic ones.
• Product vision and additional context. Anything else that keeps generated work on-mission.

You can also upload documents such as a product brief or a strategy deck (PDF or DOCX, up to 10 MB each). Frankee extracts the text and draws on the relevant passages when it generates stories, so you do not have to paste the same background in every time. See Product Context for the full field-by-field guide and how retrieval works.

6. Generate your first stories

1. Open Generate Stories

   Under Backlog › Generate Stories, describe the feature or problem you want broken down. Plain language is fine. You do not need to write anything resembling a user story yourself.

2. Review what comes back

   Frankee produces stories with acceptance criteria, along with the assumptions and dependencies it identified. Read those two sections carefully: they are where a misunderstanding will show up first, and they are often a useful prompt for a conversation with your Product Owner.

3. Push to your tracker

   When you are happy, push the set. Frankee creates an epic and files the stories underneath it. Pushing is one-way and final: Frankee will not re-push or overwrite a story it has already created, so edits after that point happen in Jira or Azure DevOps. Exporting and pushing both happen from Saved Stories: see Story Generation for the full walkthrough.

Where to go next

Once setup is done, the rest of Frankee is available from the sidebar. A few places worth trying in your first week:

• Definition of Ready. Record what your team means by ready, and Frankee applies it while generating, instead of you correcting the same gaps every time.
• Daily Standup Starter. A briefing built from what actually moved in your tracker, including what has been sitting still.
• Retro Analysis and Sprint Review. Preparation for the two ceremonies that most often get done at the last minute.
• Action Items. Frankee scans comments on recently closed work and surfaces follow-ups that were mentioned in passing and never captured anywhere.