Performance Review Self-Assessment Examples for Business Analysts and QA Testers

Last updated: October 2026

A performance review self-assessment is often the only document your manager reads before deciding your rating. Business analysts, BAT analysts and QA testers tend to undersell themselves here, because good testing and clear requirements make problems disappear before anyone sees them. This guide shows how to turn invisible work into specific, rating-appropriate goal comments, core values examples and improvement statements.

What you will get from this guide

A repeatable STAR structure for each goal comment
Wording that matches a “met” rating versus an “exceeded” rating
Before/after self-assessment examples for delivery, migration, compliance and product goals
Core values examples mapped to the Scrum values
Areas for improvement that read as growth, not weakness
A JQL query to pull your year of Jira evidence in two minutes

What a Performance Review Self-Assessment Is For

A self-assessment is not a diary of tasks. The U.S. Office of Personnel Management describes the employee self-accomplishment narrative as a written summary of key achievements that gives the supervisor context and evidence for the rating. That framing works in private industry too. Your manager needs evidence they can defend in a calibration meeting.

It also matters because your words travel. Career columnist Alison Green notes that many managers pull language straight from the self-assessment into their own evaluation. If your comment is vague, the manager’s comment will be vague too.

Reader	What they need from you	What fails with them
Your direct manager	Reminders of work they forgot, with numbers	Lists of duties with no outcomes
Calibration panel or skip-level	Proof that your rating matches peers at the same level	A top rating with “met expectations” evidence
HR file, future managers	A clear record of scope and impact	Internal jargon nobody outside the team understands

The self-assessment and the pay discussion are separate conversations. If you want help with the second one, see the guide to the merit conversation with your manager.

Collect Evidence Before You Write Your Self-Assessment

Analysts and testers leave a long data trail. The problem is that it sits across Jira, test management tools, email and meeting notes. Spend one hour pulling it together before you write a single sentence.

Evidence type	Where to find it	Metric you can state
Stories and requirements delivered	Jira, Confluence requirement pages	Number of stories written or refined; releases supported
Defects found before production	Defect log, test management tool	Defects logged, by severity; critical issues caught pre-release
Test execution	Test runs, BAT or UAT sign-off reports	Test cases executed; cycles finished on schedule
Stakeholder recognition	Email, chat, sprint review notes	Named thanks for a specific result
Scope growth	Team rosters, calendar	Number of Scrum teams or projects supported at once
Learning	Training portal, certificates	Required trainings completed on time; new tools learned

Pull your year of Jira work with JQL

Jira Query Language supports the currentUser() and startOfYear() functions, per Atlassian’s functions reference (as of October 2026). These two queries give you a ready-made evidence list.

-- Dialect: Jira Query Language (JQL), Jira Cloud or Data Center
-- Query 1: work items assigned to you and resolved this calendar year
assignee = currentUser() AND resolved >= startOfYear() ORDER BY resolved DESC

-- Query 2: defects you reported this calendar year
reporter = currentUser() AND issuetype = Bug AND created >= startOfYear() ORDER BY priority DESC

A correct result shows only issues with your name in the Assignee or Reporter field, dated from January 1 of the current year. If Query 2 returns nothing, your project may call defects “Defect” instead of “Bug.” Change the issue type name to match your project.

Export the results and group defects by severity. A quick pivot gives you counts you can quote. The walkthrough on pivot tables for defect reporting shows the setup.

Use the STAR Structure for Each Goal Comment

Several government HR guides teach the STAR format for self-assessments: Situation, Task, Action, Result. It works because it forces you to end on an outcome. Some appraisal systems also cap each comment, for example at 2,000 characters per element. Check your own tool’s limit before you write.

S: Situation

One line of context. What project, what pressure?

T: Task

Your specific responsibility, not the team’s.

A: Action

What you did. Use active verbs: wrote, tested, flagged.

R: Result

The outcome, with a number, date or business effect.

For short comment boxes, compress STAR into two sentences. The first sentence covers situation and action. The second sentence states the result.

Match Your Wording to Your Self-Rating

OPM guidance says performance standards should be objective, measurable, realistic and written down. It also encourages standards above “Fully Successful” so employees know what exceeding looks like. Your comment should prove the level you chose. A top rating with routine evidence invites a downgrade.

