The problem: Security opens a ticket for a serious weakness. The product owner says the sprint is full of client features, and the ticket has no business value. The developers say, “It is not in the sprint, so it is not our call.” The ticket sits for months.
Words used here: a sprint is a short work period, often two weeks, in which a development team builds a set list of work. The product owner decides what the team builds first. The backlog is the waiting list of work.
Think of a repair list at home
A family keeps a list: new sofa, paint the hall, fix the roof leak. Every month there is a little money. The sofa and the paint are things guests will see, so they win. The roof leak is small and hidden, so it slips down one place. Nobody ever said “never fix the roof.” It just never won. Then the rains come.
Security tickets live like that roof leak.
What it looks like at work
Security finds that the login page lets anyone try endless passwords. They open a ticket marked high. At sprint planning, the product owner looks at the features promised to the client and the date. The ticket needs two days of work, and nobody can say what it is worth in business terms. It stays in the backlog. Security asks again every sprint. The answer is always “next sprint.”
- 1Security findsLogin allows endless triesTicket: High
- 2Planning daySprint is full, client demo firstNeeds 2 days
- 3Next sprintNext sprint, I promiseAsked again
- 4Months passStill in the backlog4 months old
- 5Auditor asksWhy is this still open?Repeat finding
Both sides are half right. The product owner is right that a sprint has limited room, and that planning it is their job. Security is right that the weakness is real. What is missing is a shared way to say how serious it is and how soon it must be fixed.
You will notice it when:
- Security tickets are months old and still “not planned.”
- The ticket is written in technical words, such as the name of an attack.
- Nobody can say what the fix costs in days.
- The team has no room kept for risk work, so it is argued every sprint.
- The same ticket appears again in the next audit.
What exactly needs fixing
The first fix is not the code. It is agreeing how serious the ticket is, how soon it must be fixed, and who decides. This card shows the whole problem on one page:
Customer login allows endless password tries
Customer portal login page. Ticket open 4 months, never planned.
Attackers try millions of passwords until one customer account opens.
- Customer accounts taken over
- Client talk and lost trust
- Rushed fix later costs more
- Repeat audit finding
- 1Write it in their wordsWhat can happen, which client, and days of work
- 2Agree the fix timeHigh = fix within 30 days, set once with head of engineering
- 3Reserve sprint roomA small, steady share of every sprint for risk work
Team lead does the work. Head of engineering decides.
High: 30 days from today. A date, not “soon”.
A blank copy of this card is in the Tools section.
Why it happens
- Features have a client’s name on them. Security fixes do not. So features feel more urgent.
- The product owner is judged on features and dates. Risk work does not show on that scorecard.
- There are no agreed fix times. Every ticket starts a new argument.
- The ticket is not in business words. The product owner cannot weigh “insufficient rate limiting.”
- Nobody with authority has said “this must happen.” So the team follows the usual priorities.
- The risk is invisible until it hurts. Like a roof leak in the dry season.
What happens if you ignore it
The weakness stays open until someone else finds it.
- An attacker finds the weakness before the team fixes it.
- A client or an auditor finds it first, and it becomes a repeat finding.
- A rushed fix later costs more than a planned one now.
- Security and the product team stop trusting each other.
At a glance
| Question | Answer |
|---|---|
| How likely is it to hurt us? | Very likely. It happens in most teams that plan work in sprints. |
| Worst case? | The weakness is used to break into customer accounts. |
| What does it cost? | A rushed fix, a talk with the client, and lost trust. |
| What if we wait? | The ticket gets older and the fix gets harder. |
| What does the fix cost? | One agreed table of fix times and a small share of each sprint. |
How to fix it, step by step
Make security work something the team can plan, not something it has to argue about.
- Write the ticket in their words. What can happen, to which client or data, how many days of work, and what the smallest safe fix is.
- Agree fix times once, by how serious the ticket is. Do it with the head of engineering, not ticket by ticket.
- Reserve a small share of every sprint for risk work. The team sets the size. Keep it steady so it is not renegotiated each time.
- Let the product owner choose how, not whether. Offer a full fix, the smallest safe fix, or a stop-gap with a date.
- If a ticket is put off, get a signed note. The business owner signs, and a review date is set. Then it is a decision, not a drift.
- Show the list every month. Open, fixed, and overdue tickets, in one page.
The numbers in the picture are examples. Set your own with the head of engineering.
Who to bring in: The head of engineering (the decision), the product owner, the team lead, security (the risk and the options), and the business owner if a fix is put off.
Tools and templates
Fix times by how serious
| How serious | Fix within | Who can put it off |
|---|---|---|
| Critical | This sprint | Head of engineering, in writing |
| High | 30 days | Product owner, with a signed risk note |
| Medium | 90 days | Product owner |
| Low | Reviewed every quarter | Product owner |
A security ticket the product owner can use
| Field | Write here |
|---|---|
| What can happen | One sentence, in plain words |
| Who is affected | Which client, product, or data |
| How serious | Critical, high, medium, or low |
| Effort | Days of work for the full fix and the smallest safe fix |
| Fix by | A date, from the table above |
| If put off | Who signs, and when it is looked at again |
Blank finding card
| Field | Write here |
|---|---|
| What is broken | One line, in plain words |
| Where it is | The system, team, or process |
| What could go wrong | In one sentence |
| What it costs us | Money, time, a leak, lost trust |
| The fix | The exact action |
| Who fixes it | One name or one team |
| By when | A date, not “soon” |
Email to the head of engineering
Subject: Agreeing fix times for security tickets
Hi [name]. We have several security tickets that have waited for months because every sprint is full. I would like us to agree fix times by how serious a ticket is, and keep a small share of each sprint for this work. Then the product owner does not have to argue each ticket. Can we spend 30 minutes on it this week? I will bring the open tickets and a one-page proposal.
Field tip
A security ticket needs three things before it can win a place: a size in days, a date, and a name next to it.
Words used in this chapter
- Sprint: a short work period, often two weeks, with a set list of work.
- Product owner: the person who decides what the team builds first.
- Backlog: the waiting list of work.
- Stop-gap: a temporary protection until the real fix is done.
- Risk note: a short signed paper that says who accepted a risk, and until when.