name	about	labels
User Story	A valuable increment of functionality, testable by the users	user story

1. As a [user concerned by the story]
2. I want [goal of the story]
3. so that [reason for the story]

Acceptance Criteria

• Should ‹testable condition that should be satisfied›
• Should ‹testable condition that should be satisfied›
• …

Delete following sections as necessary

Roles

• Operator of the Bosun PaaS (possibly a candidate user)
• User of the Bosun PaaS
• Product Owner of products on the Bosun PaaS
• Security Engineer overseeing the Bosun PaaS

A good user story should be (I-N-V-E-S-T principle)

• Independent (from other user stories, allowing to realize them in any order);
• Negotiable (omit details that would freeze the story);
• Valuable (implementation delivers an increment of functionality, observable by and useful to users);
• Estimatable (developers should be able to estimate its size relative to other stories);
• Sizable (implementation fits in one iteration – if it needs many to complete, it is an EPIC);
• Testable (user must be able to check the conditions of satisfaction).