Self-rating (example 5-point scale)	Evidence it needs	Wording that fits
5: Significantly exceeded	Results beyond the goal, extra scope, or impact outside your team	“went above,” “ahead of schedule,” “also took on,” numbers
4: Exceeded	Goal met plus one clear extra contribution	“met and improved,” “added,” “reduced”
3: Met	Goal delivered as defined, on time	“completed,” “delivered,” “on time”
2: Partially met	Progress plus a named blocker and a recovery plan	“completed X of Y,” “next step is”

Worked on new products.

After

I wrote requirements and tested setup for [2] new product lines. Both launched on schedule in [3] new markets.

Notice what changed. Each “after” names your action, uses plain verbs and ends on a result. None of them uses words like “synergy” or “best-in-class.”

Core Values Self-Assessment Examples

Many review forms ask you to show company values “with specific examples of behavior.” Generic claims like “I always act with integrity” score poorly because anyone can write them. Use a three-part formula: behavior, example, effect on others.

Your employer’s values will have their own names. To keep the examples neutral, the cards below use the five Scrum values from the 2020 Scrum Guide: commitment, focus, openness, respect and courage. Swap in your company’s labels.

Commitment

I keep my deadlines, even when requirements change late. When scope grew mid-sprint on [project], I re-planned my test cases and still finished on time.

Focus

I supported several Scrum teams at once and kept each team’s priorities clear. I blocked time for each team so no testing cycle slipped.

Openness

I report problems as soon as I find them. On [project], I flagged a data issue before launch instead of letting it reach production.

Respect

I listen to different views. When there is a disagreement, I walk through the issue together with the team so we all understand the problem, then solve it.

Courage

I held a release when acceptance tests failed, and explained the risk to stakeholders with test evidence. The fix shipped [2] days later without production defects.

Tone check. “I help others understand the problem” can sound like you always know better. “We walk through it together” says the same thing as teamwork.

Areas for Improvement Examples That Read as Growth

This is the box most people leave blank or fill with something risky. Writing “none” signals low self-awareness to most managers. Business News Daily, citing Harvard Business School’s Timothy Butler, advises using developmental language rather than describing where you fall down.

Choose an area that is real, connected to a strength, and already being handled by you. That last part matters. If you frame a gap as a problem for your manager to fix, they may assign a fix you do not want.

Risky version	Growth version
I overthink everything and keep adding details nobody asked for.	I’m working on balancing thoroughness with speed when deadlines are tight.
I get distracted in video meetings.	I’d like to build more confidence when speaking up in larger meetings.
None.	I’d like to learn test automation basics so I can speed up regression cycles.
I need feedback.	I’m working on [one area], and I’d welcome feedback on other ways to grow.

Six safe areas for BA and QA roles

Learning a new tool, such as SQL, test automation or a reporting platform
Taking more ownership of larger projects
Sharing ideas earlier in refinement sessions
Learning more about other parts of the business
Balancing thoroughness with speed under tight deadlines
Delegating or documenting so others can pick up work faster

Business analysts who want a structured way to pick a growth area can use IIBA’s member Self-Assessment Tool. IIBA describes it as a thirty-question tool used alongside its Business Analysis Competency Model. Naming a competency from that model makes your improvement goal concrete.

Scenario 1: A BAT Analyst Split Across Three Scrum Teams

Fictional setting: Cedar Point Health Plan moved claims intake from a legacy system to a new platform. One business acceptance testing analyst covered three Scrum teams with overlapping sprint calendars.

Constraints: requirements arrived incomplete, the cutover date was fixed by a vendor contract, and one tester was shared with another program.

Weak goal comment: “Supported multiple teams during the migration.”

Strong goal comment: “I supported three Scrum teams during the claims platform move. I wrote acceptance criteria for [38] stories and ran BAT for each release. I caught [5] high-severity defects before cutover, and the platform went live on the contract date.”

Why this works: the multi-team load becomes evidence of scope, not a complaint. The fixed date turns “on time” into a business result. The defect count proves value that otherwise stays invisible.

Scenario 2: A QA Analyst During a Release Freeze

Fictional setting: Granite Ridge Credit Union froze releases for six weeks during an audit. A QA analyst used the freeze to rebuild the API regression suite for the legacy core banking connector.

