Twelve terms
Glossary
Plain-language definitions of the project-tracking terms used on a Pensiro board.
00Jump to a term
01The terms
The terms.
- User story
- A user story is a short description of a feature from the person who wants it, usually phrased "As a [user], I want [goal], so that [reason]." It captures intent, not implementation detail. In Pensiro, every story also carries acceptance criteria, and a Tech story adds technical requirements, so intent and build spec live on one card.
- Acceptance criteria
- Acceptance criteria are the specific, testable conditions a piece of work must meet before it counts as done, phrased as clear pass-or-fail statements. They remove guesswork about what "finished" means. In Pensiro every story carries an acceptance criteria field, which the team fills in as they shape the work.
- WIP limit
- A WIP (work in progress) limit caps how many cards can sit in one board column at once, forcing a team to finish work before starting more. It surfaces bottlenecks early instead of letting unfinished work pile up. Pensiro enforces WIP limits at the database level on the Tech track, not just as a visual suggestion.
- Sprint
- A sprint is a fixed time box, usually one to four weeks, in which a team commits to and completes a slice of work. It creates a steady rhythm of planning, building and review. Pensiro sprints run on a visible countdown with a set start and end date.
- Kanban
- Kanban is a visual work-management method that represents tasks as cards moving through columns that mirror a real workflow, such as Backlog to Deployed. It limits work in progress and makes bottlenecks visible at a glance. Pensiro's board is Kanban-based on both tracks.
- Backlog
- The backlog is the holding column for work that has been captured but not yet started: every accepted request or reported bug a team has not committed to build. It is ordered by priority. In Pensiro, a client intake request lands as a developer-ready story directly in Backlog.
- Feature vs story
- A Feature is a larger body of work, usually a business outcome, that groups related Stories and Bugs beneath it. A Story is one buildable unit of work inside that Feature. A Feature's completion is a rollup percentage of its children; a Story is what one person is assigned. Pensiro nests Features two levels deep so rollups stay unambiguous.
- Bug severity
- Bug severity rates how much damage a defect causes, from P0 (breaks core functionality for everyone, fix immediately) down to P3 (minor or cosmetic). It differs from priority, which is about order, not damage. Pensiro's severity picker runs P0 to P3, and a P0 bug bypasses normal WIP limits.
- Cycle time
- Cycle time is how long a single piece of work takes from when a team starts it to when it is finished, for example from In Progress to Deployed. It measures actual delivery speed, not estimates. Pensiro's Tech dashboard calculates it automatically from the activity log.
- Cumulative flow
- A cumulative flow diagram stacks the number of work items in each board column over time, showing whether work is piling up in one stage or moving smoothly. A widening band means a bottleneck. Pensiro's Tech dashboard renders it directly from column history.
- Throughput
- Throughput is the count of work items a team finishes in a given period, such as stories completed per week. It measures output volume rather than per-item speed, and is a simple check on whether delivery pace is holding steady. Pensiro's Non-Tech dashboard tracks it alongside overdue counts.
- Intake form
- An intake form is the structured entry point where a request first enters a system, replacing informal channels like email or chat. A good intake form captures enough detail that nothing has to be re-asked later. Pensiro puts a plain-language request into a fixed story structure every time, which the team then fills in and edits.
Client words in, dev-ready structure out.
Request early access See pricing
Signups open at launch. Early access reaches the team directly. You can also email support@pensiro.com.