Delivery principles

1. Four eyes on each story.
2. Every story should be testable and have instructions on how to test.
3. Every story is a deliverable and has value.
4. Stories are continuously deployed.
5. A sprint is a week where we focus on one project but the sprint is not the deliverable.
6. Either fixed scope (backlog) or fixed budget (number of sprints).
7. The delivery teams iare responsible for following up stories that are stuck.
8. The deliverables in sprint 0 need to be checked by UX, designer, and a developer.
9. Discoveries that affect the delivery (its estimate etc) need to be communicated in a persistent way and reach the project manager.
10. All deliveries are handled by the delivery teams.
11. Each client is handled by a single delivery team.
12. Each client has a tech lead with certain responsibilites

Types of projects:

• Website
  • External websites
  • Intranets
  • Client portals
• Research (Förstudier)
• Audits (a11y, performance, security)
• Component libraries

Out of scope for the delivery teams:

• Hosting
• Matomo

New Site

Most common type of project.

Subtypes:

• No previous design (e.g. HelloLilly)
• Brand profile from third party (most common)
• UX design from third party (e.g. Cirkus Cirkör)

Take-over of Legacy Site

Examples: ST, NSR, Strategiska

1. Technical review

Subcontractor

Examples: Branäs via Advant