Constraints: no production changes allowed, outdated interface documentation, and a developer team that disputed several defects (ticket PROJ-1042 is one fictional example).

Weak area for improvement: “I argue with developers too much.”

Strong area for improvement: “I’m working on sharing test evidence earlier, so defect discussions with developers move faster and stay focused on facts.”

The strong version names a real behavior. It shows the analyst already has a fix in progress and keeps the tone neutral about colleagues.

How Weighted Ratings Change Where You Spend Words

Some review forms weight goals and values differently. Check your own form for the split. As an illustration only, suppose goals count for 70% and values for 30%.

Overall rating = (average goal rating x 0.70) + (values rating x 0.30)

Example: goals average 4.2, values rated 4
(4.2 x 0.70) + (4 x 0.30) = 2.94 + 1.20 = 4.14

A correct calculation always lands between your lowest and highest input. In this example, your goal comments carry more than twice the weight of your values comments. Spend your strongest evidence there, and keep your summary in the same proportion.

Plain-Language Editing Pass

Reviewers skim. Short, plain sentences survive skimming. Before you submit, run this checklist on every comment.

One idea per sentence; split anything with three commas
Start with a verb you did: wrote, tested, found, led
Replace slashes like “projects/testing” with “projects and testing”
Put “and” before the last item in a list
Remove filler such as “I would like to mention that”
Check common errors: “piece of work,” not “peace”; you “make” mistakes
Read it aloud; if you run out of breath, cut it

Common Self-Assessment Mistakes

Mistake	Why it hurts	Fix
Listing duties	Duties are in your job description already	State the result of each duty
Writing “we” for everything	Your manager cannot see your part	Name your action, credit the team for theirs
Top rating, average evidence	Invites a downgrade in calibration	Add the extra scope or number that justifies it
Too personal in improvement areas	Can read as a performance concern	Frame as a skill you are building
Leaving placeholders in	Looks copied and careless	Search for “[” before you submit
Criticizing coworkers	Shifts focus away from your work	Describe the situation neutrally

FAQ

How long should a performance review self-assessment be?

Long enough to prove the rating, short enough to read in a minute per goal. Two to four sentences per goal usually works. Some systems set hard character limits, so check yours first.

What should I write for areas for improvement?

Pick one real area tied to a strength, such as balancing thoroughness with speed. Show you are already working on it. Avoid “none,” which can suggest low self-awareness.

Should I give myself the highest rating?

Only where your evidence clearly exceeds the goal. A top rating is more believable on one or two goals than on all of them. Match your verbs to the rating definitions your employer publishes.

How do I write a self-assessment without sounding arrogant?

Let numbers and outcomes carry the praise instead of adjectives. “Found 27 defects before launch” sounds confident. “I am an exceptional tester” sounds boastful.

What is the STAR method in a self-evaluation?

STAR stands for Situation, Task, Action and Result. It structures each comment so it ends on a measurable outcome. Government HR guides commonly recommend it for self-assessments.

Can I mention work done with my Scrum team?

Yes, but separate your contribution from the team’s. Write “the team delivered X; I wrote the acceptance criteria and ran BAT.” That keeps credit honest and visible.

Next steps

The one takeaway: every goal comment should end with a result your manager can repeat in a calibration meeting.

Run the two JQL queries above and export your year of evidence today.
Draft one STAR comment per goal, then cut each to four sentences or fewer.
Check each self-rating against your evidence, and lower any rating you cannot prove.
Start an accomplishment log for next year so the next review takes one hour, not one week.

Download the Self-Assessment Writing Kit (PDF)

STAR worksheet, rating-to-wording guide, core values formula, improvement phrase bank, plain-language checklist and a 12-month accomplishment log.

Get the free kit

Sources

U.S. Office of Personnel Management, USA Performance Help Center: Complete and Release Employee Self-Accomplishment Narrative
U.S. Office of Personnel Management: Developing Performance Standards
Arkansas National Guard: Writing Effective Self-Assessments (PDF)
Ken Schwaber and Jeff Sutherland: The 2020 Scrum Guide
Atlassian: Advanced searching, functions reference (JQL)
Alison Green, Ask a Manager: How to write a self-assessment for your performance review
Business News Daily: How to Write a Self-Assessment
IIBA: Business Analyst Career Road Map and Self-Assessment Tool